diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 076bcbcf5..3fde0d38d 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -33,71 +33,115 @@ msgid "Install" msgstr "" #: ../../content/administration/install/cdn.rst:3 -msgid "Setting up a Content Delivery Network (CDN)" +msgid "Set up a content delivery network (CDN)" msgstr "" #: ../../content/administration/install/cdn.rst:8 -msgid "Deploying with KeyCDN_" +msgid "Deploying with KeyCDN" msgstr "" -#: ../../content/administration/install/cdn.rst:12 -msgid "This document will guide you through the setup of a KeyCDN_ account with your Odoo powered website." +#: ../../content/administration/install/cdn.rst:10 +msgid "A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, is a geographically distributed network of servers that provides high speed internet content. The :abbr:`CDN (Content Delivery Network)` provides quick, high-quality content delivery for content-heavy websites." msgstr "" -#: ../../content/administration/install/cdn.rst:16 -msgid "Step 1: Create a pull zone in the KeyCDN dashboard" +#: ../../content/administration/install/cdn.rst:14 +msgid "This document will guide you through the setup of a KeyCDN_ account with an Odoo powered website." msgstr "" -#: ../../content/administration/install/cdn.rst:21 -msgid "When creating the zone, enable the CORS option in the :guilabel:`advanced features` submenu. (more on that later)" +#: ../../content/administration/install/cdn.rst:17 +msgid "Create a pull zone in the KeyCDN dashboard" msgstr "" -#: ../../content/administration/install/cdn.rst:27 -msgid "Once done, you'll have to wait a bit while KeyCDN_ is crawling your website." +#: ../../content/administration/install/cdn.rst:19 +msgid "On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` menu item on the left. On the form, give a value to the :guilabel:`Zone Name`, which will appear as part of the :abbr:`CDN (Content Delivery Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the :guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the :guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this address should be the full Odoo database :abbr:`URL (Uniform Resource Locator)`." msgstr "" -#: ../../content/administration/install/cdn.rst:32 -msgid "a new URL has been generated for your Zone, in this case it is ``http://pulltest-b49.kxcdn.com``" +#: ../../content/administration/install/cdn.rst:28 +msgid "Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* subdomain prefix with the actual name of the database. A custom :abbr:`URL (Uniform Resource Locator)` can be used, as well, in place of the Odoo subdomain that was provided to the database." +msgstr "" + +#: ../../content/administration/install/cdn.rst:-1 +msgid "KeyCDN's Zone configuration page." msgstr "" #: ../../content/administration/install/cdn.rst:36 -msgid "Step 2: Configure the odoo instance with your zone" +msgid "Under the :guilabel:`General Settings` heading below the zone form, click the :guilabel:`Show all settings` button to expand the zone options. This should be the last option on the page. After expanding the :guilabel:`General Settings` ensure that the :guilabel:`CORS` option is :guilabel:`enabled`." msgstr "" -#: ../../content/administration/install/cdn.rst:38 -msgid "In the Odoo back end, go to the :guilabel:`Website Settings`: menu, then activate the CDN support and copy/paste your zone URL in the :guilabel:`CDN Base URL` field. This field is only visible and configurable if you have developer mode activated." +#: ../../content/administration/install/cdn.rst:41 +msgid "Next, scroll to the bottom of the zone configuration page and :guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be deployed. This can take about 10 minutes." msgstr "" -#: ../../content/administration/install/cdn.rst:46 -msgid "Now your website is using the CDN for the resources matching the :guilabel:`CDN filters` regular expressions." +#: ../../content/administration/install/cdn.rst:-1 +msgid "KeyCDN deploying the new Zone." msgstr "" #: ../../content/administration/install/cdn.rst:49 -msgid "You can have a look to the HTML of your website in order to check if the CDN integration is properly working." +msgid "A new :guilabel:`Zone URL` has been generated for your Zone, in this example it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each database." +msgstr "" + +#: ../../content/administration/install/cdn.rst:52 +msgid "Copy this :guilabel:`Zone URL` to a text editor for later, as it will be used in the next steps." +msgstr "" + +#: ../../content/administration/install/cdn.rst:55 +msgid "Configure the Odoo instance with the new zone" msgstr "" #: ../../content/administration/install/cdn.rst:57 -msgid "Why should I activate CORS?" -msgstr "" - -#: ../../content/administration/install/cdn.rst:59 -msgid "A security restriction in some browsers (Firefox and Chrome at time of writing) prevents a remotely linked CSS file to fetch relative resources on this same external server." +msgid "In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and then activate the :guilabel:`Content Delivery Network (CDN)` setting and copy/paste the :guilabel:`Zone URL` value from the earlier step into the :guilabel:`CDN Base URL` field. This field is only visible and configurable when :doc:`Developer Mode <../../applications/general/developer_mode>` is activated." msgstr "" #: ../../content/administration/install/cdn.rst:63 -msgid "If you don't activate the CORS option in the CDN zone, the more obvious resulting problem on a default Odoo website will be the lack of font-awesome icons because the font file declared in the font-awesome CSS won't be loaded on the remote server." +msgid "Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`." msgstr "" -#: ../../content/administration/install/cdn.rst:68 -msgid "Here's what you would see on your homepage in such a case:" +#: ../../content/administration/install/cdn.rst:66 +msgid ":guilabel:`Save` the settings when complete." msgstr "" -#: ../../content/administration/install/cdn.rst:73 -msgid "A security error message will also appear in the browser's console:" +#: ../../content/administration/install/cdn.rst:-1 +msgid "Activate the CDN setting in Odoo." msgstr "" -#: ../../content/administration/install/cdn.rst:78 -msgid "Enabling the CORS option in the CDN fixes this issue." +#: ../../content/administration/install/cdn.rst:72 +msgid "Now the website is using the CDN for the resources matching the :guilabel:`CDN filters` regular expressions." +msgstr "" + +#: ../../content/administration/install/cdn.rst:75 +msgid "In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` integration is evidenced as working properly by checking the :abbr:`URL (Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen by using your web browser's :guilabel:`Inspect` feature on the Odoo website. Look for it's record by searching within the :guilabel:`Network` tab inside of devtools." +msgstr "" + +#: ../../content/administration/install/cdn.rst:-1 +msgid "The CDN Base URL can be seen using the inspect function on the Odoo website." +msgstr "" + +#: ../../content/administration/install/cdn.rst:85 +msgid "Prevent security issues by activating cross-origin resource sharing (CORS)" +msgstr "" + +#: ../../content/administration/install/cdn.rst:87 +msgid "A security restriction in some browsers (such as Mozilla Firefox and Google Chrome) prevents a remotely linked CSS file to fetch relative resources on this same external server." +msgstr "" + +#: ../../content/administration/install/cdn.rst:90 +msgid "If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard Odoo website will be the lack of *Font Awesome* icons because the font file declared in the *Font Awesome* CSS won't be loaded from the remote server." +msgstr "" + +#: ../../content/administration/install/cdn.rst:95 +msgid "When these cross-origin resource issues occur, a security error message similar to the output below will appear in the web browser's developer console:" +msgstr "" + +#: ../../content/administration/install/cdn.rst:98 +msgid "``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://yourdatabase.odoo.com' is therefore not allowed access.``" +msgstr "" + +#: ../../content/administration/install/cdn.rst:-1 +msgid "Error message populated in the browser console." +msgstr "" + +#: ../../content/administration/install/cdn.rst:106 +msgid "Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the :abbr:`CDN (Content Delivery Network)` settings fixes this issue." msgstr "" #: ../../content/administration/install/deploy.rst:3 @@ -148,7 +192,7 @@ msgstr "" #: ../../content/administration/install/deploy.rst:58 #: ../../content/administration/install/deploy.rst:153 #: ../../content/administration/install/deploy.rst:276 -msgid "in ``/etc/odoo.conf`` set:" +msgid "in :ref:`the configuration file ` set:" msgstr "" #: ../../content/administration/install/deploy.rst:53 @@ -367,7 +411,7 @@ msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" msgstr "" #: ../../content/administration/install/deploy.rst:241 -msgid "in ``/etc/odoo.conf``:" +msgid "in :ref:`the configuration file `:" msgstr "" #: ../../content/administration/install/deploy.rst:257 @@ -835,7 +879,7 @@ msgstr "" #: ../../content/administration/install/install.rst:59 #: ../../content/administration/maintain/domain_names.rst:167 #: ../../content/administration/maintain/domain_names.rst:237 -#: ../../content/administration/maintain/supported_versions.rst:27 +#: ../../content/administration/maintain/supported_versions.rst:31 #: ../../content/administration/upgrade/odoo_online.rst:3 msgid "Odoo Online" msgstr "" @@ -1416,196 +1460,205 @@ msgid "For more information, visit `Microsoft's documentation `_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings will need to connect and perform the following configuration. Next, navigate to the section labeled :guilabel:`Manage Azure Active Directory`." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:26 +#: ../../content/administration/maintain/azure_oauth.rst:30 msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select :guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:32 +#: ../../content/administration/maintain/azure_oauth.rst:36 msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https:///microsoft_outlook/confirm` in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at which your Odoo instance can be reached (e.g. mydatabase.odoo.com if you are hosted on Odoo.com) in the URL field. Then, click :guilabel:`Register` and the application is created." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:39 +#: ../../content/administration/maintain/azure_oauth.rst:43 msgid "API permissions" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:41 -msgid "The :guilabel:`API permissions` should be set next. Odoo will need specific API permissions to be able to read (IMAP) and send (IMAP) emails in the Microsoft 365 setup. First, click the :guilabel:`API permissions` link, located in the left menu bar. Next, click on the :guilabel:`(+) Add a Permission` button and select :guilabel:`Microsoft Graph` under :guilabel:`Commonly Used Microsoft APIs`. After, select the :guilabel:`Delegated Permissions` option." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:48 -msgid "In the search bar, search for the following :guilabel:`Deregulated permissions` and click :guilabel:`Add permissions` for each one:" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:51 -msgid ":guilabel:`SMTP.Send`" +#: ../../content/administration/maintain/azure_oauth.rst:45 +msgid "The :guilabel:`API permissions` should be set next. Odoo will need specific API permissions to be able to read (IMAP) and send (SMTP) emails in the Microsoft 365 setup. First, click the :guilabel:`API permissions` link, located in the left menu bar. Next, click on the :guilabel:`(+) Add a Permission` button and select :guilabel:`Microsoft Graph` under :guilabel:`Commonly Used Microsoft APIs`. After, select the :guilabel:`Delegated Permissions` option." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:52 -msgid ":guilabel:`IMAP.AccessAsUser.All`" +msgid "In the search bar, search for the following :guilabel:`Deregulated permissions` and click :guilabel:`Add permissions` for each one:" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:55 +msgid ":guilabel:`SMTP.Send`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:56 +msgid ":guilabel:`IMAP.AccessAsUser.All`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:59 msgid "The :guilabel:`User.Read` permission will be added by default." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:None +#: ../../content/administration/maintain/azure_oauth.rst:-1 msgid "API permissions added for the app." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:62 +#: ../../content/administration/maintain/azure_oauth.rst:66 msgid "Assign users and groups" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:64 +#: ../../content/administration/maintain/azure_oauth.rst:68 msgid "After adding the API permissions, navigate back to the :guilabel:`Overview` of the :guilabel:`Application` in the top of the left sidebar menu." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:67 +#: ../../content/administration/maintain/azure_oauth.rst:71 msgid "Now, add users to this application. Under the :guilabel:`Essentials` overview table, click on the link labeled :guilabel:`Managed Application in Local Directory`, or the last option on the bottom right-hand side of the table." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:None +#: ../../content/administration/maintain/azure_oauth.rst:-1 msgid "Link to the created application and to add users/groups." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:75 +#: ../../content/administration/maintain/azure_oauth.rst:79 msgid "In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click on :guilabel:`(+) Add User/Group`. Depending on the account, either a :guilabel:`Group` and a :guilabel:`User` can be added, or only :guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` to be added." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:80 +#: ../../content/administration/maintain/azure_oauth.rst:84 msgid "Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None Selected` and add the users or group of users that will be sending emails from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to the application." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:86 +#: ../../content/administration/maintain/azure_oauth.rst:90 msgid "Create credentials" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:88 +#: ../../content/administration/maintain/azure_oauth.rst:92 msgid "Now that the Microsoft Azure app is set up, credentials need to be created for the Odoo setup. These include the :guilabel:`Client ID` and :guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or :guilabel:`Application ID` is located under the :guilabel:`Display Name` in the :guilabel:`Essentials` overview of the app." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:None +#: ../../content/administration/maintain/azure_oauth.rst:-1 msgid "Application/Client ID located in the Overview of the app." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:98 +#: ../../content/administration/maintain/azure_oauth.rst:102 msgid "Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this value, click on :guilabel:`Certificates & Secrets` in the left sidebar menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do this, click on the :guilabel:`(+) New Client Secret` button." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:102 +#: ../../content/administration/maintain/azure_oauth.rst:106 msgid "A window on the right will populate with a button labeled :guilabel:`Add a client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or something recognizable, and then set the :guilabel:`expiration date`." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:107 +#: ../../content/administration/maintain/azure_oauth.rst:111 msgid "A new :guilabel:`Client Secret` will need to be produced and configured if the first one expires. In this event, there could be an interruption of service, so the expiration date should be noted and set to the furthest possible date." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:111 +#: ../../content/administration/maintain/azure_oauth.rst:115 msgid "Next, click on :guilabel:`Add` when these two values are entered. A :guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret Value` into a notepad as it will become encrypted after leaving this page. The :guilabel:`Secret ID` is not needed." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:None +#: ../../content/administration/maintain/azure_oauth.rst:-1 msgid "Client Secret Value or Value in the app's credentials." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:120 +#: ../../content/administration/maintain/azure_oauth.rst:124 msgid "After these steps, the following items should be ready to be set up in Odoo:" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:122 +#: ../../content/administration/maintain/azure_oauth.rst:126 msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:123 +#: ../../content/administration/maintain/azure_oauth.rst:127 msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:125 +#: ../../content/administration/maintain/azure_oauth.rst:129 msgid "This completes the setup on the :guilabel:`Microsoft Azure Portal` side." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:128 -#: ../../content/administration/maintain/google_oauth.rst:84 +#: ../../content/administration/maintain/azure_oauth.rst:132 +#: ../../content/administration/maintain/google_oauth.rst:111 msgid "Setup in Odoo" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:131 +#: ../../content/administration/maintain/azure_oauth.rst:135 msgid "Enter Microsoft Outlook credentials" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:133 +#: ../../content/administration/maintain/azure_oauth.rst:137 msgid "First, open the Odoo database and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Outlook`. After that, install the module called :guilabel:`Microsoft Outlook`." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:137 +#: ../../content/administration/maintain/azure_oauth.rst:141 msgid "Next, navigate to :guilabel:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`External Email Servers` is checked. This populates a new option for :guilabel:`Outlook Credentials`." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:141 +#: ../../content/administration/maintain/azure_oauth.rst:145 msgid ":guilabel:`Save` the progress." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:143 +#: ../../content/administration/maintain/azure_oauth.rst:147 msgid "Then, copy and paste the :guilabel:`Client ID` (Application ID) and :guilabel:`Client Secret (Client Secret Value)` into the respective fields and :guilabel:`Save` the settings." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:147 -#: ../../content/administration/maintain/google_oauth.rst:98 +#: ../../content/administration/maintain/azure_oauth.rst:151 +#: ../../content/administration/maintain/google_oauth.rst:127 msgid "Configure outgoing email server" msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:149 +#: ../../content/administration/maintain/azure_oauth.rst:153 msgid "On the :guilabel:`General Settings` page, under the :guilabel:`External Email Servers` setting, click the :guilabel:`Outgoing Email Servers` link to configure the Microsoft account." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:152 +#: ../../content/administration/maintain/azure_oauth.rst:156 msgid "Then, create a new email server and check the box for :guilabel:`Outlook`. Next, fill in the :guilabel:`Description` (it can be anything) and the Microsoft Outlook email :guilabel:`Username`." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:155 +#: ../../content/administration/maintain/azure_oauth.rst:159 msgid "Then, cick on :guilabel:`Connect your Outlook account`." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:157 +#: ../../content/administration/maintain/azure_oauth.rst:161 msgid "A new window from Microsoft opens to complete the :guilabel:`authorization process`. Select the appropriate email address that is being configured in Odoo." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:None +#: ../../content/administration/maintain/azure_oauth.rst:-1 msgid "Permission page to grant access between newly created app and Odoo." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:164 +#: ../../content/administration/maintain/azure_oauth.rst:168 msgid "Then, allow Odoo to access the Microsoft account by clicking on :guilabel:`Yes`. After this, the page will navigate back to the newly configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration automatically loads the :guilabel:`token` in Odoo, and a tag stating :guilabel:`Outlook Token Valid` appears in green." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:169 +#: ../../content/administration/maintain/azure_oauth.rst:173 msgid "Finally, click :guilabel:`Test Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Microsoft Outlook using OAuth authentication." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:173 +#: ../../content/administration/maintain/azure_oauth.rst:177 msgid "To extend the server's use, set a :guilabel:`mail.force.smtp.from` system parameter so that email is sent from a default *from email address* for all emails sent from the database. The value of the system parameter should be the :guilabel:`username` being configured in Microsoft Outlook." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:179 +#: ../../content/administration/maintain/azure_oauth.rst:183 msgid "The :guilabel:`System Parameters` can be accessed by activating :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." msgstr "" -#: ../../content/administration/maintain/azure_oauth.rst:184 +#: ../../content/administration/maintain/azure_oauth.rst:188 msgid ":doc:`../../applications/general/email_communication/email_domain`" msgstr "" #: ../../content/administration/maintain/domain_names.rst:3 +#: ../../content/administration/maintain/odoo_online.rst:70 msgid "Domain names" msgstr "" @@ -1678,7 +1731,7 @@ msgid "Some search engines provide tools for web admins, such as `Google Search msgstr "" #: ../../content/administration/maintain/domain_names.rst:74 -msgid ":doc:`/applications/websites/website/optimize/seo`" +msgid ":doc:`/applications/websites/website/pages/seo`" msgstr "" #: ../../content/administration/maintain/domain_names.rst:75 @@ -1721,7 +1774,7 @@ msgstr "" msgid "To do so, go to :menuselection:`Website --> Go to website --> Promote --> Domain Name`. Alternatively, open your `database manager `_, click on the :guilabel:`settings` button next to your database, then on :guilabel:`Domain names`." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:None +#: ../../content/administration/maintain/domain_names.rst:-1 msgid "Clicking on Domain Names from an Odoo website" msgstr "" @@ -1729,7 +1782,7 @@ msgstr "" msgid "Search for the domain name of your choice to check its availability, then select the one you want to register for your website." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:None +#: ../../content/administration/maintain/domain_names.rst:-1 msgid "The search of the domain name example.com shows which associated domains are available." msgstr "" @@ -1757,7 +1810,7 @@ msgstr "" msgid "To manage the DNS records of your domain name registered with Odoo or to visualize the contacts associated with it, open your `database manager `_, click on the :guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on :guilabel:`Contacts` or :guilabel:`DNS`." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:None +#: ../../content/administration/maintain/domain_names.rst:-1 msgid "Management of the domain names linked to an Odoo database" msgstr "" @@ -1811,7 +1864,7 @@ msgstr "" #: ../../content/administration/maintain/domain_names.rst:172 #: ../../content/administration/maintain/domain_names.rst:251 -#: ../../content/administration/maintain/supported_versions.rst:27 +#: ../../content/administration/maintain/supported_versions.rst:32 #: ../../content/administration/odoo_sh.rst:5 #: ../../content/administration/upgrade/odoo_sh.rst:3 msgid "Odoo.sh" @@ -2030,7 +2083,7 @@ msgstr "" msgid "In the :guilabel:`Domain` field, fill in the web address of your website (e.g., ``https://www.example.com``) and click on :guilabel:`Save`." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:None +#: ../../content/administration/maintain/domain_names.rst:-1 msgid "Configuring https://www.example.com as the Domain of the website" msgstr "" @@ -2047,7 +2100,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr "" #: ../../content/administration/maintain/enterprise.rst:6 -msgid "Upgrade Community to Enterprise" +msgid "Switch from Community to Enterprise" msgstr "" #: ../../content/administration/maintain/enterprise.rst:8 @@ -2155,208 +2208,235 @@ msgid "For more information, visit `Google's documentation `_. Log in with your *Google Workspace* account if you have one, otherwise log in with your personal Gmail account (this should match the email address you want to configure in Odoo)." +#: ../../content/administration/maintain/google_oauth.rst:24 +msgid "To get started, go to the `Google API Console `_. Log in with your *Google Workspace* account if you have one, otherwise log in with your personal Gmail account (this should match the email address you want to configure in Odoo)." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:25 -msgid "After that, click on :guilabel:`Create Project`, located on the far right of the OAuth consent screen. If a project has already been created in this account, then the :guilabel:`New Project` option will be located on the top left under the :guilabel:`Select a project` drop-down menu." +#: ../../content/administration/maintain/google_oauth.rst:28 +msgid "After that, click on :guilabel:`Create Project`, located on the far right of the :guilabel:`OAuth consent screen`. If a project has already been created in this account, then the :guilabel:`New Project` option will be located on the top right under the :guilabel:`Select a project` drop-down menu." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:29 -msgid "On the :guilabel:`New Project` screen, rename the :guilabel:`Project name` to `Odoo` and browse for the :guilabel:`Location`. Set the :guilabel:`Location` as the `Google Workspace` organization. If you are using a personal Gmail account, then leave the :guilabel:`Location` as `No Organization`." +#: ../../content/administration/maintain/google_oauth.rst:33 +msgid "On the :menuselection:`New Project` screen, rename the :guilabel:`Project name` to `Odoo` and browse for the :guilabel:`Location`. Set the :guilabel:`Location` as the *Google Workspace organization*. If you are using a personal Gmail account, then leave the :guilabel:`Location` as :guilabel:`No Organization`." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:None -msgid "Project Name and Location for Google Oauth." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:37 -msgid "Click on :guilabel:`Create` to finish this step. On the next screen, :guilabel:`User Type` options, select the :guilabel:`External` option, and then click on :guilabel:`Create` again, which will finally navigate to the :guilabel:`Edit app registration` page." +#: ../../content/administration/maintain/google_oauth.rst:-1 +msgid "Project Name and Location for Google OAuth." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:42 -msgid "Edit app registration" +msgid "Click on :guilabel:`Create` to finish this step." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:44 -msgid "On the :guilabel:`Oauth consent screen` step, under the :guilabel:`App information` section, enter `Odoo` in the :guilabel:`App name` field. Select the organization's email address under the :guilabel:`User support` email field." +#: ../../content/administration/maintain/google_oauth.rst:45 +msgid "OAuth consent screen" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:47 -msgid "Next, under :menuselection:`App Domain --> Authorized domains`, click on :guilabel:`Add Domain` and enter `odoo.com`." +msgid "If the page doesn't redirect to the :menuselection:`User Type` options, click on :guilabel:`OAuth consent screen` in the left menu." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:49 -msgid "After that, under the :guilabel:`Developer contact information` section, enter the organization's email address. Google uses this email address to notify the organization about any changes to your project." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:52 -msgid "Next, click on the :guilabel:`Save and Continue` button." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:53 -msgid "Then, skip the :guilabel:`Scopes` page by scrolling to the bottom and clicking on :guilabel:`Save and Continue`." +#: ../../content/administration/maintain/google_oauth.rst:50 +msgid "Under :guilabel:`User Type` options, select the appropriate :guilabel:`User Type`, and then click on :guilabel:`Create` again, which will finally navigate to the :menuselection:`Edit app registration` page." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:55 -msgid "Next, add the email being configured under the :guilabel:`Test users` step by clicking on :guilabel:`Add Users` and then the :guilabel:`Save and Continue` button. A summary of the :guilabel:`App registration` appears." +msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:58 -msgid "Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard`." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:61 -msgid "Create Credentials" +#: ../../content/administration/maintain/google_oauth.rst:59 +msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:63 -msgid "Now that you have set up the project, you need to create credentials, which includes the :guilabel:`Client ID` and :guilabel:`Client Secret`. First, click on :guilabel:`Credentials` in the left sidebar menu." +msgid "Edit app registration" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:65 +msgid "Next we will configure the app registration of the project." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:67 -msgid "Then, click on :guilabel:`Create Credentials` in the top menu and select :guilabel:`OAuth client ID` from the dropdown menu." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:70 -msgid "Under :guilabel:`Application Type`, select :guilabel:`Web Application` from the dropdown menu." +msgid "On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App information` section, enter `Odoo` in the :guilabel:`App name` field. Select the organization's email address under the :guilabel:`User support` email field." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:71 -msgid "In the :guilabel:`Client ID` field, enter `Odoo`." +msgid "Next, under :menuselection:`App Domain --> Authorized domains`, click on :guilabel:`Add Domain` and enter `odoo.com`." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:72 -msgid "Under the :guilabel:`Authorized redirect URIs` label, click the button :guilabel:`ADD URI`, and then input `https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1` field. Be sure to replace the *yourdbname* part of the URL with your actual Odoo database name." +#: ../../content/administration/maintain/google_oauth.rst:74 +msgid "After that, under the :guilabel:`Developer contact information` section, enter the organization's email address. Google uses this email address to notify the organization about any changes to your project." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:75 -msgid "Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID` and :guilabel:`Client Secret`. Finally, copy each generated value for later use when configuring in Odoo, and then navigate to the Odoo database." +#: ../../content/administration/maintain/google_oauth.rst:78 +msgid "Next, click on the :guilabel:`Save and Continue` button. Then, skip the :menuselection:`Scopes` page by scrolling to the bottom and clicking on :guilabel:`Save and Continue`." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:None -msgid "Client ID and Client Secret for Google OAuth." +#: ../../content/administration/maintain/google_oauth.rst:81 +msgid "If continuing in testing mode (External), add the email addresses being configured under the :guilabel:`Test users` step, by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:87 -msgid "Enter Google Credentials" +#: ../../content/administration/maintain/google_oauth.rst:85 +msgid "Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to finish setting up the project." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:89 -msgid "First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Google`. Install the module called :guilabel:`Google Gmail`." +msgid "Create Credentials" msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:92 -msgid "Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`Custom Email Servers` is checked. This populates a new option for :guilabel:`Gmail Credentials`. Then, copy and paste the :guilabel:`Client ID` and :guilabel:`Client Secret` into the respective fields and :guilabel:`Save` the settings." +#: ../../content/administration/maintain/google_oauth.rst:91 +msgid "Now that the project is set up, credentials should be created, which includes the *Client ID* and *Client Secret*. First, click on :guilabel:`Credentials` in the left sidebar menu." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:100 -msgid "After that, on the :guilabel:`General Settings` page, under :guilabel:`Custom Email Servers`, click :guilabel:`Outgoing Email Servers` to configure the external Gmail account." +#: ../../content/administration/maintain/google_oauth.rst:94 +msgid "Then, click on :guilabel:`Create Credentials` in the top menu and select :guilabel:`OAuth client ID` from the dropdown menu." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:None -#: ../../content/administration/maintain/google_oauth.rst:None -msgid "Configure Outgoing Email Servers in Odoo." +#: ../../content/administration/maintain/google_oauth.rst:97 +msgid "Under :guilabel:`Application Type`, select :guilabel:`Web Application` from the dropdown menu." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:107 -msgid "Then, :guilabel:`Create` a new email server and select the option for :guilabel:`Gmail`. Next, fill in the :guilabel:`Description` (can be anything) and the email :guilabel:`Username` and click on :guilabel:`Connect your Gmail account`." +#: ../../content/administration/maintain/google_oauth.rst:98 +msgid "In the :guilabel:`Name` field, enter `Odoo`." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:111 -msgid "A new window from :guilabel:`Google` opens to complete the authorization process. Select the appropriate email address that is being configured in Odoo." +#: ../../content/administration/maintain/google_oauth.rst:99 +msgid "Under the :guilabel:`Authorized redirect URIs` label, click the button :guilabel:`ADD URI`, and then input `https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1` field. Be sure to replace the *yourdbname* part of the URL with the actual Odoo database name." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:102 +msgid "Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID` and :guilabel:`Client Secret`. Finally, copy each generated value for later use when configuring in Odoo, and then navigate to the Odoo database." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:-1 +msgid "Client ID and Client Secret for Google OAuth." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:114 -msgid "If the email address is a personal account, an extra step pops up, click :guilabel:`Continue` to allow the verification and connect the Gmail account to Odoo." +msgid "Enter Google Credentials" msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:117 -msgid "Then, allow Odoo to access the Google account by clicking on :guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates back to the newly configured outgoing email server in Odoo. The configuration automatically loads the token in Odoo, and a tag stating :guilabel:`Gmail Token Valid` appears in green." +#: ../../content/administration/maintain/google_oauth.rst:116 +msgid "First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Google`. Install the module called :guilabel:`Google Gmail`." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:126 -msgid "Finally, save the settings and :guilabel:`Test the Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Google using OAuth authentication." +#: ../../content/administration/maintain/google_oauth.rst:120 +msgid "Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is checked. This populates a new option for :guilabel:`Gmail Credentials` or :guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and :guilabel:`Save` the settings." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:131 -msgid "Google OAuth FAQ" +#: ../../content/administration/maintain/google_oauth.rst:129 +msgid "To configure the external Gmail account, return to the top of the :guilabel:`Custom Email Servers` setting and then click the :guilabel:`Outgoing Email Servers` link." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:134 -msgid "Production VS Testing Publishing Status" +#: ../../content/administration/maintain/google_oauth.rst:-1 +msgid "Configure Outgoing Email Servers in Odoo." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:136 -msgid "Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` (instead of Testing) will display the following warning message:" +msgid "Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the email :guilabel:`Username` (if required)." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:None -msgid "OAuth is Limited to 100 Sensitive Scope Logins." +#: ../../content/administration/maintain/google_oauth.rst:139 +msgid "Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` (under the :guilabel:`Authenticate with` or :guilabel:`Connection` section). Finally, click on :guilabel:`Connect your Gmail Account`." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:143 -msgid "To correct this warning, navigate to the `Google API Platform `_. If the :guilabel:`Publishing status` is :guilabel:`In Production`, click :guilabel:`Back to Testing` to correct the issue." +msgid "A new window labeled :guilabel:`Google` opens to complete the authorization process. Select the appropriate email address that is being configured in Odoo." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:148 -msgid "No Test Users Added" +#: ../../content/administration/maintain/google_oauth.rst:146 +msgid "If the email address is a personal account, then an extra step pops up, so click :guilabel:`Continue` to allow the verification and connect the Gmail account to Odoo." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:150 -msgid "If no test users are added to the OAuth consent screen, then a 403 access denied error will populate." +#: ../../content/administration/maintain/google_oauth.rst:149 +msgid "Then, allow Odoo to access the Google account by clicking on :guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates back to the newly configured outgoing email server in Odoo. The configuration automatically loads the token in Odoo, and a tag stating :guilabel:`Gmail Token Valid` appears in green." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:None -msgid "403 Access Denied Error." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:157 -msgid "To correct this error, return to the :guilabel:`OAuth consent screen` under :guilabel:`APIs & Services` and add test user(s) to the app. Add the email that you are configuring in Odoo." +#: ../../content/administration/maintain/google_oauth.rst:158 +msgid "Finally, :guilabel:`Test the Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Google using OAuth authentication." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:162 -msgid "Gmail Module not updated" +msgid "Google OAuth FAQ" msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:164 -msgid "If the :guilabel:`Gmail Module` in Odoo has not been updated to the latest version, then a :guilabel:`Forbidden` error message populates." +#: ../../content/administration/maintain/google_oauth.rst:165 +msgid "Production VS Testing Publishing Status" msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:None -msgid "Forbidden you don't have the permission to access the requested resource." +#: ../../content/administration/maintain/google_oauth.rst:167 +msgid "Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` (instead of :guilabel:`Testing`) will display the following warning message:" msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:171 -msgid "To correct this error, go to the :guilabel:`Apps` module and clear out the search terms. Then, search for `Gmail` or `Google` and upgrade the :guilabel:`Google Gmail` module. Finally, click on the three dots on the upper right of the module and select :guilabel:`Upgrade`." +#: ../../content/administration/maintain/google_oauth.rst:-1 +msgid "OAuth is Limited to 100 Sensitive Scope Logins." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:176 -msgid "Application Type" +#: ../../content/administration/maintain/google_oauth.rst:174 +msgid "To correct this warning, navigate to the `Google API Platform `_. If the :guilabel:`Publishing status` is :guilabel:`In Production`, click :guilabel:`Back to Testing` to correct the issue." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:178 -msgid "When creating the :guilabel:`Credentials` (OAuth Client ID and Client Secret), if :guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an :guilabel:`Authorization Error` appears." +#: ../../content/administration/maintain/google_oauth.rst:179 +msgid "No Test Users Added" msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:None -msgid "Error 400 Redirect URI Mismatch." +#: ../../content/administration/maintain/google_oauth.rst:181 +msgid "If no test users are added to the OAuth consent screen, then a 403 access denied error will populate." msgstr "" -#: ../../content/administration/maintain/google_oauth.rst:186 -msgid "To correct this error, delete the credentials already created and create new credentials, selecting :guilabel:`Web Application` for the :guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect URIs`, click :guilabel:`ADD URI` and type: `https://yourdbname.odoo.com/google_gmail/confirm` in the field." +#: ../../content/administration/maintain/google_oauth.rst:-1 +msgid "403 Access Denied Error." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:188 +msgid "To correct this error, return to the :guilabel:`OAuth consent screen` under :guilabel:`APIs & Services` and add test user(s) to the app. Add the email that you are configuring in Odoo." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:192 -msgid "Replace *yourdbname* in the URL with the Odoo database name." +msgid "Gmail Module not updated" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:194 +msgid "If the *Google Gmail* module in Odoo has not been updated to the latest version, then a :guilabel:`Forbidden` error message populates." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:-1 +msgid "Forbidden you don't have the permission to access the requested resource." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:201 +msgid "To correct this error, go to the :menuselection:`Apps` module and clear out the search terms. Then, search for `Gmail` or `Google` and upgrade the :guilabel:`Google Gmail` module. Finally, click on the three dots on the upper right of the module and select :guilabel:`Upgrade`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:206 +msgid "Application Type" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:208 +msgid "When creating the credentials (OAuth *Client ID* and *Client Secret*), if :guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an :guilabel:`Authorization Error` appears." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:-1 +msgid "Error 400 Redirect URI Mismatch." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:215 +msgid "To correct this error, delete the credentials already created and create new credentials, selecting :guilabel:`Web Application` for the :guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect URIs`, click :guilabel:`ADD URI` and type: `https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure to replace *yourdbname* in the URL with the Odoo database name." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:6 @@ -2538,222 +2618,188 @@ msgid "Odoo Online database management" msgstr "" #: ../../content/administration/maintain/odoo_online.rst:5 -msgid "To manage a database, sign in to https://www.odoo.com and access the `database management page `_ by clicking on the user icon, then on *My Databases*." +msgid "To manage a database, go to the `database manager `_ and sign in as the database administrator." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:None -msgid "Clicking on the user icon opens a drop-down menu. \"My databases\" button is highlighted." +#: ../../content/administration/maintain/odoo_online.rst:8 +msgid "All the main database management options are available by clicking the database name, except the upgrade option, which can be accessed by clicking the **arrow in a circle** icon next to the database name. It is only displayed if an upgrade is available." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:13 -msgid "Make sure you are connected as the administrator of the database you want to manage." +#: ../../content/administration/maintain/odoo_online.rst:-1 +msgid "Accessing the database management options" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:None -msgid "Clicking on the gear icon opens the drop-down menu." -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:19 -msgid "Open the drop-down menu next to the database you want to manage by clicking on the gear icon." -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:21 -msgid "Several actions are available:" -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:23 +#: ../../content/administration/maintain/odoo_online.rst:15 msgid ":ref:`odoo_online/upgrade`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:24 +#: ../../content/administration/maintain/odoo_online.rst:16 msgid ":ref:`odoo_online/duplicate`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:25 +#: ../../content/administration/maintain/odoo_online.rst:17 msgid ":ref:`odoo_online/rename`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:26 +#: ../../content/administration/maintain/odoo_online.rst:18 msgid ":ref:`odoo_online/download`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:27 +#: ../../content/administration/maintain/odoo_online.rst:19 msgid ":ref:`odoo_online/domains`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:28 +#: ../../content/administration/maintain/odoo_online.rst:20 msgid ":ref:`odoo_online/tags`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:29 +#: ../../content/administration/maintain/odoo_online.rst:21 msgid ":ref:`odoo_online/delete`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:30 +#: ../../content/administration/maintain/odoo_online.rst:22 msgid ":ref:`odoo_online/contact-support`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:31 +#: ../../content/administration/maintain/odoo_online.rst:23 msgid ":ref:`odoo_online/users`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:36 +#: ../../content/administration/maintain/odoo_online.rst:28 #: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:77 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 #: ../../content/administration/upgrade.rst:10 msgid "Upgrade" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:38 -msgid "If you are *not* on the latest **Online version**, you should receive an invitation to :doc:`upgrade <../upgrade>` your database. A **Rolling Release button** on your database's main screen proposes an upgrade to the latest version (e.g., 13.0 to 15.1)." +#: ../../content/administration/maintain/odoo_online.rst:30 +msgid "Trigger a database upgrade." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:0 -msgid "**If your Odoo database's version is lower than the latest major release:**" +#: ../../content/administration/maintain/odoo_online.rst:33 +msgid "For more information about the upgrade process, check out the :doc:`Odoo Online upgrade documentation <../upgrade/odoo_online>`." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:0 -msgid "You must upgrade your database within two months. After these two months, an automatic upgrade is initiated." -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:0 -msgid "**If your Odoo database's version is equal to or higher than the latest major release:**" -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:0 -msgid "You can disregard the invitation to upgrade as you probably wouldn't benefit from new features every two months." -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:51 -msgid "Versions that are not supported anymore become deprecated and need to be updated to avoid security issues. We recommend you initiate the upgrade of the database yourself, as this method allows you to request a test upgrade of your database to check for any discrepancies." -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:56 -msgid ":doc:`../upgrade`" -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:57 -msgid ":doc:`supported_versions`" -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:62 +#: ../../content/administration/maintain/odoo_online.rst:39 msgid "Duplicate" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:64 -msgid "Make an exact copy of the database to be able to perform testing without compromising the daily operations." +#: ../../content/administration/maintain/odoo_online.rst:41 +msgid "Create an exact copy of the database, which can be used to perform testing without compromising daily operations." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:68 -msgid "By checking *For testing purposes*, all external communication (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database." +#: ../../content/administration/maintain/odoo_online.rst:45 +msgid "By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:70 -msgid "Duplicate databases expire automatically after 15 days." +#: ../../content/administration/maintain/odoo_online.rst:47 +msgid "Duplicated databases expire automatically after 15 days." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:75 +#: ../../content/administration/maintain/odoo_online.rst:52 msgid "Rename" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:77 +#: ../../content/administration/maintain/odoo_online.rst:54 msgid "Rename the database and its URL." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:82 +#: ../../content/administration/maintain/odoo_online.rst:59 msgid "Download" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:84 -msgid "Download instantly a ZIP file with a backup of the database." +#: ../../content/administration/maintain/odoo_online.rst:61 +msgid "Download a ZIP file containing a backup of the database." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:87 -msgid "Databases are backed up daily according to the `Odoo Cloud SLA `_." +#: ../../content/administration/maintain/odoo_online.rst:64 +msgid "Databases are backed up daily as per the `Odoo Cloud Hosting SLA `_." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:93 -msgid "Domains" +#: ../../content/administration/maintain/odoo_online.rst:72 +msgid "Use a custom :doc:`domain name ` to access the database via another URL." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:95 -msgid "Configure custom domains to access the database via another URL." +#: ../../content/administration/maintain/odoo_online.rst:75 +msgid "You can :ref:`register a domain name for free `." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:98 -msgid ":doc:`domain_names`" -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:103 +#: ../../content/administration/maintain/odoo_online.rst:80 msgid "Tags" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:105 -msgid "Add tags to sort your databases out. You can search the tags in the search bar." +#: ../../content/administration/maintain/odoo_online.rst:82 +msgid "Add tags to easily identify and sort your databases." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:110 +#: ../../content/administration/maintain/odoo_online.rst:85 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:90 #: ../../content/administration/odoo_sh/getting_started/branches.rst:550 msgid "Delete" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:112 +#: ../../content/administration/maintain/odoo_online.rst:92 msgid "Delete a database instantly." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:115 -msgid "Deleting a database means that all data is permanently lost. The deletion is instant and for all users. It is recommended to create a backup of the database before deleting it." +#: ../../content/administration/maintain/odoo_online.rst:95 +msgid "Deleting a database means that all data is permanently lost. The deletion is instant and applies to all users. It is recommended to create a backup of the database before deleting it." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:118 -msgid "Read carefully the warning message that pops up and proceed only if you fully understand the implications of deleting a database:" +#: ../../content/administration/maintain/odoo_online.rst:98 +msgid "Carefully read the warning message and only proceed if the implications of deleting a database are fully understood." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:None -msgid "A warning message is prompted before deleting a database." +#: ../../content/administration/maintain/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:126 +#: ../../content/administration/maintain/odoo_online.rst:105 msgid "Only an administrator can delete a database." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:127 -msgid "The database name is immediately available for a new database." +#: ../../content/administration/maintain/odoo_online.rst:106 +msgid "The database name is immediately made available to anyone." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:128 -msgid "It is not possible to delete a database if it is expired or linked to a subscription. If needed, please get in touch with `Odoo Support `_." +#: ../../content/administration/maintain/odoo_online.rst:107 +msgid "Deleting a database if it has expired or is linked to a subscription is impossible. In that case, contact `Odoo Support `_." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:130 -msgid "To delete your account, please get in touch with `Odoo Support `_." +#: ../../content/administration/maintain/odoo_online.rst:113 +msgid "Contact us" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:135 -msgid "Contact Support" +#: ../../content/administration/maintain/odoo_online.rst:115 +msgid "Access the `Odoo.com support page `_ with the database's details already pre-filled." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:137 -msgid "Access the Odoo `support page `_ with your database's details already pre-filled." +#: ../../content/administration/maintain/odoo_online.rst:121 +msgid "Invite / remove users" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:143 -msgid "Invite / Remove Users" +#: ../../content/administration/maintain/odoo_online.rst:123 +msgid "To invite users, fill out the new user's email address and click :guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:145 -msgid "To invite users, fill out the email address of the new user and click on *Invite*. To add multiple users, click on *Add more users*." +#: ../../content/administration/maintain/odoo_online.rst:-1 +msgid "Inviting a user on a database" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:None -msgid "Clicking on \"Add more users\" adds additional email fields." +#: ../../content/administration/maintain/odoo_online.rst:129 +msgid "To remove users, select them and click :guilabel:`Remove`." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:152 -msgid "To remove users, select the users to remove and click on *Remove*." +#: ../../content/administration/maintain/odoo_online.rst:132 +msgid ":doc:`../../applications/general/users/manage_users`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:155 -msgid ":doc:`/applications/general/users/manage_users`" +#: ../../content/administration/maintain/odoo_online.rst:133 +msgid ":doc:`../../applications/general/users/delete_account`" msgstr "" #: ../../content/administration/maintain/on_premise.rst:3 @@ -2776,7 +2822,7 @@ msgstr "" msgid "If you are unable to register your database, you will likely encounter this message:" msgstr "" -#: ../../content/administration/maintain/on_premise.rst:None +#: ../../content/administration/maintain/on_premise.rst:-1 msgid "Something went wrong while registering your database, you can try again or contact Odoo\n" "Help" msgstr "" @@ -2860,7 +2906,7 @@ msgstr "" msgid "If you have more users in your local database than provisionned in your Odoo Enterprise subscription, you may encounter this message:" msgstr "" -#: ../../content/administration/maintain/on_premise.rst:None +#: ../../content/administration/maintain/on_premise.rst:-1 msgid "This database will expire in X days, you have more users than your subscription allows" msgstr "" @@ -2888,7 +2934,7 @@ msgstr "" msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:" msgstr "" -#: ../../content/administration/maintain/on_premise.rst:None +#: ../../content/administration/maintain/on_premise.rst:-1 msgid "This database has expired." msgstr "" @@ -2965,270 +3011,342 @@ msgstr "" msgid "**Major releases are in bold type.**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:27 +#: ../../content/administration/maintain/supported_versions.rst:33 #: ../../content/administration/upgrade/on_premise.rst:3 msgid "On-Premise" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:27 +#: ../../content/administration/maintain/supported_versions.rst:34 msgid "Release date" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:27 +#: ../../content/administration/maintain/supported_versions.rst:35 msgid "End of support" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:29 -msgid "**Odoo 16.0**" +#: ../../content/administration/maintain/supported_versions.rst:36 +msgid "Odoo saas~16.3" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:29 -#: ../../content/administration/maintain/supported_versions.rst:29 -#: ../../content/administration/maintain/supported_versions.rst:29 -#: ../../content/administration/maintain/supported_versions.rst:31 -#: ../../content/administration/maintain/supported_versions.rst:35 -#: ../../content/administration/maintain/supported_versions.rst:35 -#: ../../content/administration/maintain/supported_versions.rst:35 -#: ../../content/administration/maintain/supported_versions.rst:37 -#: ../../content/administration/maintain/supported_versions.rst:37 #: ../../content/administration/maintain/supported_versions.rst:37 +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:56 +#: ../../content/administration/maintain/supported_versions.rst:57 +#: ../../content/administration/maintain/supported_versions.rst:73 +#: ../../content/administration/maintain/supported_versions.rst:74 +#: ../../content/administration/maintain/supported_versions.rst:75 +#: ../../content/administration/maintain/supported_versions.rst:79 +#: ../../content/administration/maintain/supported_versions.rst:80 +#: ../../content/administration/maintain/supported_versions.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:62 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:67 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:82 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:99 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:107 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:119 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:122 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:127 msgid "|green|" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/maintain/supported_versions.rst:38 #: ../../content/administration/maintain/supported_versions.rst:39 -msgid "October 2022" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:29 -msgid "October 2025 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:31 -msgid "Odoo saas~15.2" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:31 -#: ../../content/administration/maintain/supported_versions.rst:31 -#: ../../content/administration/maintain/supported_versions.rst:33 -#: ../../content/administration/maintain/supported_versions.rst:33 -#: ../../content/administration/maintain/supported_versions.rst:41 -#: ../../content/administration/maintain/supported_versions.rst:41 +#: ../../content/administration/maintain/supported_versions.rst:44 #: ../../content/administration/maintain/supported_versions.rst:45 -#: ../../content/administration/maintain/supported_versions.rst:45 -#: ../../content/administration/maintain/supported_versions.rst:49 -#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:50 #: ../../content/administration/maintain/supported_versions.rst:51 -#: ../../content/administration/maintain/supported_versions.rst:51 -#: ../../content/administration/maintain/supported_versions.rst:55 -#: ../../content/administration/maintain/supported_versions.rst:55 -#: ../../content/administration/maintain/supported_versions.rst:57 -#: ../../content/administration/maintain/supported_versions.rst:59 -#: ../../content/administration/maintain/supported_versions.rst:59 -#: ../../content/administration/maintain/supported_versions.rst:61 +#: ../../content/administration/maintain/supported_versions.rst:62 +#: ../../content/administration/maintain/supported_versions.rst:63 +#: ../../content/administration/maintain/supported_versions.rst:68 +#: ../../content/administration/maintain/supported_versions.rst:69 +#: ../../content/administration/maintain/supported_versions.rst:92 +#: ../../content/administration/maintain/supported_versions.rst:93 +#: ../../content/administration/maintain/supported_versions.rst:104 +#: ../../content/administration/maintain/supported_versions.rst:105 +#: ../../content/administration/maintain/supported_versions.rst:116 +#: ../../content/administration/maintain/supported_versions.rst:117 +#: ../../content/administration/maintain/supported_versions.rst:122 +#: ../../content/administration/maintain/supported_versions.rst:123 +#: ../../content/administration/maintain/supported_versions.rst:134 +#: ../../content/administration/maintain/supported_versions.rst:135 +#: ../../content/administration/maintain/supported_versions.rst:140 +#: ../../content/administration/maintain/supported_versions.rst:146 +#: ../../content/administration/maintain/supported_versions.rst:147 +#: ../../content/administration/maintain/supported_versions.rst:152 msgid "N/A" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:31 -msgid "March 2022" +#: ../../content/administration/maintain/supported_versions.rst:40 +msgid "June 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:31 -msgid "January 2023" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:33 -msgid "Odoo saas~15.1" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:33 -#: ../../content/administration/maintain/supported_versions.rst:39 -#: ../../content/administration/maintain/supported_versions.rst:39 -#: ../../content/administration/maintain/supported_versions.rst:39 #: ../../content/administration/maintain/supported_versions.rst:41 -#: ../../content/administration/maintain/supported_versions.rst:43 -#: ../../content/administration/maintain/supported_versions.rst:43 -#: ../../content/administration/maintain/supported_versions.rst:43 -#: ../../content/administration/maintain/supported_versions.rst:45 -#: ../../content/administration/maintain/supported_versions.rst:47 -#: ../../content/administration/maintain/supported_versions.rst:47 +msgid "September 2023 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:42 +msgid "Odoo saas~16.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:46 +msgid "March 2023" +msgstr "" + #: ../../content/administration/maintain/supported_versions.rst:47 +msgid "July 2023 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:48 +msgid "Odoo saas~16.1" +msgstr "" + #: ../../content/administration/maintain/supported_versions.rst:49 -#: ../../content/administration/maintain/supported_versions.rst:51 -#: ../../content/administration/maintain/supported_versions.rst:53 -#: ../../content/administration/maintain/supported_versions.rst:53 -#: ../../content/administration/maintain/supported_versions.rst:53 -#: ../../content/administration/maintain/supported_versions.rst:55 -#: ../../content/administration/maintain/supported_versions.rst:57 -#: ../../content/administration/maintain/supported_versions.rst:57 -#: ../../content/administration/maintain/supported_versions.rst:59 -#: ../../content/administration/maintain/supported_versions.rst:61 #: ../../content/administration/maintain/supported_versions.rst:61 +#: ../../content/administration/maintain/supported_versions.rst:67 +#: ../../content/administration/maintain/supported_versions.rst:85 +#: ../../content/administration/maintain/supported_versions.rst:86 +#: ../../content/administration/maintain/supported_versions.rst:87 +#: ../../content/administration/maintain/supported_versions.rst:91 +#: ../../content/administration/maintain/supported_versions.rst:97 +#: ../../content/administration/maintain/supported_versions.rst:98 +#: ../../content/administration/maintain/supported_versions.rst:99 +#: ../../content/administration/maintain/supported_versions.rst:103 +#: ../../content/administration/maintain/supported_versions.rst:109 +#: ../../content/administration/maintain/supported_versions.rst:110 +#: ../../content/administration/maintain/supported_versions.rst:111 +#: ../../content/administration/maintain/supported_versions.rst:115 +#: ../../content/administration/maintain/supported_versions.rst:121 +#: ../../content/administration/maintain/supported_versions.rst:127 +#: ../../content/administration/maintain/supported_versions.rst:128 +#: ../../content/administration/maintain/supported_versions.rst:129 +#: ../../content/administration/maintain/supported_versions.rst:133 +#: ../../content/administration/maintain/supported_versions.rst:139 +#: ../../content/administration/maintain/supported_versions.rst:141 +#: ../../content/administration/maintain/supported_versions.rst:145 +#: ../../content/administration/maintain/supported_versions.rst:151 +#: ../../content/administration/maintain/supported_versions.rst:153 msgid "|red|" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:33 -msgid "February 2022" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:33 -msgid "July 2022" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:35 -msgid "**Odoo 15.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:35 -#: ../../content/administration/maintain/supported_versions.rst:43 -msgid "October 2021" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:35 -msgid "October 2024 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:37 -msgid "**Odoo 14.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:37 -#: ../../content/administration/maintain/supported_versions.rst:47 -msgid "October 2020" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:37 -msgid "October 2023 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:39 -msgid "**Odoo 13.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:39 -#: ../../content/administration/maintain/supported_versions.rst:53 -msgid "October 2019" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:41 -msgid "Odoo saas~12.3" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:41 -msgid "August 2019" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:43 -msgid "**Odoo 12.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:43 -#: ../../content/administration/maintain/supported_versions.rst:57 -msgid "October 2018" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:45 -msgid "Odoo saas~11.3" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:45 -msgid "April 2018" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:47 -msgid "**Odoo 11.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:47 -#: ../../content/administration/maintain/supported_versions.rst:61 -msgid "October 2017" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:49 -msgid "Odoo 10.saas~15" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:49 -msgid "March 2017" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:51 -msgid "Odoo 10.saas~14" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:51 -msgid "January 2017" +#: ../../content/administration/maintain/supported_versions.rst:52 +msgid "February 2023" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:53 -msgid "**Odoo 10.0**" +msgid "April 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:53 -msgid "October 2016" +#: ../../content/administration/maintain/supported_versions.rst:54 +msgid "**Odoo 16.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:55 -msgid "Odoo 9.saas~11" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:55 -msgid "May 2016" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:57 -msgid "**Odoo 9.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:57 -msgid "October 2015" +#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:89 +msgid "October 2022" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:59 -msgid "Odoo 8.saas~6" +msgid "October 2025 (planned)" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:59 -msgid "February 2015" +#: ../../content/administration/maintain/supported_versions.rst:60 +msgid "Odoo saas~15.2" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:61 -msgid "**Odoo 8.0**" +#: ../../content/administration/maintain/supported_versions.rst:64 +msgid "March 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:61 -msgid "September 2014" +#: ../../content/administration/maintain/supported_versions.rst:65 +msgid "January 2023" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:66 -msgid "|green| Supported version" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:68 -msgid "|red| End-of-support" +msgid "Odoo saas~15.1" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:70 -msgid "N/A Never released for this platform" +msgid "February 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:71 +msgid "July 2022" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:72 -msgid "🏁 Future version, not released yet" +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:76 +#: ../../content/administration/maintain/supported_versions.rst:101 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:77 +msgid "October 2024 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:78 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:82 +#: ../../content/administration/maintain/supported_versions.rst:113 +msgid "October 2020" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:83 +msgid "October 2023 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:84 +msgid "**Odoo 13.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:88 +#: ../../content/administration/maintain/supported_versions.rst:131 +msgid "October 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:90 +msgid "Odoo saas~12.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:94 +msgid "August 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:96 +msgid "**Odoo 12.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:100 +#: ../../content/administration/maintain/supported_versions.rst:143 +msgid "October 2018" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:102 +msgid "Odoo saas~11.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:106 +msgid "April 2018" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:108 +msgid "**Odoo 11.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:112 +#: ../../content/administration/maintain/supported_versions.rst:155 +msgid "October 2017" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:114 +msgid "Odoo 10.saas~15" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:118 +msgid "March 2017" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:120 +msgid "Odoo 10.saas~14" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:124 +msgid "January 2017" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:126 +msgid "**Odoo 10.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:130 +msgid "October 2016" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:132 +msgid "Odoo 9.saas~11" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:136 +msgid "May 2016" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:138 +msgid "**Odoo 9.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:142 +msgid "October 2015" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:144 +msgid "Odoo 8.saas~6" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:148 +msgid "February 2015" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:150 +msgid "**Odoo 8.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:154 +msgid "September 2014" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:159 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:161 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:163 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:165 +msgid "🏁 Future version, not released yet" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:176 msgid "I run an older version of Odoo/OpenERP/TinyERP" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:85 +#: ../../content/administration/maintain/supported_versions.rst:178 msgid "OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:87 +#: ../../content/administration/maintain/supported_versions.rst:180 msgid "TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:89 +#: ../../content/administration/maintain/supported_versions.rst:182 msgid "Even though we don't support older versions, you can always `upgrade from any version `_." msgstr "" @@ -3573,7 +3691,7 @@ msgstr "" msgid "Finally, *via* the Odoo Shell, you can trigger the piece of code/function/method you want to debug." msgstr "" -#: ../../content/administration/odoo_sh/advanced/containers.rst:None +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." msgstr "" @@ -3622,7 +3740,7 @@ msgid "Your scheduled actions should be `idempotent `." -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:112 -msgid "Configure the deploy keys for the private repositories you use as submodules in your branches to allow Odoo.sh to download them." -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 -msgid "These settings are required for **private repositories** only. If you are looking on how to set up your submodules, instructions are available in the chapter :ref:`Submodules ` of this documentation." -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 -msgid "When a repository is private, it is not possible to publicly download its branches and revisions. For that reason, you need to configure a deploy key for Odoo.sh, so the remote Git server allows our platform to download the revisions of this private repository." -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 -msgid "To configure the deploy key for a private repository, proceed as follows:" -msgstr "" - #: ../../content/administration/odoo_sh/getting_started/settings.rst:130 -msgid "in the input, paste the SSH URL of your private sub-repository and click on *Add*," -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 -msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 -msgid "it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted server" -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 -msgid "copy the public key," -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 -msgid "it should look like *ssh-rsa some...random...characters...here...==*" -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:140 -msgid "in the settings of the private sub-repository, add the public key amongst the deploy keys." -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:142 -msgid "Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 -msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:144 -msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgid "\\* Only in staging branches" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:145 -msgid "Self-hosted: append the key to the git user’s authorized_keys file in its .ssh directory" +msgid "Public Access" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 -msgid "Storage Size" +#: ../../content/administration/odoo_sh/getting_started/settings.rst:147 +msgid "Allow public access to your development builds." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:150 -msgid "This section shows the storage size used by your project." +#: ../../content/administration/odoo_sh/getting_started/settings.rst:152 +msgid "If activated, this option exposes the Builds page publicly, allowing visitors to connect to your development builds." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:155 -msgid "Storage size is computed as follows:" +msgid "In addition, visitors have access to the logs, shell and mails of your development builds." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:157 -msgid "the size of the PostgreSQL database" -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/settings.rst:159 -msgid "the size of the disk files available in your container: database filestore, sessions storage directory..." +msgid "Production and staging builds are excluded, visitors can only see their status." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:162 -msgid "In case you want to analyze disk usage, you can run the tool `ncdu `_ in your Web Shell." +msgid "Custom domains" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:165 -msgid "Should your production database size grow to exceed what's provisioned in your subscription, it will automatically be synchronized with it." +#: ../../content/administration/odoo_sh/getting_started/settings.rst:164 +msgid "To configure additional domains please refer to the corresponding branch's :ref:`settings tab `." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:169 -msgid "Database Workers" +#: ../../content/administration/odoo_sh/getting_started/settings.rst:172 +msgid "Configure the deploy keys for the private repositories you use as submodules in your branches to allow Odoo.sh to download them." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 -msgid "Additional database workers can be configured here. More workers help increase the load your production database is able to handle. If you add more, it will automatically be synchronized with your subscription." +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +msgid "These settings are required for **private repositories** only. If you are looking on how to set up your submodules, instructions are available in the chapter :ref:`Submodules ` of this documentation." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 -msgid "Adding more workers will not magically solve all performance issues. It only allows the server to handle more connections at the same time. If some operations are unusually slow, it's most likely a problem with the code, if it's not due to your own customizations you can open a ticket `here `_." +#: ../../content/administration/odoo_sh/getting_started/settings.rst:183 +msgid "When a repository is private, it is not possible to publicly download its branches and revisions. For that reason, you need to configure a deploy key for Odoo.sh, so the remote Git server allows our platform to download the revisions of this private repository." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:185 -msgid "Staging Branches" +#: ../../content/administration/odoo_sh/getting_started/settings.rst:188 +msgid "To configure the deploy key for a private repository, proceed as follows:" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:187 -msgid "Additional staging branches allow you to develop and test more features at the same time. If you add more, it will automatically be synchronized with your subscription." +#: ../../content/administration/odoo_sh/getting_started/settings.rst:190 +msgid "in the input, paste the SSH URL of your private sub-repository and click on *Add*," msgstr "" -#: ../../content/administration/odoo_sh/getting_started/settings.rst:194 -msgid "Activation" +#: ../../content/administration/odoo_sh/getting_started/settings.rst:192 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:193 +msgid "it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted server" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:196 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:198 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:200 +msgid "in the settings of the private sub-repository, add the public key amongst the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:202 +msgid "Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:203 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:204 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:205 +msgid "Self-hosted: append the key to the git user’s authorized_keys file in its .ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:208 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:210 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:215 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:217 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:219 +msgid "the size of the disk files available in your container: database filestore, sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:222 +msgid "In case you want to analyze disk usage, you can run the tool `ncdu `_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:225 +msgid "Should your production database size grow to exceed what's provisioned in your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:231 +msgid "Additional database workers can be configured here. More workers help increase the load your production database is able to handle. If you add more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:239 +msgid "Adding more workers will not magically solve all performance issues. It only allows the server to handle more connections at the same time. If some operations are unusually slow, it's most likely a problem with the code, if it's not due to your own customizations you can open a ticket `here `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:245 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:247 +msgid "Additional staging branches allow you to develop and test more features at the same time. If you add more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:254 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:256 msgid "Shows the status of the project's activation. You can change the project's activation code if needed." msgstr "" @@ -5674,7 +5770,7 @@ msgstr "" #: ../../content/administration/upgrade.rst:29 #: ../../content/administration/upgrade.rst:148 -#: ../../content/administration/upgrade.rst:252 +#: ../../content/administration/upgrade.rst:259 #: ../../content/administration/upgrade/faq.rst:81 #: ../../content/administration/upgrade/faq.rst:92 #: ../../content/administration/upgrade/faq.rst:119 @@ -5805,7 +5901,7 @@ msgstr "" msgid "Follow the instructions available per hosting type on the `website form `_ and select *Testing* purpose." msgstr "" -#: ../../content/administration/upgrade.rst:None +#: ../../content/administration/upgrade.rst:-1 msgid "Selection of the \"Testing\" purpose in the upgrade form on Odoo" msgstr "" @@ -5900,7 +5996,7 @@ msgid "Help" msgstr "" #: ../../content/administration/upgrade.rst:200 -msgid "Contact our Upgrade service support" +msgid "Contact our upgrade service support" msgstr "" #: ../../content/administration/upgrade.rst:202 @@ -5916,72 +6012,79 @@ msgid "This is a factor to take into consideration before upgrading. If you are msgstr "" #: ../../content/administration/upgrade.rst:218 -#: ../../content/administration/upgrade.rst:257 msgid ":doc:`maintain/supported_versions`" msgstr "" #: ../../content/administration/upgrade.rst:223 -msgid "Service Level Agreement" +msgid "Service-level agreement (SLA)" msgstr "" -#: ../../content/administration/upgrade.rst:226 -msgid "What is covered by the Enterprise Licence?" +#: ../../content/administration/upgrade.rst:225 +msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database." msgstr "" #: ../../content/administration/upgrade.rst:228 -msgid "Databases hosted on Odoo's Cloud platforms (Odoo Online and Odoo.sh) or On-Premise (Self-Hosting) enjoy the following services at all times." -msgstr "" - -#: ../../content/administration/upgrade.rst:231 -msgid "The upgrade of:" +msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement `. However, this section clarifies what upgrade services you can expect." msgstr "" #: ../../content/administration/upgrade.rst:233 -msgid "standard applications" -msgstr "" - -#: ../../content/administration/upgrade.rst:234 -msgid "Studio customization (as long as the :guilabel:`Studio` app is still active)" +msgid "Upgrade services covered by the SLA" msgstr "" #: ../../content/administration/upgrade.rst:235 -msgid "customizations *if* they are covered by a \"Maintenance of Customizations\" subscription" +msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:" msgstr "" -#: ../../content/administration/upgrade.rst:237 -msgid "The Upgrade Service is limited to your database's technical conversion and adaptation (standard modules and data) to make it compatible with the targeted version." +#: ../../content/administration/upgrade.rst:238 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and" msgstr "" #: ../../content/administration/upgrade.rst:241 -msgid "What upgrading does NOT cover" -msgstr "" - -#: ../../content/administration/upgrade.rst:243 -msgid "The cleaning of pre-existing data & configuration while upgrading" +msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." msgstr "" #: ../../content/administration/upgrade.rst:244 -msgid "Any new developments and/or upgrades of your own :ref:`custom modules `" +msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade." msgstr "" -#: ../../content/administration/upgrade.rst:246 -msgid "Lines of code added to standard modules that are not created with Odoo Studio." +#: ../../content/administration/upgrade.rst:248 +msgid "Upgrade services not covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:247 -msgid "`Training `_ on the latest version" +#: ../../content/administration/upgrade.rst:250 +msgid "The following upgrade-related services are **not** included:" msgstr "" -#: ../../content/administration/upgrade.rst:249 -msgid "You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription Agreement ` page." +#: ../../content/administration/upgrade.rst:252 +msgid "the **cleaning** of pre-existing data and configurations while upgrading;" msgstr "" -#: ../../content/administration/upgrade.rst:255 -msgid ":doc:`upgrade/faq`" +#: ../../content/administration/upgrade.rst:253 +msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" msgstr "" -#: ../../content/administration/upgrade.rst:256 -msgid ":doc:`odoo_sh`" +#: ../../content/administration/upgrade.rst:254 +msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code `; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:262 +msgid ":doc:`Upgrade FAQ `" +msgstr "" + +#: ../../content/administration/upgrade.rst:263 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +msgid ":doc:`Supported Odoo versions `" msgstr "" #: ../../content/administration/upgrade/faq.rst:8 @@ -6252,44 +6355,92 @@ msgstr "" msgid "If you are using the Website or Studio app, we recommend you always do a test upgrade before upgrading your production instance." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:6 -msgid "Requesting a test upgrade" +#: ../../content/administration/upgrade/odoo_online.rst:5 +msgid "Odoo databases can be manually upgraded directly from the main Odoo website. To upgrade an Odoo database, navigate to the `database manager `_ page and sign in." msgstr "" #: ../../content/administration/upgrade/odoo_online.rst:8 -msgid "Go to your `database manager `_" +msgid "The database manager page displays all of the Odoo databases associated with the user's account. Any databases that are not already on the most recent version of Odoo display an **arrow in a circle** icon next to the database name, indicating that the database can be upgraded." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:9 -msgid "Click on your profile icon and select *My Databases*." +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "The database manager page with an upgrade button next to the name of a database." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:0 -msgid "Selecting My Databases under my profile" -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:14 -msgid "Click on the up arrow button next to your main database name to proceed to the test upgrade." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:0 -msgid "Selecting the action settings icon" +#: ../../content/administration/upgrade/odoo_online.rst:17 +msgid "If the database's version is **lower** than the latest major release: the database must be upgraded within two months. After these two months, an automatic upgrade is initiated." msgstr "" #: ../../content/administration/upgrade/odoo_online.rst:19 -msgid "In the pop-up message that appears, select the target version and then :guilabel:`Test` as purpose." +msgid "If the database's version is **equal** to or **higher** than the latest major release: you can disregard the invitation to upgrade, as the database probably would not benefit from new features every two months." msgstr "" #: ../../content/administration/upgrade/odoo_online.rst:23 -msgid "The :guilabel:`Production` purpose doesn't appear if you didn't test your upgraded database at least once." +msgid "If a database is *not* on the latest online version, its administrator should receive an invitation to upgrade on the database's dashboard, displayed as an **arrow in a circle**." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:26 -msgid "This triggers the automated upgrade process. A confirmation email is then sent to you with the the link to the upgraded database or to provide information if the upgrade failed." +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "Invitation to upgrade on the database dashboard." msgstr "" #: ../../content/administration/upgrade/odoo_online.rst:30 -msgid "You can also see and access your test database from your *My Databases* page." +msgid "Versions that are not supported anymore become deprecated and must be updated to avoid security issues. It is recommended to initiate the upgrade yourself and not wait for the automatic upgrade, as the former method allows you to request a test upgrade of the database to check for any discrepancies." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:36 +msgid "Test database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:38 +msgid "Click on the **arrow in a circle** icon to start the upgrade process. On the :guilabel:`Upgrade your database` pop-up, select the version of Odoo that the platform will be upgraded to. In the :guilabel:`Email to notify` field, enter an email address that will receive email notifications about the database upgrade." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:43 +msgid "There is also a :guilabel:`Purpose` section on the pop-up that is used to specify the reason for the upgrade. However, at this stage of the process, the only selectable option is :guilabel:`Test`, as Odoo requires users to create a test copy of the upgraded database before converting the actual database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "The \"Upgrade your database\" pop-up." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:52 +msgid "After filling out the form, click the :guilabel:`Upgrade` button. The pop-up disappears and the database being upgraded shows a red :guilabel:`Upgrade in progress` tag next to its name. An email confirming that the upgrade is in progress is also sent to the email address specified on the pop-up." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "The \"Upgrade in progress\" tag next to the database name." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:61 +msgid "Once the upgrade is complete, a new test database appears on the `database manager `_ page. To access the test database, click the drop-down arrow (:guilabel:`⯆`) to the left of the main database's name. Doing so makes the test version appear below it. Finally, click the green :guilabel:`Connect` button on the right side of the test version's row to go to the database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "A test database on the database manager page." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:71 +msgid "Except for being on the newer version of Odoo, the test database is an exact copy of the one being upgraded. It is important to do extensive testing in this database to ensure that the upgrade has not altered or corrupted any data, and that all workflows still proceed as expected." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:76 +msgid "Production database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:78 +msgid "After confirming the integrity of the new version, return to the `database manager `_ page. Once again, click on the **arrow in a circle** icon next to the database being upgraded. The :guilabel:`Upgrade your database` pop-up appears as before, except that there is now a :guilabel:`Production` option under the :guilabel:`Purpose` section." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:83 +msgid "Select the :guilabel:`Production` option and then click :guilabel:`Upgrade` to begin the upgrade process. As before, a notification email is sent to the email address provided and a red :guilabel:`Upgrade in progress` tag appears next to the name of the database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:87 +msgid "The production database is then taken offline and will be upgraded automatically. The time it takes to upgrade the production database should be similar to the time that was necessary to upgrade the test database. Make sure to inform database users of the scheduled downtime." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:91 +msgid "After the upgrade is finished, the :guilabel:`Upgrade in progress` tag disappears and the database is upgraded to the version specified." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:10 @@ -6300,7 +6451,7 @@ msgstr "" msgid "The :guilabel:`Upgrade` tab is available in the branches view. It is only available for valid projects with a valid production build." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:None +#: ../../content/administration/upgrade/odoo_sh.rst:-1 msgid "Click on the upgrade menu" msgstr "" @@ -6356,7 +6507,7 @@ msgstr "" msgid "Go to the :guilabel:`Upgrade` tab and select the :guilabel:`target version`. Then, click on :guilabel:`Test Upgrade`." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:None +#: ../../content/administration/upgrade/odoo_sh.rst:-1 msgid "Odoo.sh project and tabs" msgstr "" @@ -6405,7 +6556,7 @@ msgstr "" msgid "On your :guilabel:`Production` branch, go to the :guilabel:`Upgrade` tab, select the :guilabel:`targeted version` and click on the :guilabel:`start Upgrade` button." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:None +#: ../../content/administration/upgrade/odoo_sh.rst:-1 msgid "View from the upgrade tab" msgstr "" @@ -6417,7 +6568,7 @@ msgstr "" msgid "You can see the progress of the upgrade by going to the :guilabel:`Upgrade` tab of the main branch." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:None +#: ../../content/administration/upgrade/odoo_sh.rst:-1 msgid "View showing the progress of the upgrade" msgstr "" diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot index db4d39d39..b51ede838 100644 --- a/locale/sources/contributing.pot +++ b/locale/sources/contributing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-01-03 07:53+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -153,28 +153,21 @@ msgstr "" msgid "It is mainly Odoo employees who develop new features for the codebase and write new content for the documentation. Be sure to discuss any idea for a new feature or page with the Odoo team so they can give you the green light before you begin working on it. Some features may already be in development on their side, and only approved features can be merged." msgstr "" -#: ../../content/contributing/check_mergeability_status.rst:1 -#: ../../content/contributing/check_mergeability_status.rst:1 -#: ../../content/contributing/check_mergeability_status.rst:1 -#: ../../content/contributing/check_mergeability_status.rst:1 #: ../../content/contributing/check_mergeability_status.rst:1 #: ../../content/contributing/check_mergeability_status.rst:1 msgid "At the bottom of the page, check the mergeability status and address any issues." msgstr "" -#: ../../content/contributing/configure_git_authorship.rst:1 #: ../../content/contributing/configure_git_authorship.rst:1 #: ../../content/contributing/configure_git_authorship.rst:1 msgid "Configure Git to identify yourself as the author of your future contributions. Enter the same email address you used to register on GitHub." msgstr "" -#: ../../content/contributing/configure_github_account.rst:1 #: ../../content/contributing/configure_github_account.rst:1 #: ../../content/contributing/configure_github_account.rst:1 msgid "`Generate a new SSH key and register it on your GitHub account `_." msgstr "" -#: ../../content/contributing/create_github_account.rst:1 #: ../../content/contributing/create_github_account.rst:1 #: ../../content/contributing/create_github_account.rst:1 msgid "First, you need to `create a GitHub account `_. Odoo uses GitHub to manage the source code of its products, and this is where you will make your changes and submit them for review." @@ -210,43 +203,37 @@ msgstr "" msgid "Go to `github.com/odoo/odoo `_ and click on the :guilabel:`Fork` button in the top right corner to create a fork (:dfn:`your own copy`) of the repository on your account. Do the same with `github.com/odoo/enterprise `_ if you have access to it. This creates a copy of the codebase to which you can make changes without affecting the main codebase. Skip this step if you work at Odoo." msgstr "" -#: ../../content/contributing/install_git.rst:1 #: ../../content/contributing/install_git.rst:1 #: ../../content/contributing/install_git.rst:1 msgid "`Install Git `_. It is a command-line (:dfn:`a text interface`) tool that allows tracking the history of changes made to a file and, more importantly, working on different versions of that file simultaneously. It means you do not need to worry about overwriting someone else’s pending work when making changes." msgstr "" -#: ../../content/contributing/install_git.rst:6 #: ../../content/contributing/install_git.rst:6 #: ../../content/contributing/install_git.rst:6 msgid "Verify that the installation directory of Git is included in your system's `PATH` variable." msgstr "" -#: ../../content/contributing/install_git.rst:10 -#: ../../content/contributing/install_git.rst:10 #: ../../content/contributing/documentation.rst:97 #: ../../content/contributing/documentation.rst:124 #: ../../content/contributing/documentation.rst:140 #: ../../content/contributing/install_git.rst:10 +#: ../../content/contributing/install_git.rst:10 msgid "Linux and macOS" msgstr "" -#: ../../content/contributing/install_git.rst:12 #: ../../content/contributing/install_git.rst:12 #: ../../content/contributing/install_git.rst:12 msgid "Follow the `guide to update the PATH variable on Linux and macOS `_ with the installation path of Git (by default :file:`/usr/bin/git`)." msgstr "" -#: ../../content/contributing/install_git.rst:16 -#: ../../content/contributing/install_git.rst:16 #: ../../content/contributing/documentation.rst:104 #: ../../content/contributing/documentation.rst:130 #: ../../content/contributing/documentation.rst:146 #: ../../content/contributing/install_git.rst:16 +#: ../../content/contributing/install_git.rst:16 msgid "Windows" msgstr "" -#: ../../content/contributing/install_git.rst:18 #: ../../content/contributing/install_git.rst:18 #: ../../content/contributing/install_git.rst:18 msgid "Follow the `guide to update the PATH variable on Windows `_ with the installation path of Git (by default :file:`C:\\\\Program Files\\\\Git`)." @@ -268,129 +255,125 @@ msgstr "" msgid "In the command below, replace `` with the name of the GitHub account on which you created the fork(s)." msgstr "" -#: ../../content/contributing/development.rst:56 +#: ../../content/contributing/development.rst:57 msgid "If you have access to `odoo/enterprise`, configure the related remote too." msgstr "" -#: ../../content/contributing/development.rst:62 +#: ../../content/contributing/development.rst:64 msgid "Link Git with odoo-dev" msgstr "" -#: ../../content/contributing/development.rst:72 +#: ../../content/contributing/development.rst:76 msgid "That's it! You are ready to :ref:`make your first contribution `." msgstr "" -#: ../../content/contributing/development.rst:79 +#: ../../content/contributing/development.rst:82 #: ../../content/contributing/documentation.rst:158 msgid "Make your first contribution" msgstr "" -#: ../../content/contributing/development.rst:82 +#: ../../content/contributing/development.rst:85 msgid "Odoo development can be challenging for beginners. We recommend you to be knowledgeable enough to code a small module before contributing. If that is not the case, take some time to go through the :doc:`developer tutorials ` to fill in the gaps." msgstr "" -#: ../../content/contributing/development.rst:85 +#: ../../content/contributing/development.rst:88 #: ../../content/contributing/documentation.rst:204 msgid "Some steps of this guide require to be comfortable with Git. Here are some `tutorials `_ and an `interactive training `_ if you are stuck at some point." msgstr "" -#: ../../content/contributing/development.rst:89 +#: ../../content/contributing/development.rst:92 msgid "Now that your environment is set up, you can start contributing to the codebase. In a terminal, navigate to the directory where you installed Odoo from sources and follow the guide below." msgstr "" -#: ../../content/contributing/development.rst:92 +#: ../../content/contributing/development.rst:95 msgid "Choose the version of Odoo to which you want to make changes. Keep in mind that contributions targeting an :doc:`unsupported version of Odoo ` are not accepted. This guide assumes that the changes target Odoo 14, which corresponds to branch `14.0`." msgstr "" -#: ../../content/contributing/development.rst:96 +#: ../../content/contributing/development.rst:99 #: ../../content/contributing/documentation.rst:216 msgid "Create a new branch starting from branch 14.0. Prefix the branch name with the base branch: `14.0-...`. If you work at Odoo, suffix the branch name with your Odoo handle: `14.0-...-xyz`." msgstr "" -#: ../../content/contributing/development.rst:110 +#: ../../content/contributing/development.rst:113 msgid "`Sign the Odoo CLA `_ if not already done. Skip this step if you work at Odoo." msgstr "" -#: ../../content/contributing/development.rst:112 +#: ../../content/contributing/development.rst:115 msgid "Make the desired changes to the codebase. When working on the codebase, follow these rules:" msgstr "" -#: ../../content/contributing/development.rst:114 +#: ../../content/contributing/development.rst:117 msgid "Keep your changes focused and specific. It is best to work on one particular feature or bug fix at a time rather than tackle multiple unrelated changes simultaneously." msgstr "" -#: ../../content/contributing/development.rst:116 +#: ../../content/contributing/development.rst:119 msgid "Respect the `stable policy `_ when working in another branch than `master`." msgstr "" -#: ../../content/contributing/development.rst:119 +#: ../../content/contributing/development.rst:122 msgid "Follow the :doc:`coding guidelines `." msgstr "" -#: ../../content/contributing/development.rst:120 +#: ../../content/contributing/development.rst:123 msgid "Test your changes thoroughly and :doc:`write tests ` to ensure that everything is working as expected and that there are no regressions or unintended consequences." msgstr "" -#: ../../content/contributing/development.rst:124 +#: ../../content/contributing/development.rst:127 #: ../../content/contributing/documentation.rst:249 msgid "Commit your changes. Write a clear commit message as instructed in the :doc:`Git guidelines `." msgstr "" -#: ../../content/contributing/development.rst:132 +#: ../../content/contributing/development.rst:135 #: ../../content/contributing/documentation.rst:257 msgid "Push your change to your fork, for which we added the remote alias `dev`." msgstr "" -#: ../../content/contributing/development.rst:140 +#: ../../content/contributing/development.rst:143 #: ../../content/contributing/documentation.rst:274 msgid "Open a :abbr:`PR (Pull Request)` on GitHub to submit your changes for review." msgstr "" -#: ../../content/contributing/development.rst:142 +#: ../../content/contributing/development.rst:145 msgid "Go to the `compare page of the odoo/odoo codebase `_, or the `compare page of the odoo/enterprise codebase `_, depending on which codebase your changes target." msgstr "" -#: ../../content/contributing/development.rst:146 +#: ../../content/contributing/development.rst:149 #: ../../content/contributing/documentation.rst:278 msgid "Select **14.0** for the base." msgstr "" -#: ../../content/contributing/development.rst:147 +#: ../../content/contributing/development.rst:150 #: ../../content/contributing/documentation.rst:279 msgid "Click on :guilabel:`compare across forks`." msgstr "" -#: ../../content/contributing/development.rst:148 +#: ../../content/contributing/development.rst:151 msgid "Select **/odoo** or **/enterprise** for the head repository. Replace `` with the name of the GitHub account on which you created the fork or by **odoo-dev** if you work at Odoo." msgstr "" -#: ../../content/contributing/development.rst:151 +#: ../../content/contributing/development.rst:154 #: ../../content/contributing/documentation.rst:192 #: ../../content/contributing/documentation.rst:283 msgid "Review your changes and click on the :guilabel:`Create pull request` button." msgstr "" -#: ../../content/contributing/development.rst:152 +#: ../../content/contributing/development.rst:155 #: ../../content/contributing/documentation.rst:193 #: ../../content/contributing/documentation.rst:284 msgid "Tick the :guilabel:`Allow edits from maintainer` checkbox. Skip this step if you work at Odoo." msgstr "" -#: ../../content/contributing/development.rst:153 +#: ../../content/contributing/development.rst:156 #: ../../content/contributing/documentation.rst:286 msgid "Complete the description and click on the :guilabel:`Create pull request` button again." msgstr "" -#: ../../content/contributing/handle_reviews.rst:1 -#: ../../content/contributing/handle_reviews.rst:1 -#: ../../content/contributing/handle_reviews.rst:1 -#: ../../content/contributing/handle_reviews.rst:1 #: ../../content/contributing/handle_reviews.rst:1 #: ../../content/contributing/handle_reviews.rst:1 msgid "As soon as your :abbr:`PR (Pull Request)` is ready for merging, a member of the Odoo team will be automatically assigned for review. If the reviewer has questions or remarks, they will post them as comments and you will be notified by email. Those comments must be resolved for the contribution to go forward." msgstr "" -#: ../../content/contributing/development.rst:157 +#: ../../content/contributing/development.rst:160 msgid "Once your changes are approved, the review merges them and they become available for all Odoo users after the next code update!" msgstr "" @@ -418,714 +401,714 @@ msgstr "" msgid "Directories" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:33 +#: ../../content/contributing/development/coding_guidelines.rst:34 msgid "A module is organized in important directories. Those contain the business logic; having a look at them should make you understand the purpose of the module." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:36 +#: ../../content/contributing/development/coding_guidelines.rst:37 msgid "*data/* : demo and data xml" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:37 +#: ../../content/contributing/development/coding_guidelines.rst:38 msgid "*models/* : models definition" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:38 +#: ../../content/contributing/development/coding_guidelines.rst:39 msgid "*controllers/* : contains controllers (HTTP routes)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:39 +#: ../../content/contributing/development/coding_guidelines.rst:40 msgid "*views/* : contains the views and templates" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:40 +#: ../../content/contributing/development/coding_guidelines.rst:41 msgid "*static/* : contains the web assets, separated into *css/, js/, img/, lib/, ...*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:42 +#: ../../content/contributing/development/coding_guidelines.rst:43 msgid "Other optional directories compose the module." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:44 +#: ../../content/contributing/development/coding_guidelines.rst:45 msgid "*wizard/* : regroups the transient models (``models.TransientModel``) and their views" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:45 +#: ../../content/contributing/development/coding_guidelines.rst:46 msgid "*report/* : contains the printable reports and models based on SQL views. Python objects and XML views are included in this directory" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:46 +#: ../../content/contributing/development/coding_guidelines.rst:47 msgid "*tests/* : contains the Python tests" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:50 +#: ../../content/contributing/development/coding_guidelines.rst:51 msgid "File naming" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:52 +#: ../../content/contributing/development/coding_guidelines.rst:53 msgid "File naming is important to quickly find information through all odoo addons. This section explains how to name files in a standard odoo module. As an example we use a `plant nursery `_ application. It holds two main models *plant.nursery* and *plant.order*." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:57 +#: ../../content/contributing/development/coding_guidelines.rst:58 msgid "Concerning *models*, split the business logic by sets of models belonging to a same main model. Each set lies in a given file named based on its main model. If there is only one model, its name is the same as the module name. Each inherited model should be in its own file to help understanding of impacted models." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:71 +#: ../../content/contributing/development/coding_guidelines.rst:72 msgid "Concerning *security*, three main files should be used:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:73 +#: ../../content/contributing/development/coding_guidelines.rst:74 msgid "First one is the definition of access rights done in a :file:`ir.model.access.csv` file." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:74 +#: ../../content/contributing/development/coding_guidelines.rst:75 msgid "User groups are defined in :file:`_groups.xml`." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:75 +#: ../../content/contributing/development/coding_guidelines.rst:76 msgid "Record rules are defined in :file:`_security.xml`." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:86 +#: ../../content/contributing/development/coding_guidelines.rst:87 msgid "Concerning *views*, backend views should be split like models and suffixed by ``_views.xml``. Backend views are list, form, kanban, activity, graph, pivot, .. views. To ease split by model in views main menus not linked to specific actions may be extracted into an optional ``_menus.xml`` file. Templates (QWeb pages used notably for portal / website display) and bundles (import of JS and CSS assets) are put in separate files. Those are respectively ``_templates.xml`` and ``assets.xml`` files." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:106 +#: ../../content/contributing/development/coding_guidelines.rst:107 msgid "Concerning *data*, split them by purpose (demo or data) and main model. Filenames will be the main_model name suffixed by ``_demo.xml`` or ``_data.xml``. For instance for an application having demo and data for its main model as well as subtypes, activities and mail templates all related to mail module:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:119 +#: ../../content/contributing/development/coding_guidelines.rst:120 msgid "Concerning *controllers*, generally all controllers belong to a single controller contained in a file named ``.py``. An old convention in Odoo is to name this file ``main.py`` but it is considered as outdated. If you need to inherit an existing controller from another module do it in ``.py``. For example adding portal controller in an application is done in ``portal.py``." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:133 +#: ../../content/contributing/development/coding_guidelines.rst:134 msgid "Concerning *static files*, Javascript files follow globally the same logic as python models. Each component should be in its own file with a meaningful name. For instance, the activity widgets are located in ``activity.js`` of mail module. Subdirectories can also be created to structure the 'package' (see web module for more details). The same logic should be applied for the templates of JS widgets (static XML files) and for their styles (scss files). Don't link data (image, libraries) outside Odoo: do not use an URL to an image but copy it in the codebase instead." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:142 +#: ../../content/contributing/development/coding_guidelines.rst:143 msgid "Concerning *wizards*, naming convention is the same of for python models: ``.py`` and ``_views.xml``. Both are put in the wizard directory. This naming comes from old odoo applications using the wizard keyword for transient models." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:154 +#: ../../content/contributing/development/coding_guidelines.rst:155 msgid "Concerning *statistics reports* done with python / SQL views and classic views naming is the following :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:164 +#: ../../content/contributing/development/coding_guidelines.rst:165 msgid "Concerning *printable reports* which contain mainly data preparation and Qweb templates naming is the following :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:174 +#: ../../content/contributing/development/coding_guidelines.rst:175 msgid "The complete tree of our Odoo module therefore looks like" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:233 +#: ../../content/contributing/development/coding_guidelines.rst:234 msgid "File names should only contain ``[a-z0-9_]`` (lowercase alphanumerics and ``_``)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:236 +#: ../../content/contributing/development/coding_guidelines.rst:237 msgid "Use correct file permissions : folder 755 and file 644." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:241 +#: ../../content/contributing/development/coding_guidelines.rst:242 msgid "XML files" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:244 +#: ../../content/contributing/development/coding_guidelines.rst:245 msgid "Format" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:245 +#: ../../content/contributing/development/coding_guidelines.rst:247 msgid "To declare a record in XML, the **record** notation (using **) is recommended:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:247 +#: ../../content/contributing/development/coding_guidelines.rst:249 msgid "Place ``id`` attribute before ``model``" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:248 +#: ../../content/contributing/development/coding_guidelines.rst:250 msgid "For field declaration, ``name`` attribute is first. Then place the *value* either in the ``field`` tag, either in the ``eval`` attribute, and finally other attributes (widget, options, ...) ordered by importance." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:253 +#: ../../content/contributing/development/coding_guidelines.rst:255 msgid "Try to group the record by model. In case of dependencies between action/menu/views, this convention may not be applicable." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:255 +#: ../../content/contributing/development/coding_guidelines.rst:257 msgid "Use naming convention defined at the next point" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:256 +#: ../../content/contributing/development/coding_guidelines.rst:258 msgid "The tag ** is only used to set not-updatable data with ``noupdate=1``. If there is only not-updatable data in the file, the ``noupdate=1`` can be set on the ```` tag and do not set a ```` tag." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:274 +#: ../../content/contributing/development/coding_guidelines.rst:276 msgid "Odoo supports custom tags acting as syntactic sugar:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:276 +#: ../../content/contributing/development/coding_guidelines.rst:278 msgid "menuitem: use it as a shortcut to declare a ``ir.ui.menu``" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:277 +#: ../../content/contributing/development/coding_guidelines.rst:279 msgid "template: use it to declare a QWeb View requiring only the ``arch`` section of the view." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:279 +#: ../../content/contributing/development/coding_guidelines.rst:281 msgid "These tags are preferred over the *record* notation." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:283 +#: ../../content/contributing/development/coding_guidelines.rst:285 msgid "XML IDs and naming" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:286 +#: ../../content/contributing/development/coding_guidelines.rst:288 msgid "Security, View and Action" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:288 +#: ../../content/contributing/development/coding_guidelines.rst:290 msgid "Use the following pattern :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:290 +#: ../../content/contributing/development/coding_guidelines.rst:292 msgid "For a menu: :samp:`{}_menu`, or :samp:`{}_menu_{do_stuff}` for submenus." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:291 +#: ../../content/contributing/development/coding_guidelines.rst:293 msgid "For a view: :samp:`{}_view_{}`, where *view_type* is ``kanban``, ``form``, ``tree``, ``search``, ..." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:293 +#: ../../content/contributing/development/coding_guidelines.rst:295 msgid "For an action: the main action respects :samp:`{}_action`. Others are suffixed with :samp:`_{}`, where *detail* is a lowercase string briefly explaining the action. This is used only if multiple actions are declared for the model." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:297 +#: ../../content/contributing/development/coding_guidelines.rst:299 msgid "For window actions: suffix the action name by the specific view information like :samp:`{}_action_view_{}`." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:299 +#: ../../content/contributing/development/coding_guidelines.rst:301 msgid "For a group: :samp:`{}_group_{}` where *group_name* is the name of the group, generally 'user', 'manager', ..." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:301 +#: ../../content/contributing/development/coding_guidelines.rst:303 msgid "For a rule: :samp:`{}_rule_{}` where *concerned_group* is the short name of the concerned group ('user' for the 'model_name_group_user', 'public' for public user, 'company' for multi-company rules, ...)." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:306 +#: ../../content/contributing/development/coding_guidelines.rst:308 msgid "Name should be identical to xml id with dots replacing underscores. Actions should have a real naming as it is used as display name." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:360 +#: ../../content/contributing/development/coding_guidelines.rst:362 msgid "Inheriting XML" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:362 +#: ../../content/contributing/development/coding_guidelines.rst:364 msgid "Xml Ids of inheriting views should use the same ID as the original record. It helps finding all inheritance at a glance. As final Xml Ids are prefixed by the module that creates them there is no overlap." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:366 +#: ../../content/contributing/development/coding_guidelines.rst:368 msgid "Naming should contain an ``.inherit.{details}`` suffix to ease understanding the override purpose when looking at its name." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:377 +#: ../../content/contributing/development/coding_guidelines.rst:379 msgid "New primary views do not require the inherit suffix as those are new records based upon the first one." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:392 +#: ../../content/contributing/development/coding_guidelines.rst:394 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:879 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:881 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:897 msgid "Python" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:396 +#: ../../content/contributing/development/coding_guidelines.rst:398 msgid "Do not forget to read the :ref:`Security Pitfalls ` section as well to write secure code." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:400 +#: ../../content/contributing/development/coding_guidelines.rst:402 msgid "PEP8 options" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:402 +#: ../../content/contributing/development/coding_guidelines.rst:404 msgid "Using a linter can help show syntax and semantic warnings or errors. Odoo source code tries to respect Python standard, but some of them can be ignored." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:405 +#: ../../content/contributing/development/coding_guidelines.rst:407 msgid "E501: line too long" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:406 +#: ../../content/contributing/development/coding_guidelines.rst:408 msgid "E301: expected 1 blank line, found 0" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:407 +#: ../../content/contributing/development/coding_guidelines.rst:409 msgid "E302: expected 2 blank lines, found 1" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:410 +#: ../../content/contributing/development/coding_guidelines.rst:412 msgid "Imports" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:411 +#: ../../content/contributing/development/coding_guidelines.rst:414 msgid "The imports are ordered as" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:413 +#: ../../content/contributing/development/coding_guidelines.rst:416 msgid "External libraries (one per line sorted and split in python stdlib)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:414 +#: ../../content/contributing/development/coding_guidelines.rst:417 msgid "Imports of ``odoo``" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:415 +#: ../../content/contributing/development/coding_guidelines.rst:418 msgid "Imports from Odoo modules (rarely, and only if necessary)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:417 +#: ../../content/contributing/development/coding_guidelines.rst:420 msgid "Inside these 3 groups, the imported lines are alphabetically sorted." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:435 +#: ../../content/contributing/development/coding_guidelines.rst:438 msgid "Idiomatics of Programming (Python)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:437 +#: ../../content/contributing/development/coding_guidelines.rst:440 msgid "Always favor *readability* over *conciseness* or using the language features or idioms." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:438 +#: ../../content/contributing/development/coding_guidelines.rst:441 msgid "Don't use ``.clone()``" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:449 +#: ../../content/contributing/development/coding_guidelines.rst:452 msgid "Python dictionary : creation and update" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:474 +#: ../../content/contributing/development/coding_guidelines.rst:477 msgid "Use meaningful variable/class/method names" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:475 +#: ../../content/contributing/development/coding_guidelines.rst:478 msgid "Useless variable : Temporary variables can make the code clearer by giving names to objects, but that doesn't mean you should create temporary variables all the time:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:487 +#: ../../content/contributing/development/coding_guidelines.rst:490 msgid "Multiple return points are OK, when they're simpler" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:507 +#: ../../content/contributing/development/coding_guidelines.rst:510 msgid "Know your builtins : You should at least have a basic understanding of all the Python builtins (http://docs.python.org/library/functions.html)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:515 +#: ../../content/contributing/development/coding_guidelines.rst:518 msgid "Also, ``if 'key' in my_dict`` and ``if my_dict.get('key')`` have very different meaning, be sure that you're using the right one." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:518 +#: ../../content/contributing/development/coding_guidelines.rst:521 msgid "Learn list comprehensions : Use list comprehension, dict comprehension, and basic manipulation using ``map``, ``filter``, ``sum``, ... They make the code easier to read." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:531 +#: ../../content/contributing/development/coding_guidelines.rst:534 msgid "Collections are booleans too : In python, many objects have \"boolean-ish\" value when evaluated in a boolean context (such as an if). Among these are collections (lists, dicts, sets, ...) which are \"falsy\" when empty and \"truthy\" when containing items:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:542 +#: ../../content/contributing/development/coding_guidelines.rst:545 msgid "So, you can write ``if some_collection:`` instead of ``if len(some_collection):``." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:545 +#: ../../content/contributing/development/coding_guidelines.rst:548 msgid "Iterate on iterables" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:559 +#: ../../content/contributing/development/coding_guidelines.rst:562 msgid "Use dict.setdefault" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:575 +#: ../../content/contributing/development/coding_guidelines.rst:578 msgid "As a good developer, document your code (docstring on methods, simple comments for tricky part of code)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:577 +#: ../../content/contributing/development/coding_guidelines.rst:580 msgid "In additions to these guidelines, you may also find the following link interesting: http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html (a little bit outdated, but quite relevant)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:582 +#: ../../content/contributing/development/coding_guidelines.rst:585 msgid "Programming in Odoo" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:584 +#: ../../content/contributing/development/coding_guidelines.rst:587 msgid "Avoid to create generators and decorators: only use the ones provided by the Odoo API." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:586 +#: ../../content/contributing/development/coding_guidelines.rst:589 msgid "As in python, use ``filtered``, ``mapped``, ``sorted``, ... methods to ease code reading and performance." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:591 +#: ../../content/contributing/development/coding_guidelines.rst:593 msgid "Make your method work in batch" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:592 +#: ../../content/contributing/development/coding_guidelines.rst:595 msgid "When adding a function, make sure it can process multiple records by iterating on self to treat each record." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:601 +#: ../../content/contributing/development/coding_guidelines.rst:604 msgid "For performance issue, when developing a 'stat button' (for instance), do not perform a ``search`` or a ``search_count`` in a loop. It is recommended to use ``read_group`` method, to compute all value in only one request." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:616 +#: ../../content/contributing/development/coding_guidelines.rst:619 msgid "Propagate the context" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:617 +#: ../../content/contributing/development/coding_guidelines.rst:621 msgid "The context is a ``frozendict`` that cannot be modified. To call a method with a different context, the ``with_context`` method should be used :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:626 +#: ../../content/contributing/development/coding_guidelines.rst:630 msgid "Passing parameter in context can have dangerous side-effects." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:628 +#: ../../content/contributing/development/coding_guidelines.rst:632 msgid "Since the values are propagated automatically, some unexpected behavior may appear. Calling ``create()`` method of a model with *default_my_field* key in context will set the default value of *my_field* for the concerned model. But if during this creation, other objects (such as sale.order.line, on sale.order creation) having a field name *my_field* are created, their default value will be set too." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:634 +#: ../../content/contributing/development/coding_guidelines.rst:638 msgid "If you need to create a key context influencing the behavior of some object, choose a good name, and eventually prefix it by the name of the module to isolate its impact. A good example are the keys of ``mail`` module : *mail_create_nosubscribe*, *mail_notrack*, *mail_notify_user_signature*, ..." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:641 +#: ../../content/contributing/development/coding_guidelines.rst:644 msgid "Think extendable" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:643 +#: ../../content/contributing/development/coding_guidelines.rst:646 msgid "Functions and methods should not contain too much logic: having a lot of small and simple methods is more advisable than having few large and complex methods. A good rule of thumb is to split a method as soon as it has more than one responsibility (see http://en.wikipedia.org/wiki/Single_responsibility_principle)." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:648 +#: ../../content/contributing/development/coding_guidelines.rst:651 msgid "Hardcoding a business logic in a method should be avoided as it prevents to be easily extended by a submodule." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:674 +#: ../../content/contributing/development/coding_guidelines.rst:677 msgid "The above code is over extendable for the sake of example but the readability must be taken into account and a tradeoff must be made." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:677 +#: ../../content/contributing/development/coding_guidelines.rst:680 msgid "Also, name your functions accordingly: small and properly named functions are the starting point of readable/maintainable code and tighter documentation." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:680 +#: ../../content/contributing/development/coding_guidelines.rst:683 msgid "This recommendation is also relevant for classes, files, modules and packages. (See also http://en.wikipedia.org/wiki/Cyclomatic_complexity)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:685 +#: ../../content/contributing/development/coding_guidelines.rst:687 msgid "Never commit the transaction" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:686 +#: ../../content/contributing/development/coding_guidelines.rst:689 msgid "The Odoo framework is in charge of providing the transactional context for all RPC calls. The principle is that a new database cursor is opened at the beginning of each RPC call, and committed when the call has returned, just before transmitting the answer to the RPC client, approximately like this:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:707 +#: ../../content/contributing/development/coding_guidelines.rst:710 msgid "If any error occurs during the execution of the RPC call, the transaction is rolled back atomically, preserving the state of the system." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:710 +#: ../../content/contributing/development/coding_guidelines.rst:713 msgid "Similarly, the system also provides a dedicated transaction during the execution of tests suites, so it can be rolled back or not depending on the server startup options." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:714 +#: ../../content/contributing/development/coding_guidelines.rst:717 msgid "The consequence is that if you manually call ``cr.commit()`` anywhere there is a very high chance that you will break the system in various ways, because you will cause partial commits, and thus partial and unclean rollbacks, causing among others:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:719 +#: ../../content/contributing/development/coding_guidelines.rst:722 msgid "inconsistent business data, usually data loss" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:720 +#: ../../content/contributing/development/coding_guidelines.rst:723 msgid "workflow desynchronization, documents stuck permanently" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:721 +#: ../../content/contributing/development/coding_guidelines.rst:724 msgid "tests that can't be rolled back cleanly, and will start polluting the database, and triggering error (this is true even if no error occurs during the transaction)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:732 +#: ../../content/contributing/development/coding_guidelines.rst:735 msgid "Here is the very simple rule:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:726 +#: ../../content/contributing/development/coding_guidelines.rst:729 msgid "You should **NEVER** call ``cr.commit()`` yourself, **UNLESS** you have created your own database cursor explicitly! And the situations where you need to do that are exceptional!" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:730 +#: ../../content/contributing/development/coding_guidelines.rst:733 msgid "And by the way if you did create your own cursor, then you need to handle error cases and proper rollback, as well as properly close the cursor when you're done with it." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:734 +#: ../../content/contributing/development/coding_guidelines.rst:737 msgid "And contrary to popular belief, you do not even need to call ``cr.commit()`` in the following situations: - in the ``_auto_init()`` method of an *models.Model* object: this is taken care of by the addons initialization method, or by the ORM transaction when creating custom models - in reports: the ``commit()`` is handled by the framework too, so you can update the database even from within a report - within *models.Transient* methods: these methods are called exactly like regular *models.Model* ones, within a transaction and with the corresponding ``cr.commit()/rollback()`` at the end - etc. (see general rule above if you are in doubt!)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:746 +#: ../../content/contributing/development/coding_guidelines.rst:749 msgid "All ``cr.commit()`` calls outside of the server framework from now on must have an **explicit comment** explaining why they are absolutely necessary, why they are indeed correct, and why they do not break the transactions. Otherwise they can and will be removed !" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:753 +#: ../../content/contributing/development/coding_guidelines.rst:755 msgid "Use translation method correctly" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:755 +#: ../../content/contributing/development/coding_guidelines.rst:757 msgid "Odoo uses a GetText-like method named \"underscore\" ``_( )`` to indicate that a static string used in the code needs to be translated at runtime using the language of the context. This pseudo-method is accessed within your code by importing as follows:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:764 +#: ../../content/contributing/development/coding_guidelines.rst:766 msgid "A few very important rules must be followed when using it, in order for it to work and to avoid filling the translations with useless junk." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:767 +#: ../../content/contributing/development/coding_guidelines.rst:769 msgid "Basically, this method should only be used for static strings written manually in the code, it will not work to translate field values, such as Product names, etc. This must be done instead using the translate flag on the corresponding field." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:772 +#: ../../content/contributing/development/coding_guidelines.rst:774 msgid "The method accepts optional positional or named parameter The rule is very simple: calls to the underscore method should always be in the form ``_('literal string')`` and nothing else:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:815 +#: ../../content/contributing/development/coding_guidelines.rst:817 msgid "Also, keep in mind that translators will have to work with the literal values that are passed to the underscore function, so please try to make them easy to understand and keep spurious characters and formatting to a minimum. Translators must be aware that formatting patterns such as ``%s`` or ``%d``, newlines, etc. need to be preserved, but it's important to use these in a sensible and obvious manner:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:835 +#: ../../content/contributing/development/coding_guidelines.rst:837 msgid "In general in Odoo, when manipulating strings, prefer ``%`` over ``.format()`` (when only one variable to replace in a string), and prefer ``%(varname)`` instead of position (when multiple variables have to be replaced). This makes the translation easier for the community translators." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:842 +#: ../../content/contributing/development/coding_guidelines.rst:843 msgid "Symbols and Conventions" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:852 +#: ../../content/contributing/development/coding_guidelines.rst:853 msgid "Model name (using the dot notation, prefix by the module name) :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:845 +#: ../../content/contributing/development/coding_guidelines.rst:846 msgid "When defining an Odoo Model : use singular form of the name (*res.partner* and *sale.order* instead of *res.partnerS* and *saleS.orderS*)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:847 +#: ../../content/contributing/development/coding_guidelines.rst:848 msgid "When defining an Odoo Transient (wizard) : use ``.`` where *related_base_model* is the base model (defined in *models/*) related to the transient, and *action* is the short name of what the transient do. Avoid the *wizard* word. For instance : ``account.invoice.make``, ``project.task.delegate.batch``, ..." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:851 +#: ../../content/contributing/development/coding_guidelines.rst:852 msgid "When defining *report* model (SQL views e.i.) : use ``.report.``, based on the Transient convention." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:854 +#: ../../content/contributing/development/coding_guidelines.rst:855 msgid "Odoo Python Class : use camelcase (Object-oriented style)." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:865 +#: ../../content/contributing/development/coding_guidelines.rst:866 msgid "Variable name :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:863 +#: ../../content/contributing/development/coding_guidelines.rst:864 msgid "use camelcase for model variable" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:864 +#: ../../content/contributing/development/coding_guidelines.rst:865 msgid "use underscore lowercase notation for common variable." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:865 +#: ../../content/contributing/development/coding_guidelines.rst:866 msgid "suffix your variable name with *_id* or *_ids* if it contains a record id or list of id. Don't use ``partner_id`` to contain a record of res.partner" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:873 +#: ../../content/contributing/development/coding_guidelines.rst:874 msgid "``One2Many`` and ``Many2Many`` fields should always have *_ids* as suffix (example: sale_order_line_ids)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:874 +#: ../../content/contributing/development/coding_guidelines.rst:875 msgid "``Many2One`` fields should have *_id* as suffix (example : partner_id, user_id, ...)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:884 +#: ../../content/contributing/development/coding_guidelines.rst:885 msgid "Method conventions" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:876 +#: ../../content/contributing/development/coding_guidelines.rst:877 msgid "Compute Field : the compute method pattern is *_compute_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:877 +#: ../../content/contributing/development/coding_guidelines.rst:878 msgid "Search method : the search method pattern is *_search_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:878 +#: ../../content/contributing/development/coding_guidelines.rst:879 msgid "Default method : the default method pattern is *_default_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:879 +#: ../../content/contributing/development/coding_guidelines.rst:880 msgid "Selection method: the selection method pattern is *_selection_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:880 +#: ../../content/contributing/development/coding_guidelines.rst:881 msgid "Onchange method : the onchange method pattern is *_onchange_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:881 +#: ../../content/contributing/development/coding_guidelines.rst:882 msgid "Constraint method : the constraint method pattern is *_check_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:882 +#: ../../content/contributing/development/coding_guidelines.rst:883 msgid "Action method : an object action method is prefix with *action_*. Since it uses only one record, add ``self.ensure_one()`` at the beginning of the method." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:895 +#: ../../content/contributing/development/coding_guidelines.rst:896 msgid "In a Model attribute order should be" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:887 +#: ../../content/contributing/development/coding_guidelines.rst:888 msgid "Private attributes (``_name``, ``_description``, ``_inherit``, ``_sql_constraints``, ...)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:888 +#: ../../content/contributing/development/coding_guidelines.rst:889 msgid "Default method and ``default_get``" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:889 +#: ../../content/contributing/development/coding_guidelines.rst:890 msgid "Field declarations" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:890 +#: ../../content/contributing/development/coding_guidelines.rst:891 msgid "Compute, inverse and search methods in the same order as field declaration" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:891 +#: ../../content/contributing/development/coding_guidelines.rst:892 msgid "Selection method (methods used to return computed values for selection fields)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:892 +#: ../../content/contributing/development/coding_guidelines.rst:893 msgid "Constrains methods (``@api.constrains``) and onchange methods (``@api.onchange``)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:893 +#: ../../content/contributing/development/coding_guidelines.rst:894 msgid "CRUD methods (ORM overrides)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:894 +#: ../../content/contributing/development/coding_guidelines.rst:895 msgid "Action methods" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:895 +#: ../../content/contributing/development/coding_guidelines.rst:896 msgid "And finally, other business methods." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:951 +#: ../../content/contributing/development/coding_guidelines.rst:952 msgid "Javascript and CSS" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:954 +#: ../../content/contributing/development/coding_guidelines.rst:955 msgid "Static files organization" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:956 +#: ../../content/contributing/development/coding_guidelines.rst:957 msgid "Odoo addons have some conventions on how to structure various files. We explain here in more details how web assets are supposed to be organized." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:959 +#: ../../content/contributing/development/coding_guidelines.rst:960 msgid "The first thing to know is that the Odoo server will serve (statically) all files located in a *static/* folder, but prefixed with the addon name. So, for example, if a file is located in *addons/web/static/src/js/some_file.js*, then it will be statically available at the url *your-odoo-server.com/web/static/src/js/some_file.js*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:964 +#: ../../content/contributing/development/coding_guidelines.rst:965 msgid "The convention is to organize the code according to the following structure:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:966 +#: ../../content/contributing/development/coding_guidelines.rst:967 msgid "*static*: all static files in general" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:968 +#: ../../content/contributing/development/coding_guidelines.rst:969 msgid "*static/lib*: this is the place where js libs should be located, in a sub folder. So, for example, all files from the *jquery* library are in *addons/web/static/lib/jquery*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:970 +#: ../../content/contributing/development/coding_guidelines.rst:971 msgid "*static/src*: the generic static source code folder" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:972 +#: ../../content/contributing/development/coding_guidelines.rst:973 msgid "*static/src/css*: all css files" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:973 +#: ../../content/contributing/development/coding_guidelines.rst:974 msgid "*static/src/fonts*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:974 +#: ../../content/contributing/development/coding_guidelines.rst:975 msgid "*static/src/img*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:975 +#: ../../content/contributing/development/coding_guidelines.rst:976 msgid "*static/src/js*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:977 +#: ../../content/contributing/development/coding_guidelines.rst:978 msgid "*static/src/js/tours*: end user tour files (tutorials, not tests)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:979 +#: ../../content/contributing/development/coding_guidelines.rst:980 msgid "*static/src/scss*: scss files" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:980 +#: ../../content/contributing/development/coding_guidelines.rst:981 msgid "*static/src/xml*: all qweb templates that will be rendered in JS" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:982 +#: ../../content/contributing/development/coding_guidelines.rst:983 msgid "*static/tests*: this is where we put all test related files." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:984 +#: ../../content/contributing/development/coding_guidelines.rst:985 msgid "*static/tests/tours*: this is where we put all tour test files (not tutorials)." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:987 +#: ../../content/contributing/development/coding_guidelines.rst:988 msgid "Javascript coding guidelines" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:989 +#: ../../content/contributing/development/coding_guidelines.rst:990 msgid "``use strict;`` is recommended for all javascript files" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:990 +#: ../../content/contributing/development/coding_guidelines.rst:991 msgid "Use a linter (jshint, ...)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:991 +#: ../../content/contributing/development/coding_guidelines.rst:992 msgid "Never add minified Javascript Libraries" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:992 +#: ../../content/contributing/development/coding_guidelines.rst:993 msgid "Use camelcase for class declaration" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:994 +#: ../../content/contributing/development/coding_guidelines.rst:995 msgid "More precise JS guidelines are detailed in the `github wiki `_. You may also have a look at existing API in Javascript by looking Javascript References." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:999 +#: ../../content/contributing/development/coding_guidelines.rst:1000 msgid "CSS coding guidelines" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1001 +#: ../../content/contributing/development/coding_guidelines.rst:1002 msgid "Prefix all your classes with *o_* where *module_name* is the technical name of the module ('sale', 'im_chat', ...) or the main route reserved by the module (for website module mainly, i.e. : 'o_forum' for *website_forum* module). The only exception for this rule is the webclient: it simply uses *o_* prefix." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1006 +#: ../../content/contributing/development/coding_guidelines.rst:1007 msgid "Avoid using *id* tag" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1007 +#: ../../content/contributing/development/coding_guidelines.rst:1008 msgid "Use Bootstrap native classes" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1008 +#: ../../content/contributing/development/coding_guidelines.rst:1009 msgid "Use underscore lowercase notation to name class" msgstr "" @@ -1395,16 +1378,13 @@ msgid "Click on the :guilabel:`Preview changes` button to review your contributi msgstr "" #: ../../content/contributing/documentation.rst:184 -msgid "Scroll to the bottom of the page and fill out the small form to propose your changes. In the first text box, write a very short summary of your changes. For instance, \"Fix a typo\" or \"Add documentation for invoicing of sales orders\". In the second text box, explain *why* you are proposing these changes. Then, click on the :guilabel:`Propose changes` button." +msgid "Scroll to the bottom of the page and fill out the small form to propose your changes. In the first text box, write a very short summary of your changes. For instance, \"Fix a typo\" or \"Add documentation for invoicing of sales orders.\" In the second text box, explain *why* you are proposing these changes. Then, click on the :guilabel:`Propose changes` button." msgstr "" #: ../../content/contributing/documentation.rst:195 msgid "Review the summary that you wrote about your changes and click on the :guilabel:`Create pull request` button again." msgstr "" -#: ../../content/contributing/documentation/changes_approved.rst:1 -#: ../../content/contributing/documentation/changes_approved.rst:1 -#: ../../content/contributing/documentation/changes_approved.rst:1 #: ../../content/contributing/documentation/changes_approved.rst:1 #: ../../content/contributing/documentation/changes_approved.rst:1 msgid "Once your changes are approved, the reviewer merges them and they appear online the next day!" @@ -1755,7 +1735,7 @@ msgstr "" msgid "If necessary, you can **edit** the screenshot to remove unnecessary fields and to narrow even more Odoo's display." msgstr "" -#: ../../content/contributing/documentation/content_guidelines.rst:None +#: ../../content/contributing/documentation/content_guidelines.rst:-1 msgid "Three tips to take good screenshots for the Odoo documentation." msgstr "" @@ -1944,7 +1924,7 @@ msgid "Odoo uses :abbr:`OCR (optical character recognition)` and artificial inte msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:149 -msgid ":abbr:`GUI (Graphical User Interface)` element" +msgid ":abbr:`GUI (graphical user interface)` element" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:151 @@ -2538,42 +2518,46 @@ msgid "Code tabs are essentially :ref:`group tabs ` tha msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:1009 +msgid "Cards" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1057 msgid "Document metadata" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1011 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1059 msgid "Sphinx supports document-wide metadata markups that specify a behavior for the entire page." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1012 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1060 msgid "They must be placed between colons (`:`) at the top of the source file." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1015 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1063 msgid "**Metadata**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1015 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1063 msgid "**Purpose**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1017 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1065 msgid "`show-content`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1017 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1065 msgid "Make a toctree page accessible from the navigation menu." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1019 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1067 msgid "`show-toc`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1019 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1067 msgid "Show the table of content on a page that has the `show-content` metadata markup." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1022 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1070 msgid "`code-column`" msgstr "" @@ -2582,62 +2566,62 @@ msgid "Show a dynamic side column that can be used to display interactive tutori msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:0 -msgid "For example, see :doc:`/applications/finance/accounting/getting_started/memento`." +msgid "For example, see :doc:`/applications/finance/accounting/getting_started/cheat_sheet`." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1027 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1075 msgid "`hide-page-toc`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1027 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1075 msgid "Hide the \"On this page\" sidebar and use full page width for the content." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1029 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1077 msgid "`custom-css`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1029 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1077 msgid "Link CSS files (comma-separated) to the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1031 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1079 msgid "`custom-js`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1031 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1079 msgid "Link JS files (comma-separated) to the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1033 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1081 msgid "`classes`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1033 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1081 msgid "Assign the specified classes to the `
` element of the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1035 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1083 msgid "`orphan`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1035 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1083 msgid "Suppress the need to include the document in a toctree." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1037 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1085 msgid "`nosearch`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1037 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1085 msgid "Exclude the document from search results." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1043 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1091 msgid "Formatting tips" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1048 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1096 msgid "Break the line but not the paragraph" msgstr "" @@ -2649,15 +2633,15 @@ msgstr "" msgid "A second line that follows a line break." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1066 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1114 msgid "Escape markup symbols (Advanced)" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1068 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1116 msgid "Markup symbols escaped with backslashes (``\\``) are rendered normally. For instance, ``this \\*\\*line of text\\*\\* with \\*markup\\* symbols`` is rendered as “this \\*\\*line of text\\*\\* with \\*markup\\* symbols”." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1072 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1120 msgid "When it comes to backticks (`````), which are used in many cases such as :ref:`external hyperlinks `, using backslashes for escaping is no longer an option because the outer backticks interpret enclosed backslashes and thus prevent them from escaping inner backticks. For instance, ```\\`this formatting\\```` produces an ``[UNKNOWN NODE title_reference]`` error. Instead, `````this formatting````` should be used to produce the following result: ```this formatting```." msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 1398bb1c2..ae404ac94 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -44,169 +44,167 @@ msgstr "" msgid "Bank and cash" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds.rst:5 -msgid "Bank feeds" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:3 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:3 msgid "Bank statements" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:5 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:5 msgid "Importing your bank statements in Odoo Accounting allows you to keep track of the financial movements that occur on your bank accounts and reconcile them with the transactions recorded in your accounting." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:9 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:9 msgid "We recommend you use bank synchronization for more efficiency. Please read the related documentation: :doc:`bank_synchronization`." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:12 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:12 msgid "However, if you don't want to use bank synchronization or if your bank is not a supported institution, you still have other options:" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:15 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:15 msgid "Import the bank statement files delivered by your bank" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:16 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:16 msgid "Register the bank statements manually" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:19 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:19 msgid "Import bank statements files" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:21 msgid "Odoo supports multiple file formats to import bank statements:" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:23 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:23 msgid "SEPA recommended Cash Management format (CAMT.053)" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:24 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:24 msgid "Comma-separated values (.CSV)" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:25 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:25 msgid "Open Financial Exchange (.OFX)" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:26 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:26 msgid "Quicken Interchange Format (.QIF)" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:27 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:27 msgid "Belgium: Coded Statement of Account (.CODA)" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:29 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:29 msgid "To import them, go to :menuselection:`Accounting --> Overview --> Bank`, click on *Import Statements*, or on the three dots, and then on *Import Statement*." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:None +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:-1 msgid "Import a bank statement file in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:36 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:36 msgid "Next, select the file you want to import and click on *Import*." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:38 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:38 msgid "Odoo opens an **import widget** to help you set the **Formatting Options** and **map** the different columns you want to import." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:None -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:None +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:-1 msgid "Register bank statements manually in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:46 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:46 msgid "Quicken Interchange Format (.QIF) is an older file format that is no longer supported since 2005. If possible, prefer OFX files over QIF." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:50 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:50 msgid "Register bank statements manually" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:52 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:52 msgid "If needed, you can also record your bank statements manually." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:54 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:54 msgid "To do so, go to :menuselection:`Accounting --> Overview --> Bank`, click on *Create Statements*, or on the three dots, and then on *New Statement*." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:57 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:57 msgid "Add a new line for each transaction written on the original bank statement." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:59 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:59 msgid "To ease the reconciliation process, make sure to fill out the *Partner* field. You can also write the payments’ references in the *Label* field." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:67 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:67 msgid "The *Ending Balance* and the *Computed Balance* should have the same amount. If it is not the case, make sure that there is no mistake in the transactions’ amounts." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:71 -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:122 -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:109 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:71 msgid ":doc:`bank_synchronization`" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:72 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:72 msgid "Todo" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:72 +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:72 msgid "add doc link to new documentation about reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:3 -msgid "Bank synchronization: automatic import" +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:5 +msgid "Bank synchronization" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:5 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:7 msgid "Odoo can synchronize directly with your bank institution to get all bank statements imported automatically into your database." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:8 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:10 msgid "To check if your bank is compatible with Odoo, go to `Odoo Accounting Features `_, and click on :guilabel:`See list of supported institutions`." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:12 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:14 msgid "Odoo supports more than 25,000 institutions around the world." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:14 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:16 msgid "To connect to the banks, Odoo uses multiple web-services:" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:16 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:18 msgid "**Plaid**: United States of America and Canada" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:17 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:19 msgid "**Yodlee**: Worldwide" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:18 -msgid "**Salt Edge**: Europe (:doc:`more information `)" +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:20 +msgid ":doc:`Salt Edge `: Worldwide" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:19 -msgid "**Ponto**: Europe (:doc:`more information `)" +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:21 +msgid ":doc:`Ponto `: Europe" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:20 -msgid "**EnableBanking**: Scandinavian countries" +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:22 +msgid ":doc:`Enable Banking `: Scandinavian countries" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:23 -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:24 -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:19 -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:14 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:25 +msgid ":doc:`bank_statements`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:28 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:24 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:22 +#: ../../content/applications/finance/accounting/bank/interbank.rst:14 #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:67 #: ../../content/applications/finance/accounting/bank/reconciliation/use_cases.rst:16 #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:16 @@ -223,6 +221,7 @@ msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:47 #: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:21 #: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:46 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:12 #: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:15 #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:20 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:39 @@ -239,6 +238,8 @@ msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:13 #: ../../content/applications/finance/fiscal_localizations.rst:21 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:32 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:18 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:105 #: ../../content/applications/finance/fiscal_localizations/chile.rst:29 #: ../../content/applications/finance/fiscal_localizations/chile.rst:290 #: ../../content/applications/finance/fiscal_localizations/chile.rst:332 @@ -249,591 +250,623 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:78 #: ../../content/applications/finance/fiscal_localizations/peru.rst:25 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:6 -#: ../../content/applications/finance/payment_acquirers.rst:99 -#: ../../content/applications/finance/payment_acquirers/adyen.rst:21 +#: ../../content/applications/finance/payment_acquirers.rst:98 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:25 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:30 msgid "Configuration" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:26 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:31 msgid "On-Premise users" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:28 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:33 msgid "To be able to use this service, you need to have a valid Odoo Enterprise subscription. So make sure that your database is registered with your Odoo Enterprise contract. We also use a proxy between your database and the third party provider so, in case of a connection error, please check that you don't have a firewall or a proxy blocking the following address:" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:34 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:39 msgid "https://production.odoofin.com/" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:37 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:42 msgid "First synchronization" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:39 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:44 msgid "You can start synchronization either by going to the Accounting app and :menuselection:`Accounting Dashboard --> Configuration --> Banks: Add a Bank Account`." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:42 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:47 msgid "Now you can search for your bank institution. Select it and follow the steps to synchronize with it." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:45 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:50 msgid "If you have any issues during your first synchronization, please verify that your web browser doesn't block pop-ups and that your ad-blocker is disabled." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:49 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:54 msgid "When choosing the date for the first bank statement synchronization, pick the date when you start recording accounting transaction on your Odoo accounting database. For example, if you import your closing balance in Odoo on the 31/12/2022 and you start recording accounting transactions on the 01/01/2023, your synchronization date should be 01/01/2023." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:54 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:59 msgid "You must provide a phone number during your first synchronization to secure your account. We ask for such information because we don't want your data falling into the wrong hands. Therefore, if we detect suspicious activities on your account, we block all requests coming from your account, and you need to reactivate it using that phone number." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:59 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:64 msgid "The third-party provider may request more information in order to connect with your bank institution. This information is not stored on Odoo's servers." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:63 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:68 msgid "By default, transactions fetched from an online source are grouped inside the same statement, and one bank statement is created per month. You can change the bank statement creation periodicity in your journal settings." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:67 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:72 msgid "You can find all your synchronizations by going to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:71 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:76 msgid "Synchronize manually" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:73 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:78 msgid "After your first synchronization, the created journals are synchronized by default every 12 hours. If you wish, you can synchronize manually by clicking on the :guilabel:`Synchronize Now` button on the dashboard." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:77 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:82 msgid "Or you can go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`, select your institution and then click on the :guilabel:`fetch transactions` button." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:82 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:87 msgid "Some institutions do not allow transactions to be fetched automatically. For such institutions, during the automatic synchronization of the account, you receive an error message asking you to disable the automatic synchronization. This message can be found in the chatter of your online synchronizations. In this case, make sure to perform manual synchronizations." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:88 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:93 msgid "Issues" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:91 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:96 msgid "Synchronization in error" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:93 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:98 msgid "To report a connection error to the `Odoo support `_, go to :menuselection:`Accounting Dashboard--> Configuration --> Accounting: Online Synchronization`, select the connection that failed, and copy the error description and the reference." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:98 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:103 msgid "Synchronization disconnected" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:100 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:105 msgid "If your connection with the proxy is disconnected, you can reconnect with the proxy using the :guilabel:`Fetch Account` button." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:104 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:109 msgid "This disconnection can be caused by the Odoo support. In this case, please contact the `support `_ directly with your client id or the reference of the error listed in the chatter." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:111 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:116 msgid "Migration process for users having installed Odoo before December 2020" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:113 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:118 msgid "If you are on-premise, please first make sure that your source is up-to-date with the latest version of Odoo." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:116 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:121 msgid "Users who have created a database before December 2020 need to install the new module manually to use the new functionalities." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:119 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:124 msgid "To do so, go to :menuselection:`Apps --> Update Apps List`, remove the default filter in the search bar and type `account_online_synchronization`. You can then click on :guilabel:`Install`. Finally, make sure all your users refresh their Odoo page by pressing CTRL+F5." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:125 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:130 msgid "All previous synchronizations are disconnected during the installation and won't work anymore." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:126 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:131 msgid "You can find them directly in the synchronization menu (:menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`). It is not possible to resynchronize these connections; you have to make new ones." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:130 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:135 msgid "Do not uninstall `account_online_sync`, which is the previous module for online synchronization. The new one overrides it." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:132 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:137 msgid "By default, `account_online_synchronization` is installed automatically with Accounting." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:135 -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:95 -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:78 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:140 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:95 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:81 msgid "FAQ" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:138 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:143 msgid "The synchronization is not working in real-time. Is that normal?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:140 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:145 msgid "The process is not intended to work in real-time as third party providers synchronize your accounts at different intervals. To force the synchronization and fetch the statements, go to your :guilabel:`Accounting Dashboard`, and click on the :guilabel:`Synchronize Now` button. You can also synchronize and fetch transactions through :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`. Some providers only allow one refresh per day, so it is possible that clicking on :guilabel:`Synchronize Now` does not get your latest transactions if you already performed such action earlier in the day." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:148 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:153 msgid "A transaction can be visible on your bank account but not be fetched if it has the status :guilabel:`Pending`. Only transactions with the :guilabel:`Posted` status will be retrieved. If the transaction is not **Posted** yet, you will have to wait until the status changes." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:153 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:158 msgid "Is the Online Bank Synchronization feature included in my contract?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:155 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:160 msgid "**Community Version**: No, this feature is not included in the Community Version." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:156 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:161 msgid "**Online Version**: Yes, even if you benefit from the One App Free contract." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:157 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:162 msgid "**Enterprise Version**: Yes, if you have a valid enterprise contract linked to your database." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:160 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:165 msgid "Some banks have a status \"Beta.\" What does this mean?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:162 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:167 msgid "This means that banking institutions are not yet fully supported by our Third Party Provider. Bugs or other problems may arise. Odoo does not support technical problems that occur with banks in the Beta phase, but the user may still choose to connect. Connecting with these banks contributes to the development process since the Provider will have real data and feedback from the connection." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:168 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:173 msgid "Why do my transactions only synchronize when I refresh manually?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:170 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:175 msgid "Some banks have additional security measures and require extra steps, such as an SMS/email authentication code or another type of MFA. Because of this, the integrator cannot pull transactions until the security code is provided." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:175 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:180 msgid "Not all of my past transactions are in Odoo, why?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:177 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:182 msgid "For some institutions, transactions can only be fetched up to 3 months in the past." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:180 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:185 msgid "Why don't I see any transactions?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:182 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:187 msgid "During your first synchronization, you selected the bank accounts you decided to synchronize with Odoo. If you didn't synchronize any of your accounts, you can go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization` to click on the :guilabel:`Fetch Account` button on the connection." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:187 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:192 msgid "There may also be no new transactions." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:189 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:194 msgid "If your bank account is properly linked to a journal and posted transactions are not visible in your database, please `submit a support ticket `_." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:193 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:198 msgid "How can I update my bank credentials?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:195 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:200 msgid "You can update your credentials by going to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`,open the connection you want to update your credentials and click on the :guilabel:`Update Credentials` button." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:200 -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:124 -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:111 -msgid ":doc:`bank_statements`" +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:3 +msgid "Enable Banking" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:201 -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:110 -msgid ":doc:`ponto`" +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:5 +msgid "**Enable Banking** is a third-party provider aggregating banking information from bank accounts all in one place. It offers non-intrusive connectivity to ASPSPs' official APIs across Europe without storing data." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:202 -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:123 -msgid ":doc:`saltedge`" +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:-1 +msgid "Enable Banking logo" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:3 -msgid "Ponto as bank synchronization provider" +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:13 +msgid "**Odoo** synchronizes directly with banks to get access to all bank transactions and automatically import them into your database." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:5 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:17 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:20 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:18 +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:125 +#: ../../content/applications/finance/accounting/bank/reconciliation/use_cases.rst:105 +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:93 +msgid ":doc:`../bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:18 +msgid "`Enable Banking website `_" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:24 +msgid "Link bank accounts with Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:26 +msgid "Start synchronization by clicking on :menuselection:`Accounting --> Configuration --> Add a Bank Account`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:28 +msgid "Select your bank;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:29 +msgid "Make sure you give your consent to share your account information with Odoo by clicking :guilabel:`Continue authentication`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:0 +msgid "Enable Banking authentication page" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:36 +msgid "Finally, you are redirected to your bank's login page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:3 +msgid "Ponto" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:5 msgid "**Ponto** is a service that allows companies and professionals to aggregate their accounts in one place and directly see all their transactions within one app. It is a third-party solution that is continuously expanding the number of bank institutions that can be synchronized with Odoo." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:None +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:-1 msgid "Logo of the Ponto brand" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:13 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:13 msgid "**Odoo** can synchronize directly with your bank to get all bank statements imported automatically into your database." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:16 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:16 msgid "Ponto is a paid third-party provider that can handle the synchronization between your bank accounts and Odoo. `Its pricing is 4€/month per account/integration `_." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:20 -msgid "You can find more information about bank synchronization :doc:`on this page `." +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:19 +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:94 +msgid ":doc:`../bank_statements`" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:27 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:27 msgid "Link your bank accounts with Ponto" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:29 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:29 msgid "Go to `Ponto's website (https://myponto.com) `_." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:30 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:30 msgid "Create an account if you don't have one yet." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:31 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:31 msgid "Once you are logged in, create an *organization*." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:0 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 msgid "Fill out the form to add an organization in Ponto." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:0 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 msgid "Go to :menuselection:`Accounts --> Live`, and click on *Add account*." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:0 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 msgid "You might have to add your **Billing Information** first." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:39 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:39 msgid "Select your country, your bank institutions, give your consent to Ponto, and follow the steps on-screen to link your bank account with your Ponto account." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:0 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 msgid "Add bank accounts to your Ponto account." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:46 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:46 msgid "Make sure to add all bank accounts you want to synchronize with your Odoo database before moving on to the next steps." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:50 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:50 msgid "Link your Ponto account with your Odoo database" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:52 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:52 msgid "Go to :menuselection:`Accounting --> Configuration --> Add a Bank Account`." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:53 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:53 msgid "Search your institution, make sure to select the right institution. By selecting the institution, you can verify that the third party provider is Ponto." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:55 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:55 msgid "Click on *Connect* and follow the steps." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:56 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:56 msgid "At some point, you will have to authorize the accounts you want to access in Odoo. Please select **all the accounts** you want to synchronize. Even the ones coming from other banking institutions." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:0 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 msgid "Selection of the accounts you wish to synchronize with Odoo." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:64 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:64 msgid "Finish the flow." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:67 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:67 msgid "You have to authorize all the accounts you want to access in Odoo, but Odoo will filter the accounts based on the institution you selected in the second step." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:71 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:71 msgid "Update your synchronization credentials" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:73 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:73 msgid "You might have to update your Ponto credentials or modify the synchronization settings." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:75 -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:87 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:75 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:87 msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Online Synchronization` and select the institution you want to fetch the other accounts. Click on *Fetch Accounts* button to start the flow." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:79 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:79 msgid "During the update, select **all the accounts** you want to synchronize, even the ones coming from other banking institutions." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:83 -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:66 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:83 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:69 msgid "Fetch new accounts" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:85 -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:68 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:85 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:71 msgid "You might want to add new online accounts to your connection." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:91 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:91 msgid "Don't forget to keep authorization for existing accounts (for all institutions that you have synchronized with Ponto)." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:98 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:98 msgid "After my synchronization, no account appears" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:100 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:100 msgid "You selected an institution from the list and did not authorize any accounts from this institution." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:103 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:103 msgid "I have an error about that my authorization has expired" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:105 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:105 msgid "Every **3 months** (90 days) you must re-authorize the connection between your bank account and Ponto. This must be done from the `Ponto website `_. If you do not do this, the synchronization will stop for these accounts." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:110 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:110 msgid "I have some errors with my beta institution" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:112 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:112 msgid "Ponto provides institutions in *beta*, these institutions are not directly supported by Odoo and we advise you to contact Ponto directly." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:116 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:116 msgid "Using an institution in beta is beneficial for Ponto, it allows them to have real feedback on the connection with the institution." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:3 -msgid "Salt Edge as bank synchronization provider" +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:3 +msgid "Salt Edge" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:5 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:5 msgid "**Salt Edge** is a third-party provider that aggregates banking information from your bank accounts. It supports ~5000 institutions in more than 50 countries." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:None +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:-1 msgid "Salt Edge Logo" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:13 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:14 msgid "Odoo can synchronize directly with your bank to get all bank statements imported automatically into your database." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:16 -msgid "Salt Edge is a free third-party provider." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:22 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:25 msgid "Link your bank accounts with Odoo" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:24 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:27 msgid "Start synchronization by clicking on :menuselection:`Accounting --> Configuration --> Add a Bank Account`." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:26 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:29 msgid "Select the institution you want to synchronize. You can see if Salt Edge is the third party provider of the institution by selecting it." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:28 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:31 msgid "After giving your phone number, you are asked for an email address. This email address is used to create your Salt Edge account. Please make sure you enter a valid email address, as otherwise, you will not be able to access your Salt Edge account." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:0 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 msgid "Email address to provide to Salt Edge for the creation of your account." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:37 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:40 msgid "After entering your email address, you are redirected to Salt Edge to continue the synchronization process." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:0 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 msgid "Salt Edge Login page." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:44 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:47 msgid "Make sure you give your consent by checking the consent checkbox." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:0 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 msgid "Salt Edge give consent page." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:50 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:53 msgid "Complete the synchronization by following the steps." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:54 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:57 msgid "Update your credentials" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:56 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:59 msgid "You might have to update your Salt Edge credentials or modify the synchronization settings." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:58 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:61 msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Online Synchronization` and select the institution you want to update credentials. Click on the *Update Credentials* button to start the flow and follow the steps." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:62 -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:74 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:65 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:77 msgid "Don't forget to check the consent checkbox. Otherwise, Odoo may not be able to access your information." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:70 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:73 msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Online Synchronization` and select the institution to fetch the new accounts. Click on the *Fetch Accounts* button to start the flow and follow the steps." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:81 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:84 msgid "I have an error when I try to delete my synchronization within Odoo" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:83 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:86 msgid "Odoo can't permanently delete the connection you have created with the banking institution. However, it can revoke the consent you gave so that Odoo won't be able to access your account anymore. The error you are seeing is probably a message telling you that the consent was revoked, but the record could not be deleted as it still exists within Salt edge. If you want to remove the connection completely, please connect to your `Salt Edge account `_ and manually delete your synchronization. Once this is done, you can go back to Odoo to delete the record." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:92 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:95 msgid "I have an error saying that I have already synchronized this account" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:94 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:97 msgid "You have probably already synchronized your bank account with Salt Edge, please check on your `dashboard `_ that you don't already have a connection with the same credentials." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:98 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:101 msgid "In case you already have a synchronization with the same credentials present on your Salt Edge dashboard and this synchronization has not been created with Odoo, please delete it and create it from your Odoo database." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:102 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:105 msgid "In case you already have a connection with the same credentials present on your Salt Edge dashboard and this synchronization was created with Odoo, you will normally be able to find it by going to :menuselection:`Accounting --> Configuration --> Online Synchronization`. Please make sure to do an *Update Credentials* to reactivate the connection." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc.rst:5 -#: ../../content/applications/finance/accounting/payables/misc.rst:5 -msgid "Miscellaneous" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:3 +#: ../../content/applications/finance/accounting/bank/interbank.rst:3 msgid "Do a bank wire transfer from one bank to another" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:5 +#: ../../content/applications/finance/accounting/bank/interbank.rst:5 msgid "A company might have several bank accounts or cash registers. Within odoo it is possible to handle internal transfers of money with only a couple of clicks." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:9 +#: ../../content/applications/finance/accounting/bank/interbank.rst:9 msgid "We will take the following example to illustrate. My company has two bank accounts and I want to transfer 50.000 euros from one of our bank accounts to the another one." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:17 +#: ../../content/applications/finance/accounting/bank/interbank.rst:17 msgid "Check your Chart of Accounts and default transfer account" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:19 +#: ../../content/applications/finance/accounting/bank/interbank.rst:19 msgid "To handle internal transfers you need a transfer account in your charts of account. Odoo will generate an account automatically based on the country of your chart of account. To configure your chart of accounts and check the default transfer account go into the accounting module settings, select :menuselection:`Configuration --> Settings`." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:25 +#: ../../content/applications/finance/accounting/bank/interbank.rst:25 msgid "Your chart of accounts will be pre-installed depending on the country specified during your registration, it cannot be changed." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:31 +#: ../../content/applications/finance/accounting/bank/interbank.rst:31 msgid "The default transfer account will automatically be generated as well depending on your country's legislation. If necessary it can be modified from the same page." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:39 +#: ../../content/applications/finance/accounting/bank/interbank.rst:39 msgid "Create a second bank account / Journal" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:41 +#: ../../content/applications/finance/accounting/bank/interbank.rst:41 msgid "Before we can register an internal transfer we need to add a new bank to our accounting dashboard. To do so enter the accounting module, click on :menuselection:`Configuration --> Bank Accounts`. Create a new bank account. You should fill in the **Account Number**. You can also create and edit your bank to specify your bank's details." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:50 +#: ../../content/applications/finance/accounting/bank/interbank.rst:50 msgid "By saving the changes you now have 2 bank accounts." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:56 +#: ../../content/applications/finance/accounting/bank/interbank.rst:56 msgid "Register an internal transfer from one bank to another." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:58 +#: ../../content/applications/finance/accounting/bank/interbank.rst:58 msgid "We will now transfer 50.000 euros from our **Bank** to our **Bank BE57 0633 9533 1498** account." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:62 +#: ../../content/applications/finance/accounting/bank/interbank.rst:62 msgid "Log an internal transfer" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:64 +#: ../../content/applications/finance/accounting/bank/interbank.rst:64 msgid "The first step is to register the internal payment. To do so go into your accounting dashboard, click on the **more** button of one of your banks and select :menuselection:`New --> Internal transfer`." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:71 +#: ../../content/applications/finance/accounting/bank/interbank.rst:71 msgid "Create a new payment. The payment type will automatically be set to internal transfer. Select the **Bank** you want to transfer to, specify the **Amount** and add a **Memo** if you wish." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:76 +#: ../../content/applications/finance/accounting/bank/interbank.rst:76 msgid "The memo is important if you wish to automatically reconcile (see `Import bank statements and reconcile`_)." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:82 +#: ../../content/applications/finance/accounting/bank/interbank.rst:82 msgid "Save and confirm the changes to register the payment." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:84 +#: ../../content/applications/finance/accounting/bank/interbank.rst:84 msgid "In terms of accounting the money is now booked in the transfer account. We'll need to import bank statements to book the money in the final accounts." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:89 +#: ../../content/applications/finance/accounting/bank/interbank.rst:89 msgid "Import bank statements and reconcile" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:91 +#: ../../content/applications/finance/accounting/bank/interbank.rst:91 msgid "Note that the bank balance computed by Odoo is different that the last statement of your bank." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:97 +#: ../../content/applications/finance/accounting/bank/interbank.rst:97 msgid "That is because we did not import the bank statement confirming the receiving and sending of the money. It's thus necessary to import your bank statement and reconcile the payment with the correct bank statement line. Once you receive your bank statements click the **new statement** button of the corresponding bank to import them." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:106 +#: ../../content/applications/finance/accounting/bank/interbank.rst:106 msgid "Fill in your **Transactions line**. Once done, Odoo will display a **Computed Balance**. that computed balance is the theorical end balance of your bank account. If it's corresponding to the bank statement, it means that no errors were made. Fill in the **Ending balance** and click on the **Reconcile** button." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:114 +#: ../../content/applications/finance/accounting/bank/interbank.rst:114 msgid "The following window will open:" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:119 +#: ../../content/applications/finance/accounting/bank/interbank.rst:119 msgid "You need to choose counterparts for the payment. Select the correct bank statement line corresponding to the payment and click on the **reconcile** button. Close the statement to finish the transaction" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:126 +#: ../../content/applications/finance/accounting/bank/interbank.rst:126 msgid "The same steps will need to be repeated once you receive your second bank statement. Note that if you specify the same amount and the same memo in both bank statements and payment transactions then the reconciliation will happen automatically." msgstr "" @@ -849,7 +882,7 @@ msgstr "" msgid "By default in Odoo, payments registered in the **cash journal** are automatically reconciled with an **outstanding account** and their related invoices or bills marked as *In Payment* until they are reconciled with a bank statement. It is possible to :ref:`bypass ` the *In Payment* status for cash transactions, therefore removing the need to reconcile with a bank statement." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:-1 msgid "In Payment status of invoice or bill." msgstr "" @@ -861,7 +894,7 @@ msgstr "" msgid "At the start of each day, create a **cash log**. To do so, go to your :guilabel:`Accounting Dashboard` and click :guilabel:`New Transaction` in the :guilabel:`Cash` journal." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:-1 msgid "Create a new cash log." msgstr "" @@ -869,7 +902,7 @@ msgstr "" msgid "Enter the :guilabel:`Starting Balance` of your cash float and save, but do *not* post the entry yet. Create your invoice by going to :menuselection:`Accounting dashboard --> Customers --> Invoices` and confirm it. Click :guilabel:`Register Payment` and select the cash :guilabel:`Journal`. Repeat the process for each invoice." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:-1 msgid "Select Cash journal upon payment registration." msgstr "" @@ -889,7 +922,7 @@ msgstr "" msgid "On the **bank reconciliation** page, search through the list for the **cash log** transaction you created earlier. To be able to match all cash payments, make sure no **partner** is selected in the :guilabel:`Select Partner` field. If a **partner** is selected, click in the field and delete the partner. Then, pair (or match) each cash payment with your cash log by clicking on the payment in the :guilabel:`Customer/Vendor Matching`, and :guilabel:`validate`." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:-1 msgid "Cash payments reconciliation." msgstr "" @@ -909,7 +942,7 @@ msgstr "" msgid "To bypass the *In Payment* status, go to :menuselection:`Accounting app --> Configuration --> Accounting: Journals` and select the :guilabel:`Cash` journal. Click on the :guilabel:`Payments Configuration` tab and set a `Cash` account in both the :guilabel:`Outstanding Receipts Account` and :guilabel:`Outstanding Payments Account` fields, then save. Payments registered in the **cash** journal now bypass the *In Payment* status." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:-1 msgid "Configuration tab of the cash journal." msgstr "" @@ -957,7 +990,7 @@ msgstr "" msgid "When reconciling an entry with an *open balance*, you can use the buttons available under the :guilabel:`Manual Operations` tab to pre-fill all the values automatically before validating the reconciliation. Each button corresponds to a reconciliation model." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:-1 msgid "Example of a reconciliation model with a write-off button in Odoo Accounting." msgstr "" @@ -969,7 +1002,7 @@ msgstr "" msgid "This type of reconciliation model immediately suggests counterpart values when selecting an entry, which then only needs to be validated. This automation is based on a set of rules defined in the reconciliation model." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:-1 msgid "Example of a reconciliation model that suggests counterpart values in Odoo Accounting." msgstr "" @@ -981,7 +1014,7 @@ msgstr "" msgid "This type of reconciliation model automatically selects the right customer invoice or vendor bill that matches the payment. All that is left to do is to validate the entry. This automation is based on a set of rules defined in the reconciliation model." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:-1 msgid "Example of a reconciliation model that matches existing invoices and bills automatically\n" "in Odoo Accounting." msgstr "" @@ -990,7 +1023,7 @@ msgstr "" msgid "To manage or create new **reconciliation models**, go to :menuselection:`Accounting app --> Configuration --> Banks: Reconciliation Models`. Alternatively, you can also open this menu from :menuselection:`Accounting app --> Bank --> Drop-down menu (⋮) --> Reconciliation Models`." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:-1 msgid "Open the reconciliation model menu from the overview dashboard in Odoo Accounting." msgstr "" @@ -1027,7 +1060,7 @@ msgstr "" msgid "If a record matches with several reconciliation models, the first one in the list is applied. Models can be rearranged by dragging and dropping the handle next to their name." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:-1 msgid "Conditions for the reconciliation model to be applied in Odoo Accounting." msgstr "" @@ -1039,7 +1072,7 @@ msgstr "" msgid "This section comprises the values that are applied by the reconciliation model. If the value to reconcile needs to be written-off in two separate accounts, click on :guilabel:`Add a second line` a second time." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:-1 msgid "Counterparts values of a reconciliation model in Odoo Accounting." msgstr "" @@ -1047,11 +1080,6 @@ msgstr "" msgid ":doc:`use_cases`" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:125 -#: ../../content/applications/finance/accounting/bank/reconciliation/use_cases.rst:105 -msgid ":doc:`../feeds/bank_synchronization`" -msgstr "" - #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:126 msgid ":doc:`../../receivables/customer_invoices/cash_discounts`" msgstr "" @@ -1159,7 +1187,7 @@ msgid "If the payment is done with a down payment, just check if it is all right msgstr "" #: ../../content/applications/finance/accounting/bank/setup.rst:5 -#: ../../content/applications/finance/expenses.rst:177 +#: ../../content/applications/finance/expenses.rst:460 msgid "Setup" msgstr "" @@ -1183,7 +1211,7 @@ msgstr "" msgid "Every **Bank Journal** is displayed by default on the **Accounting Overview** in the form of a convenient card. It includes action buttons that are displayed when appropriate." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:None +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:-1 msgid "Bank Journals Cards are displayed on the Accounting Overview in Odoo Accounting" msgstr "" @@ -1192,7 +1220,7 @@ msgid "Add a new Bank Account" msgstr "" #: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:27 -msgid "You can either connect your bank account to your Odoo database, or configure your bank account manually and :doc:`upload the bank statements manually <../feeds/bank_statements>`." +msgid "You can either connect your bank account to your Odoo database, or configure your bank account manually and :doc:`upload the bank statements manually <../bank_statements>`." msgstr "" #: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:31 @@ -1208,10 +1236,10 @@ msgid "To synchronize a new bank account, go to :menuselection:`Accounting --> C msgstr "" #: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:40 -msgid ":doc:`Click here <../../bank/feeds/bank_synchronization>` for more information about this bank synchronization." +msgid ":doc:`Click here <../../bank/bank_synchronization>` for more information about this bank synchronization." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:None +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:-1 msgid "Select a bank institution in the list and connect it to Odoo Accounting" msgstr "" @@ -1256,7 +1284,7 @@ msgstr "" msgid "Odoo detects the bank account type (e.g., IBAN) and enables some features accordingly." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:None +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:-1 msgid "Add manually a new bank account in Odoo Accounting" msgstr "" @@ -1276,19 +1304,10 @@ msgstr "" msgid "You can configure which types of payments are enabled in the **Payment Method Types** section and how the bank statements are recorded and posted in the **Bank Statements** section." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:None +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:-1 msgid "Advanced configuration of a bank account in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:93 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:191 -msgid ":doc:`../../bank/feeds/bank_synchronization`" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:94 -msgid ":doc:`../feeds/bank_statements`" -msgstr "" - #: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:95 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:193 msgid "`Odoo Tutorials: Accounting Basics `_" @@ -1346,7 +1365,7 @@ msgstr "" msgid "In the accounting application, go to :menuselection:`Accounting --> Configuration --> Journals` and create a new one. Enter a :guilabel:`Journal Name` and set the :guilabel:`Type` to `Bank`. In the :guilabel:`Journal Entries` tab, enter a **short code**, a **currency**, and then finally click on the :guilabel:`Bank Account` field to create a new account. In the pop-up window of the account creation, enter a name, a code (ex.: 550007), set its type to `Bank and Cash`, set a currency type, and save. When you are back on the **journal**, click on the :guilabel:`Account Number` field, and in the pop-up window, fill out the :guilabel:`Account Number`, :guilabel:`Bank` of your account, and save." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:None +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:-1 msgid "Example of a created bank journal." msgstr "" @@ -1362,7 +1381,7 @@ msgstr "" msgid "To pay a bill in a foreign currency, simply select the currency next to the :guilabel:`Journal` field and register the payment. Odoo automatically creates and posts the foreign **exchange gain or loss** as a new journal entry." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:None +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:-1 msgid "How to set a bill currency." msgstr "" @@ -1378,7 +1397,7 @@ msgstr "" msgid "This report gives an overview of all unrealized amounts in a foreign currency on your balance sheet, and allows you to adjust an entry or manually set an exchange rate. To access this report, go to :menuselection:`Reporting --> Management: Unrealized Currency Gains/Losses`. From here, you have access to all open entries in your **balance sheet**." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:None +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:-1 msgid "View of the Unrealized Gains/Losses journal." msgstr "" @@ -1386,7 +1405,7 @@ msgstr "" msgid "If you wish to use a different currency rate than the one set in :menuselection:`Accounting --> Configuration --> Settings --> Currencies`, click the :guilabel:`Exchange Rates` button and change the rate of the foreign currencies in the report." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:None +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:-1 msgid "Menu to manually change exchange rates." msgstr "" @@ -1394,7 +1413,7 @@ msgstr "" msgid "When manually changing **exchange rates**, a yellow banner appears allowing you to reset back to Odoo's rate. To do so, simply click on :guilabel:`Reset to Odoo's Rate`." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:None +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:-1 msgid "Banner to reset back to Odoo's rates." msgstr "" @@ -1410,7 +1429,7 @@ msgstr "" msgid "Once posted, the :guilabel:`adjustment` column should indicate `0.00`, meaning all **unrealized gains/losses** have been adjusted." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:None +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:-1 msgid "Unrealized Currency Gains/Losses report once adjusted." msgstr "" @@ -1880,7 +1899,6 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:15 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:85 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:85 msgid "Equity" msgstr "" @@ -1890,13 +1908,11 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:19 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:89 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:89 msgid "Income" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:20 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:93 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:93 msgid "Expense" msgstr "" @@ -1904,7 +1920,7 @@ msgstr "" msgid "When browsing your chart of accounts, you can filter the accounts by number, in the left column, and also group them by :guilabel:`Account Type`." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:None +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:-1 msgid "Group the accounts by type in Odoo Accounting" msgstr "" @@ -2037,7 +2053,6 @@ msgstr "" msgid "Cost of Revenue" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:99 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:99 msgid "Other" msgstr "" @@ -2107,7 +2122,7 @@ msgstr "" msgid "To create a new account group, :ref:`developer mode ` and head to :menuselection:`Accounting app --> Configuration --> Account Groups`. Here, create a new group and enter the :guilabel:`name, code prefix, and company` to which that group account should be available. Note that you must enter the same code prefix in both :guilabel:`From` and :guilabel:`to` fields." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:None +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:-1 msgid "Account groups creation." msgstr "" @@ -2115,7 +2130,7 @@ msgstr "" msgid "To display your **Trial Balance** report with your account groups, go to :menuselection:`Accounting app-->Reporting-->Trial Balance`, then open the :guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:None +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:-1 msgid "Account Groups in the Trial Balance in Odoo Accounting" msgstr "" @@ -2194,7 +2209,7 @@ msgstr "" msgid "The step-by-step Accounting onboarding banner is composed of four steps:" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:None +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:-1 msgid "Step-by-step onboarding banner in Odoo Accounting" msgstr "" @@ -2223,7 +2238,7 @@ msgstr "" msgid "This menu allows you to add your company’s details such as the name, address, logo, website, phone number, email address, and Tax ID, or VAT number. These details are then displayed on your documents, such as on invoices." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:None +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:-1 msgid "Add your company's details in Odoo Accounting and Odoo Invoicing" msgstr "" @@ -2240,7 +2255,7 @@ msgid "Connect your bank account to your database and have your bank statements msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:58 -msgid ":doc:`Click here <../../bank/feeds/bank_synchronization>` for more information about this feature." +msgid ":doc:`Click here <../../bank/bank_synchronization>` for more information about this feature." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:60 @@ -2283,7 +2298,7 @@ msgstr "" msgid "Basic settings are displayed on this page to help you review your Chart of Accounts. To access all the settings of an account, click on the *double arrow button* at the end of the line." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:None +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:-1 msgid "Setup of the Chart of Accounts and their opening balances in Odoo Accounting" msgstr "" @@ -2307,7 +2322,7 @@ msgstr "" msgid "The Invoicing onboarding banner is composed of four main steps:" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:None +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:-1 msgid "Step-by-step onboarding banner in Odoo Invoicing" msgstr "" @@ -2343,7 +2358,7 @@ msgstr "" msgid "You can also add your *Company Tagline* and the content of the documents’ *footer*. Note that Odoo automatically adds the company's phone number, email, website URL, and Tax ID (or VAT number) to the footer, according to the values you previously configured in the :ref:`Company Data `." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:None +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:-1 msgid "Document layout configuration in Odoo Invoicing" msgstr "" @@ -2377,7 +2392,7 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:189 #: ../../content/applications/finance/accounting/payables/pay/sepa.rst:135 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:68 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:17 #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:123 msgid ":doc:`../../bank/setup/bank_accounts`" msgstr "" @@ -2386,6 +2401,10 @@ msgstr "" msgid ":doc:`chart_of_accounts`" msgstr "" +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:191 +msgid ":doc:`../../bank/bank_synchronization`" +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/main_concept.rst:3 msgid "Main accounting concepts" msgstr "" @@ -2670,7 +2689,6 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:107 #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:128 #: ../../content/applications/finance/accounting/others/analytic/usage.rst:64 -#: ../../content/applications/finance/accounting/others/analytic/usage.rst:64 #: ../../content/applications/finance/accounting/others/analytic/usage.rst:157 msgid "**Account**" msgstr "" @@ -3021,7 +3039,7 @@ msgstr "" msgid "First, we need to define what accounts relate to our project’s expenses. Go to :menuselection:`Accounting --> Configuration --> Management: Budgetary positions`, and click :guilabel:`New` to add a position. Add the accounts wherein expenses will be booked." msgstr "" -#: ../../content/applications/finance/accounting/others/adviser/budget.rst:None +#: ../../content/applications/finance/accounting/others/adviser/budget.rst:-1 msgid "display the Smith and Co expenses" msgstr "" @@ -3029,7 +3047,7 @@ msgstr "" msgid "Let's repeat the steps to create a budgetary position that reflects the revenue." msgstr "" -#: ../../content/applications/finance/accounting/others/adviser/budget.rst:None +#: ../../content/applications/finance/accounting/others/adviser/budget.rst:-1 msgid "display the Smith and Co revenue" msgstr "" @@ -3049,7 +3067,7 @@ msgstr "" msgid "When creating a new customer invoice and/or vendor bill, you have to refer to this analytic account." msgstr "" -#: ../../content/applications/finance/accounting/others/adviser/budget.rst:None +#: ../../content/applications/finance/accounting/others/adviser/budget.rst:-1 msgid "add analytic accounts in a new invoice or bill." msgstr "" @@ -3065,7 +3083,7 @@ msgstr "" msgid "First, fill in your :guilabel:`Budget Name`. Then, select the :guilabel:`Period` wherein the budget is applicable. Next, add the :guilabel:`Budgetary Position` you want to track, define the related :guilabel:`Analytic Account`, and add the :guilabel:`Planned Amount`." msgstr "" -#: ../../content/applications/finance/accounting/others/adviser/budget.rst:None +#: ../../content/applications/finance/accounting/others/adviser/budget.rst:-1 msgid "budget lines display" msgstr "" @@ -3503,7 +3521,6 @@ msgstr "" msgid "Credit Note for defective materials" msgstr "" -#: ../../content/applications/finance/accounting/others/analytic/usage.rst:70 #: ../../content/applications/finance/accounting/others/analytic/usage.rst:70 msgid "200" msgstr "" @@ -3663,7 +3680,6 @@ msgstr "" msgid "Service charges" msgstr "" -#: ../../content/applications/finance/accounting/others/analytic/usage.rst:165 #: ../../content/applications/finance/accounting/others/analytic/usage.rst:165 msgid "280" msgstr "" @@ -3864,8 +3880,6 @@ msgid "Avg Cost" msgstr "" #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:50 -#: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:50 -#: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:146 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:146 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:150 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:154 @@ -3931,21 +3945,17 @@ msgstr "" #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:56 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:84 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:86 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:103 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:105 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:107 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:119 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:121 -#: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:121 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:123 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:152 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:154 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:156 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:158 #: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:160 -#: ../../content/applications/finance/accounting/others/inventory/avg_price_valuation.rst:160 msgid "$12" msgstr "" @@ -4216,8 +4226,6 @@ msgstr "" msgid "The Exchange difference journal can be changed in your accounting settings." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange/full_reconcile_warning.rst:2 -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange/full_reconcile_warning.rst:2 #: ../../content/applications/finance/accounting/others/multicurrencies/exchange/full_reconcile_warning.rst:2 #: ../../content/applications/finance/accounting/others/multicurrencies/exchange/full_reconcile_warning.rst:2 msgid "In order for an exchange difference entry to be created automatically, the corresponding invoices and payments need to be fully reconciled. This means the invoices are fully paid and the payments are fully spent on invoices. If you partially pay 3 invoices from 2 payments, and the last invoice still has an amount due, there will be no exchange difference entry for any of them until that final amount is paid." @@ -4457,6 +4465,10 @@ msgstr "" msgid "Account payables" msgstr "" +#: ../../content/applications/finance/accounting/payables/misc.rst:5 +msgid "Miscellaneous" +msgstr "" + #: ../../content/applications/finance/accounting/payables/misc/forecast.rst:3 msgid "Forecast future bills to pay" msgstr "" @@ -4683,7 +4695,7 @@ msgstr "" msgid "To register the payment of multiple bills at once, go to :menuselection:`Accounting app --> Vendors --> Bills`. Then, select the bills you wish to register a payment for by **ticking** the boxes next to the bills. When done, either click :guilabel:`Register Payment` or :menuselection:`Action --> Register Payment`." msgstr "" -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:None +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:-1 msgid "Register payment button." msgstr "" @@ -4699,7 +4711,7 @@ msgstr "" msgid "The :guilabel:`Group Payments` option only appears when selecting two or more bills." msgstr "" -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:None +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:-1 msgid "Group payments options when registering a payment." msgstr "" @@ -4900,7 +4912,7 @@ msgstr "" msgid "To configure your account in the **Chart of Accounts**, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click on *Create*, and fill out the form." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Configuration of an Assets Account in Odoo Accounting" msgstr "" @@ -4922,7 +4934,7 @@ msgstr "" msgid "On a draft bill, select the right account for all the assets you are buying." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Selection of an Assets Account on a draft bill in Odoo Accounting" msgstr "" @@ -4936,7 +4948,7 @@ msgstr "" msgid "Start editing the product, go to the *Accounting* tab, select the right **Expense Account**, and save." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Change of the Assets Account for a product in Odoo" msgstr "" @@ -4955,9 +4967,9 @@ msgstr "" msgid "To do so, open your Purchases Journal by going to :menuselection:`Accounting --> Accounting --> Purchases`, select the journal item you want to modify, click on the account, and select the right one." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Modification of a posted journal item's account in Odoo Accounting" msgstr "" @@ -4983,7 +4995,7 @@ msgstr "" msgid "Click on **select related purchases** to link an existing journal item to this new entry. Some fields are then automatically filled out, and the journal item is now listed under the **Related Purchase** tab." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Assets entry in Odoo Accounting" msgstr "" @@ -4991,7 +5003,7 @@ msgstr "" msgid "Once done, you can click on *Compute Depreciation* (next to the *Confirm* button) to generate all the values of the **Depreciation Board**. This board shows you all the entries that Odoo will post to depreciate your asset, and at which date." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Depreciation Board in Odoo Accounting" msgstr "" @@ -5045,7 +5057,7 @@ msgstr "" msgid "Then, click on *Action*, select **Create Asset**, and fill out the form the same way you would do to :ref:`create a new entry `." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Create Asset Entry from a journal item in Odoo Accounting" msgstr "" @@ -5069,7 +5081,7 @@ msgstr "" msgid "An **increase in value** requires you to fill out additional fields related to the account movements and creates a new Asset entry with the **Value Increase**. The Gross Increase Asset Entry can be accessed with a Smart Button." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Gross Increase smart button in Odoo Accounting" msgstr "" @@ -5085,7 +5097,7 @@ msgstr "" msgid "To do so, open the asset you want to dispose of, click on *Sell or Dispose*, and fill out the form." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Disposal of Assets in Odoo Accounting" msgstr "" @@ -5127,7 +5139,7 @@ msgstr "" msgid "New buttons with all the models linked to that account appear at the top of the form. Clicking on a model button fills out the form according to that model." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Assets model button in Odoo Accounting" msgstr "" @@ -5157,7 +5169,7 @@ msgstr "" msgid "**Create and validate:** you must also select an Asset Model (see: `Assets Models`_). Whenever a transaction is posted on the account, an *Assets entry* is created and immediately validated." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:-1 msgid "Automate Assets on an account in Odoo Accounting" msgstr "" @@ -5203,7 +5215,7 @@ msgstr "" msgid "Configure a Deferred Expense Account" msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 msgid "Configuration of a Deferred Expense Account in Odoo Accounting" msgstr "" @@ -5215,11 +5227,11 @@ msgstr "" msgid "On a draft bill, select the right account for all the products of which the expenses must be deferred." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 msgid "Selection of a Deferred Expense Account on a draft bill in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 msgid "Change of the Expense Account for a product in Odoo" msgstr "" @@ -5243,7 +5255,7 @@ msgstr "" msgid "Click on **select related purchases** to link an existing journal item to this new entry. Some fields are then automatically filled out, and the journal item is now listed under the **Related Expenses** tab." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 msgid "Deferred Expense entry in Odoo Accounting" msgstr "" @@ -5251,7 +5263,7 @@ msgstr "" msgid "Once done, you can click on *Compute Deferral* (next to the *Confirm* button) to generate all the values of the **Expense Board**. This board shows you all the entries that Odoo will post to recognize your expense, and at which date." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 msgid "Expense Board in Odoo Accounting" msgstr "" @@ -5284,8 +5296,8 @@ msgstr "" msgid "Then, click on *Action*, select **Create Deferred Entry**, and fill out the form the same way you would do to `create a new entry`_." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Create Deferred Entry from a journal item in Odoo Accounting" msgstr "" @@ -5313,7 +5325,7 @@ msgstr "" msgid "When you create a new Deferred Expense entry, fill out the **Deferred Expense Account** with the right recognition account." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 msgid "Deferred Expense model button in Odoo Accounting" msgstr "" @@ -5337,7 +5349,7 @@ msgstr "" msgid "**Create and validate:** you must also select a Deferred Expense Model (see: `Deferred Expense Models`_). Whenever a transaction is posted on the account, a *Deferred Expenses entry* is created and immediately validated." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:-1 msgid "Automate Deferred Expense on an account in Odoo Accounting" msgstr "" @@ -5365,7 +5377,7 @@ msgstr "" msgid "Go to :menuselection:`Accounting --> Settings --> Bill Digitalization`, and choose whether the bills should be processed automatically (with OCR) or manually (on demand)." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/ocr.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/ocr.rst:-1 msgid "Activate the feature going to the settings application in Odoo Accounting" msgstr "" @@ -5385,7 +5397,7 @@ msgstr "" msgid "Once the data is extracted from the PDF, you can correct it if necessary by clicking on the respective tag (available in *Edit* mode), and selecting the right information instead." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/ocr.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/ocr.rst:-1 msgid "Example of a scanned bill in Odoo Accounting" msgstr "" @@ -5394,7 +5406,7 @@ msgid "The more bills you scan, the better the system gets at identifying the co msgstr "" #: ../../content/applications/finance/accounting/payables/supplier_bills/ocr.rst:44 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:36 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:45 msgid "Pricing" msgstr "" @@ -5407,7 +5419,7 @@ msgid "To buy credits, go to :menuselection:`Accounting --> Configuration --> Se msgstr "" #: ../../content/applications/finance/accounting/payables/supplier_bills/ocr.rst:53 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:45 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:55 msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" @@ -5439,7 +5451,7 @@ msgstr "" msgid "To record a new receipt, go to :menuselection:`Accounting --> Vendors --> Receipts`, click on *Create*, fill out the form, and click on *Post*." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/purchase_receipts.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/purchase_receipts.rst:-1 msgid "Fill out the draft purchase receipt in Odoo Accounting" msgstr "" @@ -5459,7 +5471,7 @@ msgstr "" msgid "To do so, click on the **Journal Items** tab, change the accounts and values according to your needs, and click on *Post*." msgstr "" -#: ../../content/applications/finance/accounting/payables/supplier_bills/purchase_receipts.rst:None +#: ../../content/applications/finance/accounting/payables/supplier_bills/purchase_receipts.rst:-1 msgid "Change the accounts used in the journal entry to record a purchase receipt." msgstr "" @@ -5724,7 +5736,7 @@ msgstr "" msgid "Configure a Deferred Revenue Account" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Configuration of a Deferred Revenue Account in Odoo Accounting" msgstr "" @@ -5744,7 +5756,7 @@ msgstr "" msgid "On a draft invoice, select the right account for all the products of which the incomes must be deferred." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Selection of a Deferred Revenue Account on a draft invoice in Odoo Accounting" msgstr "" @@ -5756,7 +5768,7 @@ msgstr "" msgid "Start editing the product, go to the *Accounting* tab, select the right **Income Account**, and save." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Change of the Income Account for a product in Odoo" msgstr "" @@ -5784,7 +5796,7 @@ msgstr "" msgid "Click on **select related purchases** to link an existing journal item to this new entry. Some fields are then automatically filled out, and the journal item is now listed under the **Related Sales** tab." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Deferred Revenue entry in Odoo Accounting" msgstr "" @@ -5792,7 +5804,7 @@ msgstr "" msgid "Once done, you can click on *Compute Revenue* (next to the *Confirm* button) to generate all the values of the **Revenue Board**. This board shows you all the entries that Odoo will post to recognize your revenue, and at which date." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Revenue Board in Odoo Accounting" msgstr "" @@ -5844,7 +5856,7 @@ msgstr "" msgid "When you create a new Deferred Revenue entry, fill out the **Deferred Revenue Account** with the right recognition account." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Deferred Revenue model button in Odoo Accounting" msgstr "" @@ -5868,7 +5880,7 @@ msgstr "" msgid "**Create and validate:** you must also select a Deferred Revenue Model (see: `Deferred Revenue Models`_). Whenever a transaction is posted on the account, a *Deferred Revenues entry* is created and immediately validated." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:-1 msgid "Automate Deferred Revenue on an account in Odoo Accounting" msgstr "" @@ -5980,7 +5992,7 @@ msgstr "" msgid "Go to :menuselection:`Accounting --> Configuration --> Journals --> Customer Invoices --> Advanced Settings --> Electronic Invoicing` and enable the formats you need for this journal." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:-1 msgid "Select the EDI format you need" msgstr "" @@ -6049,63 +6061,75 @@ msgid "Once the new module is installed, UBL 2.0 and UBL 2.1 formats no longer a msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:3 -msgid "Add EPC QR Codes to invoices" +msgid "EPC QR codes" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:5 -msgid "European Payments Council Quick Response Code, or **EPC QR Code**, are two-dimensional barcodes that customers can scan with their **mobile banking applications** to initiate a **SEPA Credit Transfer (SCT)**, and pay their invoices instantly." +msgid "European Payments Council quick response codes, or **EPC QR codes**, are two-dimensional barcodes that customers can scan with their **mobile banking applications** to initiate a **SEPA credit transfer (SCT)** and pay their invoices instantly." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:11 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:9 msgid "In addition to bringing ease of use and speed, it greatly reduces typing errors that would potentially make for payment issues." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:16 -msgid "This feature is only available in several European countries such as Austria, Belgium, Finland, Germany, and The Netherlands." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:13 +msgid "This feature is only available for companies in several European countries such as Austria, Belgium, Finland, Germany, and the Netherlands." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:18 +msgid "`Odoo Academy: QR Code on Invoices for European Customers `_" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:23 -msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and activate the **SEPA QR Code** feature." +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and activate the :guilabel:`QR Codes` feature in the :guilabel:`Customer Payments` section." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:30 -msgid "Configure your Bank Account’s journal" +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:27 +msgid "Configure your bank account's journal" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:32 -msgid "Make sure that your *Bank Account* is correctly configured on Odoo with your IBAN and BIC." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:29 +msgid "Make sure that your :guilabel:`Bank Account` is correctly configured in Odoo with your IBAN and BIC." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:35 -msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open your *bank journal*, then fill out the *Bank Account* and *Bank* under the *Bank Account* tab." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:31 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open your bank journal, then fill out the :guilabel:`Account Number` and :guilabel:`Bank` under the :guilabel:`Bank Account Number` column." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:43 -msgid "Issue Invoices with EPC QR Codes" +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:-1 +msgid "Bank account number column in the bank journal" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:45 -msgid "EPC QR Codes are added automatically to your invoices, as long as you issue them to customers that are located in a country where this feature is available." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:39 +msgid "Issue invoices with EPC QR codes" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:49 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:41 +msgid "EPC QR codes are added automatically to your invoices. Customers whose bank supports making payments via EPC QR codes will be able to scan the code and pay the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:44 msgid "Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a new invoice." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:52 -msgid "Before posting it, open the *Other Info* tab. Odoo automatically fills out the *Bank Account* field with your IBAN." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:46 +msgid "Before posting it, open the :guilabel:`Other Info` tab. Odoo automatically fills out the :guilabel:`Recipient Bank` field with your IBAN." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:55 -msgid "Make sure that the account indicated is the one you want to use to receive your customer’s payment as Odoo uses this field to generate the EPC QR Code." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:50 +msgid "In the :guilabel:`Other Info` tab, the account indicated in the :guilabel:`Recipient Bank` field is used to receive your customer's payment. Odoo automatically populates this field with your IBAN by default and uses it to generate the EPC QR code." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:63 -msgid "If you want to issue an invoice without an EPC QR Code, remove the IBAN indicated in the *Bank Account* field, under the *Other Info* tab of the invoice." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:54 +msgid "When the invoice is printed or previewed, the QR code is included at the bottom." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:69 -msgid "`Odoo Academy: QR Code on Invoices for European Customers `_" +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:-1 +msgid "QR code on a customer invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:60 +msgid "If you want to issue an invoice without an EPC QR code, remove the IBAN indicated in the :guilabel:`Recipient Bank` field, under the :guilabel:`Other Info` tab of the invoice." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/overview.rst:3 @@ -6424,7 +6448,7 @@ msgstr "" msgid "In the following example, 30% is due on the day of issuance, and the balance is due at the end of the following month." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:-1 msgid "Example of Payment Terms. The last line is the balance due on the 31st of the following\n" "month." msgstr "" @@ -6485,7 +6509,7 @@ msgstr "" msgid "This makes for easier *Follow-ups* and *Reconciliation* since Odoo takes each due date into account, rather than just the balance due date. It also helps to get an accurate *Aged Receivable report*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:-1 msgid "The amount debited on the Account Receivable is split into two Journal Items with distinct\n" "Due Dates" msgstr "" @@ -6528,54 +6552,62 @@ msgid "The $1000 debited on the Account Receivable is split into two distinct *J msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:5 -msgid "Send your invoices by post (Snailmail)" +msgid "Snailmail" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:7 -msgid "Direct mail is a great way to capture individuals’ attention at a time where inboxes are always full. Odoo allows you to send invoices and follow-up reports by post, worldwide, directly from your database." -msgstr "" - -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:12 -msgid "Set up Snailmail" +msgid "Sending direct mail can be an effective strategy for grabbing people's attention, especially when their email inboxes are overflowing. With Odoo, you have the ability to send invoices and follow-up reports through postal mail worldwide, all from within your database." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:14 -msgid "Go to :menuselection:`Accounting --> Settings --> Snailmail` and activate the feature." +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer invoices` section to activate :guilabel:`Snailmail`." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:16 -msgid "If you would like this option to be a default feature, enable *Send by Post* under *Default Sending Options*." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:17 +msgid "To make it a by-default feature, select :guilabel:`Send by Post` in the :guilabel:`Default Sending Options` section." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:-1 msgid "Under settings enable the snailmail feature in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:23 -msgid "Send your invoices by post" -msgstr "" - #: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:25 -msgid "Open your Invoice, click on the *Send & Print* button and select *Send by Post*." +msgid "Send invoices by post" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:None -msgid "Overview of an invoice and the option send by post available in Odoo Accounting" +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:27 +msgid "Open your invoice, click on :guilabel:`Send & Print` and select :guilabel:`Send by Post`. Make sure your customer’s address is set correctly, including the country, before sending the letter." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:32 -msgid "Make sure to have your customer’s address set correctly, and that it includes a country, before sending the letter." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:31 +msgid "Your document must respect the following rules to pass the validation before being sent:" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:33 +msgid "Margins must be **5 mm** on all sides. As Odoo forces the outer margins by filling them with white before sending the snailmail, it can results in the user's custom being cut off if it protrudes into the margins. To check the margins, go to :menuselection:`Settings --> General Settings` and scroll down to the :guilabel:`Business Documents` section, and open the external link." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:38 +msgid "A square of **15mm by 15mm** on the bottom left corner has to stay clear." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:39 -msgid "*Snailmail* is an *In-App Purchase (IAP)* service which requires prepaid stamps (=credits) to work. Sending one document consumes one stamp." +msgid "The postage area has to stay clear (click :download:`here ` to get more info about the area)." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:42 -msgid "To buy stamps, go to :menuselection:`Accounting --> Configuration --> Settings --> Snailmail` and click on *Buy credits*, or go to :menuselection:`Settings --> Odoo IAP` and click on *View my Services*." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:41 +msgid "Pingen (Odoo Snailmail service provider) scans the area to process the address, so if something gets written outside the area, it is not counted as part of the address." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:47 +msgid "Snailmail is an :doc:`../../../../general/in_app_purchase` service that requires prepaid stamps (=credits) to work. Sending one document consumes one stamp." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:50 +msgid "To buy stamps, go to :menuselection:`Accounting --> Configuration --> Settings --> Customer invoices: Snailmail`, click on :guilabel:`Buy credits`, or go to :menuselection:`Settings --> In-App Purchases: Odoo IAP`, and click on :guilabel:`View my Services`." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:57 msgid "Click `here `_ to know about our *Privacy Policy*." msgstr "" @@ -6611,7 +6643,7 @@ msgstr "" msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open the Journal you want to edit, click on *Edit*, and open the *Advanced Settings* tab. In the *Payment Method Types* section, enable **Batch Deposit**, and click on *Save*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:-1 msgid "Payment Method Types in a journal's advanced settings" msgstr "" @@ -6631,7 +6663,7 @@ msgstr "" msgid ":doc:`Register the payments ` on the bank account on which you plan to deposit them by opening the *Customer Invoice* for which you received a payment, and clicking on *Register Payment*. There, select the appropriate Journal linked to your bank account and select *Batch Deposit* as Payment Method." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:-1 msgid "Registering a customer payment as part of a Batch Deposit in Odoo Accounting" msgstr "" @@ -6651,7 +6683,7 @@ msgstr "" msgid "To add the payments to a Batch Deposit, go to :menuselection:`Accounting --> Customers --> Batch Payments`, and click on *Create*. Next, select the Bank and Payment Method, then click on *Add a line*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:-1 msgid "Filling out a new Inbound Batch Payment form on Odoo Accounting" msgstr "" @@ -6659,7 +6691,7 @@ msgstr "" msgid "Select all payments to include in the current Batch Deposit and click on *Select*. You can also record a new payment and add it to the list by clicking on *Create*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:-1 msgid "Selection of all payments to include in the Batch Deposit" msgstr "" @@ -6675,7 +6707,7 @@ msgstr "" msgid "The *Batch Payments* tab won't appear if a Partner is selected for this bank statement line." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:-1 msgid "Reconciliation of the Batch Payment with all its transactions" msgstr "" @@ -6715,7 +6747,7 @@ msgstr "" msgid "Go to :menuselection:`Accounting app --> Configuration --> Settings`, activate :guilabel:`SEPA Direct Debit (SDD)`, and click on :guilabel:`Save`. Enter your company's :guilabel:`Creditor Identifier`. This number is provided by your bank institution, or the authority responsible for delivering them." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:-1 msgid "Add a SEPA Creditor Identifier to Odoo Accounting" msgstr "" @@ -6807,7 +6839,7 @@ msgstr "" msgid "To generate your `.xml` file of multiple pending SDD payments, you can create a batch payment. To do so, go to :menuselection:`Accounting app --> Customers --> Payments`, select the needed payments, then click on :guilabel:`Action`, and finally :guilabel:`Create a batch Payment`. Once you click on :guilabel:`Validate`, the `.xml` file is directly available for download." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:-1 msgid "Generate an .XML file for your SDD payments in Odoo Accounting" msgstr "" @@ -6992,23 +7024,23 @@ msgid "To configure a :guilabel:`Follow-Up Action`, go to :menuselection:`Accoun msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:20 -msgid "Send an Email" +msgid "Send an email;" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:21 -msgid ":ref:`Send an SMS Message `" +msgid ":ref:`Send an SMS message `;" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:22 -msgid "Print a Letter" +msgid "Print a letter;" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:23 -msgid ":ref:`Send a Letter `" +msgid ":ref:`Send a letter `;" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:24 -msgid "Manual Action (creates a task)" +msgid "Manual action (creates a task)." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:26 @@ -7059,7 +7091,7 @@ msgstr "" msgid "To know whether a customer usually pays late or not, you can set a trust level by marking them as :guilabel:`Good Debtor`, :guilabel:`Normal Debtor`, or :guilabel:`Bad Debtor` on their follow-up report. To do so, click on the bullet next to the customer's name and select a trust level." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:-1 msgid "Set debtor's trust level" msgstr "" @@ -7071,6 +7103,18 @@ msgstr "" msgid "You can send reminder emails in batches from the :guilabel:`Follow-up Reports` page. To do so, select all the reports you would like to process, click on the :guilabel:`Action` gear icon, and select :guilabel:`Process follow-ups`." msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:78 +msgid ":doc:`../../../../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:79 +msgid ":doc:`../../../../marketing/sms_marketing/pricing/pricing_and_faq`" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:80 +msgid ":doc:`../customer_invoices/snailmail`" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:3 msgid "Invoice online payment" msgstr "" @@ -7079,7 +7123,7 @@ msgstr "" msgid "To make it more convenient for your customers to pay the invoices you issue, you can activate the **Invoice Online Payment** feature, which adds a *Pay Now* button on their **Customer Portal**. This allows your customers to see their invoices online and pay directly with their favorite payment method, making the payment process much easier." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:-1 msgid "Payment acquirer choice after having clicked on \"Pay Now\"" msgstr "" @@ -7103,7 +7147,7 @@ msgstr "" msgid "After issuing the invoice, click on *Send & Print* and send the invoice by email to the customer. They will receive an email with a link that redirects them to the invoice on their **Customer Portal**." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:-1 msgid "Email with a link to view the invoice online on the Customer Portal." msgstr "" @@ -7111,7 +7155,7 @@ msgstr "" msgid "They can choose which Payment Acquirer to use by clicking on *Pay Now*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:-1 msgid "\"Pay now\" button on an invoice in the Customer Portal." msgstr "" @@ -7136,7 +7180,7 @@ msgid "If a payment is **not linked to an invoice or bill**, the customer has an msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:16 -msgid ":doc:`Internal transfers <../../bank/misc/interbank>`" +msgid ":doc:`Internal transfers <../../bank/interbank>`" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:18 @@ -7155,7 +7199,7 @@ msgstr "" msgid "The information icon near the payment line displays more information about the payment. You can access additional information, such as the related journal, by clicking on :guilabel:`View`." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:-1 msgid "See detailed information of a payment" msgstr "" @@ -7199,7 +7243,7 @@ msgstr "" msgid "A blue banner appears when you validate a new invoice or bill and there is an outstanding payment for this specific customer or vendor. It can easily be matched from the invoice or the bill by clicking on :guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:-1 msgid "Shows the ADD option to reconcile an invoice or a bill with a payment" msgstr "" @@ -7243,7 +7287,7 @@ msgstr "" msgid "To reconcile several outstanding payments or invoices at once, for a specific customer or vendor, the batch reconciliation feature can be used. Go to :menuselection:`Accounting --> Reporting --> Aged Receivable / Aged Payable`. You now see all transactions that have not been reconciled yet, and when you select a customer or vendor, the :guilabel:`Reconcile` option is displayed." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:None +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:-1 msgid "See the reconcile option" msgstr "" @@ -7319,7 +7363,7 @@ msgstr "" msgid ":guilabel:`Journal`: select the journal in which to record the tax return." msgstr "" -#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:-1 msgid "Configure how often tax returns have to be made in Odoo Accounting" msgstr "" @@ -7335,7 +7379,7 @@ msgstr "" msgid "Odoo generates tax reports based on the :guilabel:`Tax Grids` settings that are configured on your taxes. Therefore, it is crucial to make sure that all recorded transactions use the right taxes. You can see the :guilabel:`Tax Grids` by opening the :guilabel:`Journal Items` tab of any invoice and bill." msgstr "" -#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:-1 msgid "see which tax grids are used to record transactions in Odoo Accounting" msgstr "" @@ -7343,7 +7387,7 @@ msgstr "" msgid "To configure your tax grids, go to :menuselection:`Accounting --> Configuration --> Taxes`, and open the tax you want to modify. There, you can edit your tax settings, along with the tax grids that are used to record invoices or credit notes." msgstr "" -#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:-1 msgid "Configure taxes and their tax grids in Odoo Accounting" msgstr "" @@ -7371,7 +7415,7 @@ msgstr "" msgid "To check the current :guilabel:`Tax Lock Date`, or to edit it, go to :menuselection:`Accounting --> Accounting --> Actions: Lock Dates`." msgstr "" -#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:-1 msgid "Lock your tax for a specific period in Odoo Accounting" msgstr "" @@ -7384,7 +7428,7 @@ msgstr "" msgid "Once all the transactions involving taxes have been posted for the period you want to report, open your :guilabel:`Tax Report` by going to :menuselection:`Accounting --> Reporting --> Audit Reports: Tax Report`. Make sure to select the right period you want to declare by using the date filter, this way you can have an overview of your tax report. From this view, you can easily access different formats of your tax report, such as `PDF` and XLSX. These include all the values to report to the tax authorities, along with the amount you have to pay or be refunded." msgstr "" -#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:-1 msgid "download the PDF with your Tax Report in Odoo Accounting" msgstr "" @@ -7548,7 +7592,7 @@ msgstr "" msgid "The report's first section is an overview of all your journals and their configuration. Under the inalterability check column, you can see whether or not a journal's posted entries are locked with a hash (V) or not (X). The coverage column tells you when a journal's posted entries started being locked." msgstr "" -#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:None +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:-1 msgid "Configuration report for two journals" msgstr "" @@ -7556,7 +7600,7 @@ msgstr "" msgid "The second section gives you the result of the data consistency check for each hashed journal. You can view the first hashed entry and its corresponding hash and the last hashed entry and its corresponding hash." msgstr "" -#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:None +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:-1 msgid "Data consistency check report for a journal" msgstr "" @@ -7741,7 +7785,7 @@ msgid "Taxation" msgstr "" #: ../../content/applications/finance/accounting/taxation/fiscal_year.rst:5 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Fiscal year" msgstr "" @@ -7774,7 +7818,7 @@ msgid "Corroborate that all **received payments** have been entered and recorded msgstr "" #: ../../content/applications/finance/accounting/taxation/fiscal_year/close_fiscal_year.rst:23 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1229 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1230 msgid "Year-end checklist" msgstr "" @@ -7811,7 +7855,7 @@ msgid "Year-end manual adjustments, using the **Adviser Journal Entries** menu ( msgstr "" #: ../../content/applications/finance/accounting/taxation/fiscal_year/close_fiscal_year.rst:54 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1251 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1252 msgid "**Work in Progress**." msgstr "" @@ -7820,7 +7864,7 @@ msgid "**Depreciation Journal Entries**." msgstr "" #: ../../content/applications/finance/accounting/taxation/fiscal_year/close_fiscal_year.rst:58 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1253 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1254 msgid "**Loans**." msgstr "" @@ -8061,7 +8105,7 @@ msgstr "" msgid "If you do not yet have credentials, click on :guilabel:`How to Get Credentials`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:-1 msgid "Configure Avatax settings" msgstr "" @@ -8077,7 +8121,7 @@ msgstr "" msgid "Before using the integration, specify an :guilabel:`Avatax Category` on the product categories." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:-1 msgid "Specify Avatax Category on products" msgstr "" @@ -8085,7 +8129,7 @@ msgstr "" msgid "Avatax Categories may be overridden or set on individual products as well." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:-1 msgid "Override product categories as needed" msgstr "" @@ -8097,7 +8141,7 @@ msgstr "" msgid "Manually validate customer addresses by clicking the :guilabel:`Validate address` link in the customer form view." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:-1 msgid "Validate customer addresses" msgstr "" @@ -8105,7 +8149,7 @@ msgstr "" msgid "If preferred, choose to keep the newly validated address or the original address in the wizard that pops up." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:-1 msgid "Address validation wizard" msgstr "" @@ -8190,7 +8234,7 @@ msgid "A few days later, you receive the payment:" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:66 -#: ../../content/applications/finance/payment_acquirers.rst:240 +#: ../../content/applications/finance/payment_acquirers.rst:239 msgid "Bank Journal" msgstr "" @@ -8218,7 +8262,7 @@ msgstr "" msgid "**Default Taxes** define which :doc:`taxes ` are automatically selected when there is no other indication about which tax to use. For example, Odoo prefills the **Taxes** field with the Default Taxes when you create a new product or add a new line on an invoice." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:-1 msgid "Odoo fills out the Tax field automatically according to the Default Taxes" msgstr "" @@ -8234,7 +8278,7 @@ msgstr "" msgid "To change your **Default Taxes**, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes --> Default Taxes`, select the appropriate taxes for your default **Sales Tax** and **Purchase Tax**, and click on *Save*." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:-1 msgid "Define which taxes to use by default on Odoo" msgstr "" @@ -8281,7 +8325,7 @@ msgstr "" msgid "Go to :menuselection:`Accounting/Invoicing --> Settings --> Taxes`, then enable **EU intra-community Distance Selling** (or **EU Digital Goods VAT** if you created your database before July 1, 2021), and *Save*." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/eu_distance_selling.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/eu_distance_selling.rst:-1 msgid "EU intra-community Distance Selling feature in Odoo Accounting settings" msgstr "" @@ -8325,7 +8369,7 @@ msgstr "" msgid "**Fiscal Positions** allow you to create *sets of rules* to automatically adapt the taxes and the accounts used for a transaction." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:-1 msgid "Example: Belgian to Intra-Community tax mapping with Fiscal Positions in Odoo Accounting" msgstr "" @@ -8397,7 +8441,7 @@ msgstr "" msgid "**Country Group** / **Country**: The Fiscal Position is applied to these countries." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:-1 msgid "Example of settings to apply a Fiscal Position automatically" msgstr "" @@ -8429,8 +8473,7 @@ msgstr "" msgid "To do so, open the partner's contact form, go to the **Sales & Purchase** tab, edit the **Fiscal Position** field, and click on *Save*." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:None -#: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:-1 msgid "Selection of a Fiscal Position on a Sales Order / Invoice / Bill in Odoo Accounting" msgstr "" @@ -8520,7 +8563,7 @@ msgstr "" msgid "Register an account on `TaxCloud.com `_ and complete the setup. Once you go live, get the :guilabel:`TaxCloud API Keys` by clicking on :guilabel:`Stores`, then :guilabel:`Get Details`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:-1 msgid "Example of a store's TaxCloud API Keys" msgstr "" @@ -8588,7 +8631,7 @@ msgstr "" msgid "To do so, go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Chart of Accounts`, find the company's :guilabel:`Tax Payable` account, and click on :guilabel:`Setup`. Take note of the number after `id=` in the URL string; it is the **Tax Payable account ID** and will be used later." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:-1 msgid "Example of Tax Payable account id in the URL string" msgstr "" @@ -8600,7 +8643,7 @@ msgstr "" msgid "Click on :guilabel:`Field` drop-down menu and then on :guilabel:`Search More...`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:-1 msgid "User-defined Defaults Field search" msgstr "" @@ -8608,7 +8651,7 @@ msgstr "" msgid "Use the search bar to filter for the :guilabel:`Tax Repartition Line` model, and use it a second time to filter for the :guilabel:`Account` field. Select the line with :guilabel:`Tax Repartition Line` under the :guilabel:`Model` column." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:-1 msgid "Searching for the Tax Repartition Line model and Account field" msgstr "" @@ -8620,7 +8663,7 @@ msgstr "" msgid "Select the company for which this configuration should apply under the :guilabel:`Company` field and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:-1 msgid "Example of a User-defined Defaults configuration" msgstr "" @@ -8636,7 +8679,7 @@ msgstr "" msgid "You can configure Odoo to automatically detect to which customers the fiscal position should be applied. To do so, go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Fiscal Positions` and select :guilabel:`Automatic Tax Mapping (TaxCloud)`. Enable :guilabel:`Detect Automatically` and then :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:-1 msgid "Detect Automatically setting on the TaxCloud fiscal position" msgstr "" @@ -8680,7 +8723,7 @@ msgstr "" msgid "To activate Sale Taxes, go to :menuselection:`Accounting --> Configuration --> Taxes` and use the *Activate* toggle button to activate or deactivate a tax." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:-1 msgid "Activate pre-configured taxes in Odoo Accounting" msgstr "" @@ -8688,7 +8731,7 @@ msgstr "" msgid "To edit or create a **Tax**, go to :menuselection:`Accounting --> Configuration --> Taxes` and open a tax or click on *Create*." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:-1 msgid "Edition of a tax in Odoo Accounting" msgstr "" @@ -8788,11 +8831,8 @@ msgstr "" msgid "Total" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:88 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:88 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:103 -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:103 -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:117 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:117 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:233 msgid "1,000" @@ -8890,7 +8930,7 @@ msgstr "" msgid "Allocate with precision the amount of the taxable basis or percentages of the computed tax to multiple accounts and Tax Grids." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:-1 msgid "Allocate tax amounts to the right accounts and tax grids" msgstr "" @@ -8926,7 +8966,7 @@ msgstr "" msgid "The label of the tax, as displayed on each invoice line in the **Taxes** column. This is the :ref:`label ` visible to *front end* users, on exported invoices, on their Customer Portals, etc." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:-1 msgid "The Label on Invoices is displayed on each invoice line" msgstr "" @@ -8942,7 +8982,7 @@ msgstr "" msgid "Tax groups include different iterations of the same tax. This can be useful when you must record differently the same tax according to :doc:`Fiscal Positions `." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:-1 msgid "The Tax Group name is different from the Label on Invoices" msgstr "" @@ -9010,7 +9050,7 @@ msgstr "" msgid "You can configure a new :ref:`Group of Taxes ` to include this tax, or add it directly to a product line." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:-1 msgid "The eco-tax is taken into the basis of the 21% VAT tax" msgstr "" @@ -9046,7 +9086,7 @@ msgstr "" msgid "To enable this feature, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, enable the **Verify VAT Numbers** feature, and click on *Save*." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:-1 msgid "Enable \"Verify VAT Numbers\" in Odoo Accounting" msgstr "" @@ -9058,7 +9098,7 @@ msgstr "" msgid "Whenever you create or modify a contact, make sure to fill out the **Country** and **VAT** fields." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:-1 msgid "Fill out the contact form with the country and VAT number before clicking on *Save*" msgstr "" @@ -9066,7 +9106,7 @@ msgstr "" msgid "When you click on *Save*, Odoo runs a VIES VAT number check, and displays an error message if the VAT number is invalid." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:None +#: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:-1 msgid "Odoo displays an error message instead of saving when the VAT number is invalid" msgstr "" @@ -9110,7 +9150,7 @@ msgstr "" msgid "To create workflow actions, go to :menuselection:`Documents --> Configuration --> Workspaces` and select the workspace where the action should apply. Click on the *Actions* smart button, and then on *Create*." msgstr "" -#: ../../content/applications/finance/documents.rst:None +#: ../../content/applications/finance/documents.rst:-1 msgid "Workflow actions smart button in Odoo Documents" msgstr "" @@ -9146,7 +9186,7 @@ msgstr "" msgid "**Owner**: the files must be associated with the owner set here." msgstr "" -#: ../../content/applications/finance/documents.rst:None +#: ../../content/applications/finance/documents.rst:-1 msgid "Example of a workflow action's basic condition in Odoo Documents" msgstr "" @@ -9166,7 +9206,7 @@ msgstr "" msgid "To access the *Domain* condition, the :ref:`developer mode ` needs to be activated. Once that's done, select the *Domain* condition type, and click on *Add Filter*." msgstr "" -#: ../../content/applications/finance/documents.rst:None +#: ../../content/applications/finance/documents.rst:-1 msgid "Activating the domain condition type in Odoo Documents" msgstr "" @@ -9174,7 +9214,7 @@ msgstr "" msgid "To create a rule, you typically select a field, an operator, and a value. For example, if you want to add a workflow action to all the PDF files inside a workspace, set the field to *Mime Type*, the operator to *contains*, and the value to *pdf*." msgstr "" -#: ../../content/applications/finance/documents.rst:None +#: ../../content/applications/finance/documents.rst:-1 msgid "Example of a workflow action's domain condition in Odoo Documents" msgstr "" @@ -9182,7 +9222,7 @@ msgstr "" msgid "Click on *Add node* (plus-circle icon) and *Add branch* (ellipsis icon) to add conditions and sub-conditions. You can then specify if your rule should match *ALL* or *ANY* conditions. You can also edit the rule directly using the *Code editor*." msgstr "" -#: ../../content/applications/finance/documents.rst:None +#: ../../content/applications/finance/documents.rst:-1 msgid "Add a node or a branch to a workflow action's condition in Odoo Documents" msgstr "" @@ -9258,7 +9298,7 @@ msgstr "" msgid "**Activities - Schedule Activity**: create a new activity linked to the file as configured in the action. You can choose to set the activity on the document owner." msgstr "" -#: ../../content/applications/finance/documents.rst:None +#: ../../content/applications/finance/documents.rst:-1 msgid "Example of a workflow action Odoo Documents" msgstr "" @@ -9267,244 +9307,557 @@ msgid "Expenses" msgstr "" #: ../../content/applications/finance/expenses.rst:7 -msgid "**Odoo Expenses** streamlines the management of expenses. Employees can submit their expenses; managers can approve them; accountants can record them and process the payments." +msgid "Odoo **Expenses** streamlines the management of expenses. After an employee submits their expenses in Odoo, the expenses are reviewed by management and accounting teams. Once approved, payments can then be processed and disbursed back to the employee for reimbursement(s)." msgstr "" -#: ../../content/applications/finance/expenses.rst:11 +#: ../../content/applications/finance/expenses.rst:12 msgid "`Odoo Expenses: product page `_" msgstr "" -#: ../../content/applications/finance/expenses.rst:14 -msgid "How to set expense types" +#: ../../content/applications/finance/expenses.rst:15 +msgid "Set expense types" msgstr "" -#: ../../content/applications/finance/expenses.rst:16 -msgid "The first step to track expenses is to configure the expense types (managed as products in Odoo) that your company allows, from the *Configuration* menu. When a specific expense is reimbursed at a fixed price, set a cost on the product. Otherwise keep the cost at 0.0 and employees will report the real cost per expense." +#: ../../content/applications/finance/expenses.rst:17 +msgid "The first step to track expenses is to configure the different *expense types* for the company (managed as *products* in Odoo). Each \"product\" can be as specific or generalized as needed. Go to :menuselection:`Expenses app --> Configuration --> Expense Products` to view the current expensable products in a default kanban view." msgstr "" -#: ../../content/applications/finance/expenses.rst:24 -msgid "Here are some examples:" +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Set expense costs on products." msgstr "" #: ../../content/applications/finance/expenses.rst:26 -msgid "Restaurant:" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:28 -#: ../../content/applications/finance/expenses.rst:34 -msgid "Cost: 0.00 (the cost of the ticket will be recorded on every expense)" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:29 -msgid "Travel with Personal Car:" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:31 -msgid "Cost: 0.30 (the price per mile reimbursed by the company is fixed)" +msgid "To create a new expense product, click :guilabel:`Create`. A product form will appear. Only two fields are required, the :guilabel:`Product Name` and the :guilabel:`Unit of Measure`. Enter the :guilabel:`Product Name` in the field, and select the :guilabel:`Unit of Measure` from the drop-down menu (most products will be set to :guilabel:`Units`)." msgstr "" #: ../../content/applications/finance/expenses.rst:32 -msgid "Hotel:" +msgid "The *Sales* app is where specification on the units of measure are created and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and ensure `Units of Measure` is checked off in the `Product Catalog` section. Click on the :guilabel:`Units of Measure` internal link to view, create, and edit the units of measure. Refer to :doc:`this document ` to learn more about units of measure and how to configure them." msgstr "" -#: ../../content/applications/finance/expenses.rst:36 -msgid "Others:" +#: ../../content/applications/finance/expenses.rst:43 +msgid "The :guilabel:`Cost` field on the product form is populated with a value of `0.00` by default. When a specific expense should always be reimbursed for a particular price, enter that amount in the :guilabel:`Cost` field. Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will report the actual cost when submitting an expense report." msgstr "" -#: ../../content/applications/finance/expenses.rst:38 -msgid "Cost: 0.0" +#: ../../content/applications/finance/expenses.rst:49 +msgid "Here are some examples for when to set a specific :guilabel:`Cost` on a product vs. leaving the :guilabel:`Cost` at `0.00`:" msgstr "" -#: ../../content/applications/finance/expenses.rst:40 -msgid "Don't forget to set an expense tax on each expense type (and an account if you use Odoo Accounting). It's usually a good practice to use a tax that is configured with :ref:`Tax Included in Price `. That way, employees report expenses with prices including taxes, which is usually the expected behaviour." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:48 -msgid "The *Sales* app allows you to specify units of measure for your expense types (units, miles, nights, etc.). Go to :menuselection:`Sales --> Configuration --> Settings` and check *Some products may be sold/purchased in different units of measure (advanced)*." +#: ../../content/applications/finance/expenses.rst:52 +msgid "**Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal, they enter the actual amount of the bill and will be reimbursed for that amount. An expense for a meal costing $95.23 would equal a reimbursement for $95.23." msgstr "" #: ../../content/applications/finance/expenses.rst:55 -msgid "How to record expenses" +msgid "**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for \"mileage\", they enter the number of miles driven, and are reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for $30.00." msgstr "" #: ../../content/applications/finance/expenses.rst:58 -msgid "Manually" +msgid "**Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for \"monthly parking\", the reimbursement would be for $75.00." msgstr "" #: ../../content/applications/finance/expenses.rst:60 -msgid "As an employee (Employee in user access rights), you can record expenses from :menuselection:`My Expenses --> Expenses to Submit`." +msgid "**Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and the reimbursement would be for $350.00." msgstr "" -#: ../../content/applications/finance/expenses.rst:66 -msgid "Select the related product and enter either the total amount you paid (with Quantity = 1) or the unit price if Quantity is countable (e.g. number of hotel nights)." +#: ../../content/applications/finance/expenses.rst:65 +msgid "Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It is recommended to check with the accounting department to determine the correct account to reference in this field as it will affect reports." msgstr "" #: ../../content/applications/finance/expenses.rst:69 -msgid "Enter the expense date." +msgid "Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields if applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included in Price `. Taxes will be automatically configured if this is set." msgstr "" -#: ../../content/applications/finance/expenses.rst:70 -msgid "Choose if you paid the bill on your own (and expect to be reimbursed) or if the company paid directly (e.g. if you used a company's credit card)." +#: ../../content/applications/finance/expenses.rst:76 +msgid "Record expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:72 -msgid "Set the bill reference, add some notes if requested and attach a photo/scan of the receipt from the discussion thread. That will help the manager and the accountant validate it." +#: ../../content/applications/finance/expenses.rst:79 +msgid "Manually create a new expense" msgstr "" -#: ../../content/applications/finance/expenses.rst:80 -msgid "In one click from emails" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:82 -msgid "Let your employees record their expenses from a simple email. Make a snapshot of the receipt and send it by email, or simply forward a bill!" +#: ../../content/applications/finance/expenses.rst:81 +msgid "To record a new expense, begin in the main :menuselection:`Expenses` app dashboard, which presents the default :guilabel:`My Expenses to Report` view. This view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses to Report`." msgstr "" #: ../../content/applications/finance/expenses.rst:85 -msgid "The only thing to do is setting up an email alias in :menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* @mycompany.odoo.com). For security purposes, only authenticated employee emails (cfr. *Work Email* in employee detail form) are accepted." +msgid "First, click :guilabel:`Create`, and then fill out the various fields on the form." msgstr "" -#: ../../content/applications/finance/expenses.rst:91 -msgid "The expense product is set automatically if the mail subject contains the product's internal reference in first position. Type the expense amount in the mail subject to set it on the expense too (e.g. Ref001 Food 100€)." +#: ../../content/applications/finance/expenses.rst:87 +msgid ":guilabel:`Description`: Enter a short description for the expense in the :guilabel:`Description` field. This should be short and informative, such as `lunch with client` or `hotel for conference`." msgstr "" -#: ../../content/applications/finance/expenses.rst:96 -msgid "How to submit expenses to managers" +#: ../../content/applications/finance/expenses.rst:90 +msgid ":guilabel:`Product`: Select the product from the drop-down menu that most closely corresponds to the expense. For example, an airplane ticket would be appropriate for an expense :guilabel:`Product` named :guilabel:`Air Travel`." msgstr "" -#: ../../content/applications/finance/expenses.rst:98 -msgid "When you are ready to submit your expenses to your manager (e.g. at the end of a business trip, or once a month), go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses from the list view and click on :menuselection:`Action --> Submit to Manager`. Save the newly created expense report (i.e. set of expenses), and wait for your manager to approve it." +#: ../../content/applications/finance/expenses.rst:93 +msgid ":guilabel:`Unit Price`: Enter the total amount paid for the expense in one of two ways:" msgstr "" -#: ../../content/applications/finance/expenses.rst:108 -msgid "You can also submit expenses one by one from the *Submit to Manager* button on the form view of an expense." +#: ../../content/applications/finance/expenses.rst:95 +msgid "If the expense is for one single item/expense, enter the cost in the :guilabel:`Unit Price` field, and leave the :guilabel:`Quantity` `1.00`." msgstr "" -#: ../../content/applications/finance/expenses.rst:111 -msgid "All your submitted expense reports can be found in :menuselection:`Expenses --> My Expenses --> Expense Reports`." +#: ../../content/applications/finance/expenses.rst:97 +msgid "If the expense is for multiples of the same item/expense, enter the price *per unit* in the :guilabel:`Unit Price` field, and enter the *quantity of units* in the :guilabel:`Quantity` field." msgstr "" -#: ../../content/applications/finance/expenses.rst:116 -msgid "How to approve expenses" +#: ../../content/applications/finance/expenses.rst:102 +msgid "In the case of a hotel stay, for example, the :guilabel:`Unit Price` would be set as the cost *per night*, and set the :guilabel:`Quantity` to the *number of nights* stayed." msgstr "" -#: ../../content/applications/finance/expenses.rst:118 -msgid "HR and team managers get an overview of all expense reports to validate from the top menu :menuselection:`To Approve --> Expense Reports to Approve`. Such users must have at least *Officers* access rights for *Expenses*." +#: ../../content/applications/finance/expenses.rst:105 +msgid ":guilabel:`Taxes`: If taxes were paid on the expense, select the tax percentage using the drop-down menu. Tax options are pre-configured based on the localization setting selected when the database was created. Adding any new taxes should only be done when necessary." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:110 +msgid "When a tax is selected, the :guilabel:`Total` value will update in real time to show the added taxes." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:113 +msgid ":guilabel:`Paid By`: Click the radio button to indicate who paid for the expense and should be reimbursed. If the employee paid for the expense (and should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the company paid directly instead (e.g. if the company credit card was used to pay for the expense) select :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:117 +msgid ":guilabel:`Expense Date`: Using the calendar module, enter the date the expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows to navigate to the correct month, then click on the specific day to enter the selection." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:120 +msgid ":guilabel:`Bill Reference`: If there is any reference text that should be included for the expense, enter it in this field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:122 +msgid ":guilabel:`Account`: Select the expense account that this expense should be logged on from the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:124 +msgid ":guilabel:`Employee`: Using the drop-down menu, select the employee this expense is for." msgstr "" #: ../../content/applications/finance/expenses.rst:125 -msgid "They can review expense reports, approve or reject them, as well as providing feedback thanks to the integrated communication tool." +msgid ":guilabel:`Customer to Reinvoice`: If the expense is something that should be paid for by a customer, select the customer that will be invoiced for this expense from the drop-down menu. For example, if a customer wishes to have an on-site meeting, and agrees to pay for the expenses associated with it (such as travel, hotel, meals, etc.), then all expenses tied to that meeting would indicate that customer as the :guilabel:`Customer to Reinvoice`." msgstr "" -#: ../../content/applications/finance/expenses.rst:131 -msgid "As a team manager you can easily find the expense reports of your team members. You need to be set as manager in the detail form of those employees." +#: ../../content/applications/finance/expenses.rst:130 +msgid ":guilabel:`Analytic Account`: Select the account the expense should be written against from the drop-down menu." msgstr "" -#: ../../content/applications/finance/expenses.rst:139 -msgid "How to post expenses in accounting" +#: ../../content/applications/finance/expenses.rst:132 +msgid ":guilabel:`Company`: If multiple companies are set-up, select the company this expense should be filed for from the drop-down menu. If there is only one company, this field will be automatically populated." msgstr "" -#: ../../content/applications/finance/expenses.rst:141 -msgid "Once expense reports approved by managers, the accounting department goes to :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to check accounts, products and taxes. They can click *Post Journal Entries* to post related journal entries into your books. To do so, the user must have following access rights:" +#: ../../content/applications/finance/expenses.rst:135 +msgid ":guilabel:`Notes...`: If any notes are needed in order to clarify the expense, enter them in the notes field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:138 +msgid "Once all the fields have been filled out, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "A filled in expense form for a client lunch." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:145 +msgid "Attach a receipt" msgstr "" #: ../../content/applications/finance/expenses.rst:147 -msgid "Accounting: Accountant or Adviser" +msgid "After the expense is saved, the next step is to attach a receipt. A new :guilabel:`Attach Receipt` button appears after the entry is saved, beneath the former :guilabel:`Save` button (which turns into an :guilabel:`Edit` button)." msgstr "" -#: ../../content/applications/finance/expenses.rst:148 -msgid "Expenses: Manager" +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Attach a receipt after saving the record." msgstr "" -#: ../../content/applications/finance/expenses.rst:151 -msgid "To post an expense, a *Home Address* must be set on the employee. If you get a related blocking message when posting, click the employee, go to *Personal Information* tab and select/create the contact of your employee in the address book. A contact has been automatically created if this person is using Odoo." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:158 -msgid "How to reimburse employees" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:160 -msgid "You can now see all the expense reports to reimburse in :menuselection:`Expenses --> Accountant --> Expense Reports To Pay`. To record the payment or pay by check, click *Register a Payment*." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:164 -msgid "See how you can easily manage the payment process in Odoo:" +#: ../../content/applications/finance/expenses.rst:155 +msgid "Click the new :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate to the receipt to be attached, and click :guilabel:`Open`. A new :guilabel:`Receipts` smart button appears at the top, and the new receipt is recorded in the chatter. More than one receipt can be attached to an individual expense, as needed. The number of receipts attached to the expense will be noted on the smart button." msgstr "" #: ../../content/applications/finance/expenses.rst:166 -msgid ":doc:`accounting/payables/pay/check`" +msgid "Automatically create new expenses from an email" msgstr "" -#: ../../content/applications/finance/expenses.rst:167 -msgid ":doc:`accounting/payables/pay/sepa`" +#: ../../content/applications/finance/expenses.rst:168 +msgid "Instead of individually creating each expense in the *Expenses* app, expenses can be automatically created by sending an email to an email alias." msgstr "" #: ../../content/applications/finance/expenses.rst:171 -msgid "How to re-invoice expenses to your customers" +msgid "To do so, first, an email alias needs to be configured. Go to :menuselection:`Expenses app --> Configuration --> Settings`. Ensure :guilabel:`Incoming Emails` is checked off." msgstr "" -#: ../../content/applications/finance/expenses.rst:173 -msgid "If you track expenses on customer projects, you can charge them back to your customers automatically." +#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses.rst:0 +msgid "Create the domain alias by clicking the link." msgstr "" #: ../../content/applications/finance/expenses.rst:179 -msgid "Enable **Customer Billing** in the Expenses settings" +msgid "If the domain alias needs to be set up, :guilabel:`Setup your domain alias` will appear beneath the incoming emails check box instead of the email address field. Refer to this documentation for setup instructions and more information: :doc:`/administration/maintain/domain_names`. Once the domain alias is configured, the email address field will be visible beneath the incoming emails section." msgstr "" -#: ../../content/applications/finance/expenses.rst:181 -msgid "Go to the product configuration menu and set the invoicing method on all your Expense types:" +#: ../../content/applications/finance/expenses.rst:185 +msgid "Next, enter the email address to be used in the email field, then click :guilabel:`Save`. Now that the email address has been entered, emails can be sent to that alias to create new expenses without having to be in the Odoo database." msgstr "" -#: ../../content/applications/finance/expenses.rst:184 -msgid "Ordered quantities: it will invoice expenses based on the ordered quantity" +#: ../../content/applications/finance/expenses.rst:189 +msgid "To submit an expense via email, create a new email and enter the product's *internal reference* code (if available) and the amount of the expense in the email subject. Next, attach the receipt to the email. Odoo creates the expense by taking the information in the email subject and combining it with the receipt." msgstr "" -#: ../../content/applications/finance/expenses.rst:187 -msgid "Delivered quantities: it will invoice expenses based on the expenses quantity" +#: ../../content/applications/finance/expenses.rst:194 +msgid "To check an expense product's internal reference, go to :menuselection:`Expenses app --> Configuration --> Expense Products`. If an internal reference is listed on the product, it is visible in this view as :guilabel:`(Ref###)`." msgstr "" -#: ../../content/applications/finance/expenses.rst:190 -msgid "At cost: will invoice expenses at their real cost." +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Internal reference numbers are listed in the main Expense Products view." msgstr "" -#: ../../content/applications/finance/expenses.rst:192 -msgid "At sales price: will invoice based on a fixed sales price set on the sale order." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:199 -msgid "Create an order" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:201 -msgid "As a salesman, create and confirm a Sales Order for the services delivered to your customer. If you don't put any expense in the order, it will be added automatically once posted by the accountant." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:206 -msgid "Link the expense to the Sale Order." +#: ../../content/applications/finance/expenses.rst:202 +msgid "To add an internal reference on an expense product, click on the product, then click :guilabel:`Edit`. In edit mode, enter the :guilabel:`Internal Reference` in the field. Beneath the :guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use this reference as a subject prefix when submitting by email.`." msgstr "" #: ../../content/applications/finance/expenses.rst:212 -msgid "Submit, validate and post expenses" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:214 -msgid "As a manager, make sure the analytic account is set on every expense line on approving expenses reports. Click the line to add one if missing. Employees are already able to set one when submitting." +msgid "For security purposes, only authenticated employee emails are accepted by Odoo when creating an expense from an email. To confirm an authenticated employee email address, go to the employee card in the :guilabel:`Employees` app, and refer to the :guilabel:`Work Email` in the main field." msgstr "" #: ../../content/applications/finance/expenses.rst:221 -msgid "As an accountant, post journal entries." +msgid "If submitting an expense via email for a $25.00 meal during a work trip, the email subject would be `Ref005 Meal $25.00`." msgstr "" #: ../../content/applications/finance/expenses.rst:224 -msgid "Invoice expenses" +msgid "Explanation:" msgstr "" #: ../../content/applications/finance/expenses.rst:226 -msgid "Now you can invoice the order. It shows up in :menuselection:`Sales --> Invoicing --> Sales` to Invoice. The expenses have been added automatically in the order lines. Such items show up in blue (i.e. to invoice)." +msgid "The :guilabel:`Internal Reference` for the expense product `Meals` is `Ref005`" msgstr "" -#: ../../content/applications/finance/expenses.rst:234 -msgid "e (i.e. to invoice)." +#: ../../content/applications/finance/expenses.rst:227 +msgid "The :guilabel:`Cost` for the expense is `$25.00`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:230 +msgid "Create an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:232 +msgid "When expenses are ready to submit (such as at the end of a business trip, or once a month), an *expense report* needs to be created. Go to the main :menuselection:`Expenses` app dashboard, which displays a default :guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My Expenses --> My Expenses to Report`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:237 +msgid "First, each individual expense for the report must be selected by clicking the check box next to each entry, or quickly select all the expenses in the list by clicking the check box next to :guilabel:`Expense Date`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Select the expenses to submit, then create the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:245 +msgid "Once the expenses have been selected, click the :guilabel:`Create Report` button. The new report appears with all the expenses listed, and the number of documents is visible in the :guilabel:`Documents` smart button." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:249 +msgid "It is recommended to add a short summary for each report to help keep expenses organized. Click the :guilabel:`Edit` button, and the :guilabel:`Expense Report Summary` field appears. Enter a short description for the expense report (such as `Client Trip NYC`, or `Repairs for Company Car`). Next, select a :guilabel:`Manager` from the drop-down menu to assign a manager to review the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Enter a short description and select a manager for the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:258 +msgid "If some expenses are not on the report that should be, they can still be added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense` tab. Click the check box next to each expense to add, then click :guilabel:`Select`. The items now appear on the report that was just created." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Add more expenses to the report before submitting." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:267 +msgid ":guilabel:`Add a line` only appears when the document is in edit mode. It does not appear otherwise." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:270 +msgid "When all edits have been completed, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:273 +msgid "Submit an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:275 +msgid "When an expense report is completed, the next step is to submit the report to a manager for approval. Reports must be individually submitted, and cannot be submitted in batches. Open the specific report from the list of expense reports (if the report is not already open). To view all expense reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:280 +msgid "If the list is large, grouping the results by status may be helpful since only reports that are in a :guilabel:`Draft` mode need to be submitted, reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Submit the report to the manager." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:289 +msgid "The status of each report is shown in the :guilabel:`Status` column on the far right. If the :guilabel:`Status` column is not visible, click the :guilabel:`⋮ (additional options)` icon at the end of the row, and check the box next to :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:293 +msgid "Click on a report to open it, then click :guilabel:`Submit To Manager`. After submitting a report, the next step is to wait for the manager to approve it." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:297 +msgid "The :ref:`expenses/approve`, :ref:`expenses/post`, and :ref:`expenses/reimburse` sections are **only** for users with the *necessary rights*." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:303 +msgid "Approve expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:305 +msgid "In Odoo, not just anyone can approve expense reports— only users with the necessary rights (or permissions) can. This means that a user must have at least *Team Approver* rights for the *Expenses* app. Employees with the necessary rights can review expense reports, and approve or reject them, as well as provide feedback thanks to the integrated communication tool." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:310 +msgid "To see who has rights to approve, go to the main :menuselection:`Settings` app and click on :guilabel:`Manage Users`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:314 +msgid "If the *Settings* app is not available, then certain rights are not set on the account. In the :guilabel:`Access Rights` tab of a user's card in the :menuselection:`Settings` app, the :guilabel:`Administration` section is set to one of three options:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:318 +msgid ":guilabel:`None (blank)`: The user cannot access the *Settings* app at all." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:319 +msgid ":guilabel:`Access Rights`: The user can only view the :guilabel:`User's & Companies` section of the *Settings* app." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:321 +msgid ":guilabel:`Settings`: The user has access to the entire *Settings* app with no restrictions." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:323 +msgid "Please refer to :doc:`this document ` to learn more about managing users and their access rights." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:326 +msgid "Click on an individual to view their card, which displays the :guilabel:`Access Rights` tab in the default view. Scroll down to the :guilabel:`Human Resources` section. Under :guilabel:`Expenses`, there are four options:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:330 +msgid ":guilabel:`None (blank)`: A blank field means the user has no rights to view or approve expense reports, and can only view their own." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:332 +msgid ":guilabel:`Team Approver`: The user can only view and approve expense reports for their own specific team." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:334 +msgid ":guilabel:`All Approver`: The user can view and approve any expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:335 +msgid ":guilabel:`Administrator`: The user can view and approve any expense report as well as access the reporting and configuration menus in the *Expenses* app." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:338 +msgid "Users who are able to approve expense reports (typically managers) can easily view all expense reports to validate. Go to :menuselection:`Expenses app --> Expense Reports --> Reports to Approve`. This view lists all the expense reports that have been submitted but not approved, as noted by the :guilabel:`Submitted` tag in the status column." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Reports to validate are found on the Reports to Approve page." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:347 +msgid "Reports can be approved in two ways (individually or several at once) and refused only one way. To approve multiple expense reports at once, remain in the list view. First, select the reports to approve by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click :guilabel:`Approve Report`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Approve multiple reports by clicking the checkboxes next to each report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:357 +msgid "To approve an individual report, click on a report to go to a detailed view of that report. In this view, several options are presented: :guilabel:`Approve`, :guilabel:`Refuse`, or :guilabel:`Reset to draft`. Click :guilabel:`Approve` to approve the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:361 +msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to refuse Expense` field, then click :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses.rst:0 +msgid "Send messages in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:368 +msgid "Team managers can easily view all the expense reports for their team members. While in the :guilabel:`Reports to Approve` view, click on :guilabel:`Filters`, then click :guilabel:`My Team`. This presents all the reports for the manager's team." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Select the My Team filter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:377 +msgid "If more information is needed, such as a receipt is missing, communication is easy from the chatter. In an individual report, simply type in a message, tagging the proper person (if needed), and post it to the chatter by clicking :guilabel:`Send`. The message is posted in the chatter, and the person tagged will be notified via email of the message, as well as anyone following." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:390 +msgid "Post expenses in accounting" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:392 +msgid "Once an expense report is approved, the next step is to post the report to the accounting journal. To view all expense reports to post, go to :menuselection:`Expenses --> Expense Reports --> Reports To Post`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "View reports to post by clicking on expense reports, then reports to post." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:400 +msgid "Just like approvals, expense reports can be posted in two ways (individually or several at once). To post multiple expense reports at once, remain in the list view. First, select the reports to post by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click :guilabel:`Post Entries`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Post multiple reports from the Post Entries view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:410 +msgid "To post an individual report, click on a report to go to the detailed view of that report. In this view, several options are presented: :guilabel:`Post Journal Entries`, :guilabel:`Report In Next Payslip`, or :guilabel:`Refuse`. Click :guilabel:`Post Journal Entries` to post the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:414 +msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to refuse Expense` field, then click :guilabel:`Refuse`. Refused reports can be viewed by going to :menuselection:`Expenses app --> Expense Reports --> All Reports`. This list shows all reports, including the refused ones." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:420 +msgid "To post expense reports to an accounting journal, the user must have following access rights:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:422 +msgid "Accounting: Accountant or Adviser" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:423 +msgid "Expenses: Manager" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:428 +msgid "Reimburse employees" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:430 +msgid "After an expense report is posted to an accounting journal, the next step is to reimburse the employee. To view all expense reports to pay, go to :menuselection:`Expenses --> Expense Reports --> Reports To Pay`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "View reports to pay by clicking on expense reports, then reports to pay." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:438 +msgid "Just like approvals and posting, expense reports can be paid in two ways (individually or several at once). To pay multiple expense reports at once, remain in the list view. First, select the reports to pay by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click :guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Post multiple reports by clicking the checkboxes, clicking the gear, then post the entries." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:448 +msgid "To pay an individual report, click on a report to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:452 +msgid "Re-invoice expenses to customers" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:454 +msgid "If expenses are tracked on customer projects, expenses can be automatically charged back to the customer. This is done by creating an expense report, then creating a sales order with the expensed items on it. Then, managers approve the expense report, and the accounting department posts the journal entries. Finally, the customer is invoiced." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:462 +msgid "First, specify the invoicing policy for each expense product. Go to :menuselection:`Expenses app --> Configuration --> Expense Products`. Click on the expense product to edit, then click :guilabel:`Edit`. Under the :guilabel:`Invoicing` section, select the :guilabel:`Invoicing Policy` and :guilabel:`Re-Invoicing Policy` by clicking the radio button next to the desired selection." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:467 +msgid ":guilabel:`Invoicing Policy`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:469 +msgid ":guilabel:`Ordered quantities`: Expense product will only invoice expenses based on the ordered quantity." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:471 +msgid ":guilabel:`Delivered quantities`: Expense product will only invoice expenses based on the delivered quantity." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:474 +msgid ":guilabel:`Re-Invoicing Policy`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:476 +msgid ":guilabel:`No`: Expense product will not be re-invoiced." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:477 +msgid ":guilabel:`At cost`: Expense product will invoice expenses at their real cost." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:478 +msgid ":guilabel:`At sales price`: Expense product will invoice the price set on the sale order." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:481 +msgid "Create an expense" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:483 +msgid "First, when :ref:`creating a new expense `, the correct information needs to be entered in order to re-invoice a customer. Select the :guilabel:`Customer to Reinvoice` from the drop-down menu. Next, select the :guilabel:`Analytic Account` the expense will be posted to." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Ensure the customer to be invoiced is called out on the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:492 +msgid "Create a quote and sales order" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:494 +msgid "In the :menuselection:`Sales` app, create a quote for the customer being invoiced, listing the expense products. First, click :guilabel:`Create` to create a new quotation. Next, select the :guilabel:`Customer` being invoiced for the expenses from the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:498 +msgid "In the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`. In the :guilabel:`Product` field, select the first item being invoiced from the drop-down menu, or type in the product name. Then, update the :guilabel:`Quantity`, the :guilabel:`Delivered` quantity, and the :guilabel:`Unit Price` if needed. Repeat this for all products being invoiced. When all the products have been added to the quote, click :guilabel:`Confirm` and the quotation becomes a sales order." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Create and confirm the sales order with the expenses listed as products." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:508 +msgid "Once the quote turns into a sales order, a :guilabel:`Delivered` column appears. The delivered quantity must be updated for each item. Click on the `0.000` field for each product, and enter the delivered quantity. When all delivered quantities have been entered, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:513 +msgid "Validate and post expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:515 +msgid "Only employees with permissions (typically managers or supervisors) can :ref:`approve expenses `. Before approving an expense report, ensure the :guilabel:`Analytic Account` is set on every expense line of a report. If an :guilabel:`Analytic Account` is missing, click :guilabel:`Edit` and select the correct account from the drop-down menu, then click :guilabel:`Approve` or :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:521 +msgid "The accounting department is typically responsible for :ref:`posting journal entries `. Once an expense report is approved, it can then be posted." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:525 +msgid "Invoice expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:527 +msgid "Once the quote has turned into a sales order, and the expense report has been approved, it is time to invoice the customer. Go to :menuselection:`Sales app --> To Invoice --> Orders to Invoice` to view the sales orders ready to be invoiced." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:531 +msgid "Next, find the sales order related to the expense report, click into it, and then click :guilabel:`Create Invoice` and a :guilabel:`Create invoices` pop-up window appears. Select if the invoice is a :guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)`, or :guilabel:`Down payment (fixed amount)` by clicking the radio button next to the selection. For either down payment options, enter the amount (fixed or percentage) in the :guilabel:`Down Payment Amount` field. Finally, click either :guilabel:`create and view invoice` or :guilabel:`create invoice`." msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:5 @@ -9535,7 +9888,7 @@ msgstr "" msgid "To install a new package, go to :menuselection:`Accounting --> Configuration --> Fiscal Localization`, click on **Install More Packages**, and install your country's module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations.rst:None +#: ../../content/applications/finance/fiscal_localizations.rst:-1 msgid "Install the appropriate module as fiscal localization package in Odoo Accounting." msgstr "" @@ -9543,7 +9896,7 @@ msgstr "" msgid "Once done, select your country's package, and click on *Save*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations.rst:None +#: ../../content/applications/finance/fiscal_localizations.rst:-1 msgid "Select your country's fiscal localization package in Odoo Accounting." msgstr "" @@ -9588,7 +9941,7 @@ msgid "Austria - Accounting" msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:65 -msgid "Belgium - Accounting" +msgid ":doc:`Belgium - Accounting `" msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:66 @@ -10598,99 +10951,329 @@ msgid "Australia" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:8 -msgid "KeyPay Australian Payroll" +msgid "Employment Hero Australian Payroll" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:10 -msgid "The KeyPay Module synchronizes payslip accounting entries (e.g., expenses, social charges, liabilities, taxes) from KeyPay to Odoo automatically. Payroll administration is still done in KeyPay. We only record the journal entries in Odoo." +msgid "The Employment Hero module synchronizes payslip accounting entries (e.g., expenses, social charges, liabilities, taxes) from Employment Hero to Odoo automatically. Payroll administration is still done in Employment Hero. We only record the journal entries in Odoo." msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:15 -msgid "Configuration Steps" +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:17 -msgid "Create a company located in Australia." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:20 +msgid ":ref:`Activate ` the :guilabel:`Employment Hero Australian Payroll` module (technical name: `l10n_au_keypay`)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:18 -msgid "Check that the Australian localization module (Australia - Accounting) is installed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/australia.rst:19 -msgid "Configure the *KeyPay API*." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:22 +msgid "Configure the **Employment Hero API** by going to :menuselection:`Accounting --> Configuration --> Settings`. More fields become visible after clicking on :guilabel:`Enable Employment Hero Integration`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:0 -msgid "Odoo Accounting settings includes a section for the Australian Loclization" +msgid "Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:25 -msgid "More fields become visible after clicking on *Enable KeyPay Integration*." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:30 +msgid "You can find the API Key in the :guilabel:`My Account` section of the Employment Hero platform." msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:0 -msgid "Enabling KeyPay Integration in Odoo Accounting displays new fields in the settings" +msgid "\"Account Details\" section on the Employment Hero dashboard" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:31 -msgid "You can find the API Key in the *My Account* section of the KeyPay platform." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 -msgid "\"Account Details\" section on the KeyPay dashboard" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:35 +msgid "The **Payroll URL** is pre-filled with `https://keypay.yourpayroll.com.au`. *Please do not change it.*" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:37 -msgid "The **Payroll URL** is pre-filled with ``https://keypay.yourpayroll.com.au``. *Please do not change it.*" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/australia.rst:39 -msgid "You can find the **Business ID** in the KeyPay URL. (i.e., ``189241``)" +msgid "You can find the **Business ID** in the Employment Hero URL. (i.e., `189241`)" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:0 -msgid "The KeyPay \"Business ID\" number is in the URL" +msgid "The Employment Hero \"Business ID\" number is in the URL" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:45 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:42 msgid "You can choose any Odoo journal to post the payslip entries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:48 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:45 msgid "How does the API work?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:50 -msgid "The API syncs the journal entries from KeyPay to Odoo and leaves them in draft mode. The reference includes the KeyPay payslip entry ID in brackets for the user to easily retrieve the same record in KeyPay and Odoo." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:47 +msgid "The API syncs the journal entries from Employment Hero to Odoo and leaves them in draft mode. The reference includes the Employment Hero payslip entry ID in brackets for the user to easily retrieve the same record in Employment Hero and Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:None -msgid "Example of a KeyPay Journal Entry in Odoo Accounting (Australia)" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:59 -msgid "The API sync is triggered by scheduled actions." +#: ../../content/applications/finance/fiscal_localizations/australia.rst:54 +msgid "By default, the synchronization happens once per week. You can fetch the records manually by going to :menuselection:`Accounting --> Configuration --> Settings` and, in the :guilabel:`Enable Employment Hero Integration` option, click on :guilabel:`Fetch Payruns Manually`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 -msgid "Scheduled Actions settings for KeyPay Payroll in Odoo (debug mode)" +#: ../../content/applications/finance/fiscal_localizations/australia.rst:58 +msgid "Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:60 +msgid "The accounts used by Employment Hero are defined in the section :guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:65 -msgid "KeyPay payslip entries also work based on double-entry bookkeeping. Debit must equal credit (like in Odoo)." +msgid "For the API to work, you need to create the same accounts as the default accounts of your Employment Hero business (**same name and same code**) in Odoo. You also need to choose the correct account types in Odoo to generate accurate financial reports." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:68 -msgid "The accounts used by KeyPay are defined in the section **Payroll settings**." +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:3 +msgid "Belgium" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:None -msgid "Chart of Accounts menu in KeyPay" +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 +msgid "Fiscal certification: POS restaurant" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:74 -msgid "For the API to work, you need to create the same accounts as the default accounts of your KeyPay business (**same name and same code**) in Odoo. You also need to choose the correct account types in Odoo to generate accurate financial reports." +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:10 +msgid "In Belgium, the owner of a cooking business such as a restaurant or food truck is required by law to use a government-certified **Cash Register System** for their receipts. This applies if their yearly earnings (excluding VAT, drinks, and take-away food) exceed 25,000 euros." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:14 +msgid "This government-certified system entails the use of a :ref:`certified POS system `, along with a device called a :ref:`Fiscal Data Module ` (or **black box**) and a :ref:`VAT Signing Card `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:19 +msgid "Do not forget to register as *foodservice industry manager* on the `Federal Public Service Finance registration form `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:25 +msgid "Certified POS system" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:27 +msgid "The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online** and **Odoo.sh**. Please refer to the following table to ensure that your POS system is certified." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:35 +msgid "Odoo Online" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:36 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:37 +msgid "On-Premise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:38 +msgid "Odoo 16.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:40 +msgid "Review in progress" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:41 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:43 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:44 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:45 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:49 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:53 +msgid "Not certified" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:42 +msgid "Odoo 15.2" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:46 +msgid "Odoo 15.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:47 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:51 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:52 +msgid "Certified" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 +msgid "Odoo 14.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:56 +msgid ":doc:`/administration/maintain/supported_versions`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:58 +msgid "A `certified POS system `_ must adhere to rigorous government regulations, which means it operates differently from a non-certified POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:62 +msgid "On a certified POS, you cannot:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:64 +msgid "Make a refund." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:65 +msgid "Set up and use the **global discounts** feature (the `pos_discount` module is blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:67 +msgid "Set up and use the **loyalty programs** feature (the `pos_loyalty` module is blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:69 +msgid "Reprint receipts (the `pos_reprint` module is blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:70 +msgid "Modify prices in order lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:71 +msgid "Modify or delete order lines in POS orders." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:72 +msgid "Sell products without a valid VAT number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:73 +msgid "Use a POS that is not connected to an IoT box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:75 +msgid "The :doc:`cash rounding <../../sales/point_of_sale/pricing/cash_rounding>` feature must be activated and set to a :guilabel:`Rounding Precision` of `0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:78 +msgid "Taxes must be set as included in the price. To set it up, go to :menuselection:`Point of Sale --> Configuration --> Settings`, and from the :guilabel:`Taxes` section, open the :guilabel:`Default Sales Tax` form by clicking the arrow next to the default sales tax field. There, click :guilabel:`Advanced Options` and enable :guilabel:`Included in Price`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:82 +msgid "At the start of a POS session, users must click :guilabel:`Work in` to clock in. Doing so allows the registration of POS orders. If users are not clocked in, they cannot make POS orders. Likewise, they must click :guilabel:`Work Out` to clock out at the end of the session." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:87 +msgid "If you configure a POS to work with a black box, you cannot use it again without it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:92 +msgid "The Fiscal Data Module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:94 +msgid "The :abbr:`FDM (Fiscal Data Module)`, or `black box `_, is a government-certified device that works together with the Point of Sale application and saves your POS orders information. Concretely, a **hash** (:dfn:`unique code`) is generated for each POS order and added to its receipt. This allows the government to verify that all revenue is declared." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:100 +msgid "Ensure your black box is approved by the Belgian government. You can check the compliance of your black box by visiting the `Federal Public Service Finance `_ website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:107 +msgid "Before setting up your database to work with an FDM, ensure you have the following hardware:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:109 +msgid "a registered :ref:`black box ` (go to `www.boîtenoire.be `_ to order yours);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:111 +msgid "an RS-232 serial null modem cable per FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:112 +msgid "an RS-232 serial-to-USB adapter per FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:113 +msgid "an :ref:`IoT Box ` (one IoT box per black box); and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:114 +msgid "a receipt printer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:119 +msgid "Black box module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:121 +msgid "As a pre-requisite, :ref:`activate ` the `Belgian Registered Cash Register` module (technical name: `pos_blackbox_be`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "black box modules for belgian fiscal certification" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:127 +msgid "Once the module is activated, add your VAT number to your company information. To set it up, go to :menuselection:`Settings --> Companies --> Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national registration number for every staff member who operates the POS system. To do so, go to the :guilabel:`Employees` app and open an employee form. There, go to :menuselection:`HR settings tab --> Attendance`, and fill in the :guilabel:`INSZ or BIS number` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "ISNZ or BIS number field on employee form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:137 +msgid "To input your information, click on your avatar, go to :menuselection:`My Profile --> Preference tab`, and enter your INSZ or BIS number in the designated field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:141 +msgid "You must configure the black box directly in the production database. Utilizing it in a testing environment may result in incorrect data being stored within the black box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:147 +msgid "IoT Box" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:149 +msgid "In order to use a Fiscal Data Module, you need a registered IoT Box. To register your IoT box, you must contact us through our `support contact form `_ and provide the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:153 +msgid "your VAT number;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:154 +msgid "your company's name, address, and legal structure; and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:155 +msgid "the Mac address of your IoT Box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:157 +msgid "Once your IoT box is certified, :doc:`connect <../../productivity/iot/config/connect>` it to your database. To verify that the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the :guilabel:`IOT Device` section, which should display the FDM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "Hardware status page on a registered IoT Box" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:164 +msgid "Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select your POS, scroll down to the :guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:169 +msgid "To be able to use an FDM, you must at least connect one :guilabel:`Receipt Printer`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:174 +msgid "VAT signing card" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:176 +msgid "When you open a POS session and make your initial transaction, you are prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`. The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` upon `registration `_." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:3 @@ -10729,7 +11312,7 @@ msgstr "" msgid "For this, go to *Apps* and search for Chile. Then click *Install* in the module **Chile E-invoicing**. This module has a dependency with **Chile - Accounting**. In case this last one is not installed, Odoo installs it automatically with E-invoicing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean module to install on Odoo." msgstr "" @@ -10757,7 +11340,7 @@ msgstr "" msgid "Fill in the fiscal information for your company according to the SII register, follow the instructions on each section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean company fiscal data." msgstr "" @@ -10770,7 +11353,7 @@ msgstr "" msgid "This is part of the main information required to generate electronic Invoice, select your environment and the legal information, as well as the email address to receive invoices from your vendors and the alias you use to send invoices to your customers." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean edi environment settings." msgstr "" @@ -10782,7 +11365,7 @@ msgstr "" msgid "In order to receive you the claim and acceptance emails from your customers, it is crucial to define the DTE incoming email server, considering this configuration:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Incoming email server configuration for Chilean DTE." msgstr "" @@ -10799,11 +11382,11 @@ msgstr "" msgid "In order to generate the electronic invoice signature, a digital certificate with the extension ``pfx`` is required, proceed to this section and load your file and password." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Digital certificate access." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Digital certificate configuration." msgstr "" @@ -10816,7 +11399,7 @@ msgid "In some cases, depending on the certificate format, it is possible that t msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:124 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:871 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:874 msgid "Financial Reports" msgstr "" @@ -10824,7 +11407,7 @@ msgstr "" msgid "The report Propuesta F29 requires two values that need to be defined as part of the company configuration:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Fiscal reports parameters." msgstr "" @@ -10832,7 +11415,7 @@ msgstr "" msgid "The official currency rate in Chile is provided by the Chilean service `mindicador.cl `_. You can find this service in the currency rate configuration, and you can set a predefined interval for the rate updates." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Currency reate service for Chile." msgstr "" @@ -10865,7 +11448,7 @@ msgstr "" msgid "As part of the Chilean localization, the identification types defined by the SII are now available on the Partner form. This information is essential for most transactions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean identification types for partners." msgstr "" @@ -10877,7 +11460,7 @@ msgstr "" msgid "In Chile, the document type associated with customers and vendors transactions is defined based on the Taxpayer Type. This field should be defined in the partner form, when creating a customer is important you make sure this value is set:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean taxpayer types for partners." msgstr "" @@ -10885,7 +11468,7 @@ msgstr "" msgid "As part of the information that is sent in the electronic Invoice, you need to define the email that is going to appear as the sender of the electronic invoice to your customer, and the Industry description." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean electronic invoice data for partners." msgstr "" @@ -10893,7 +11476,7 @@ msgstr "" msgid "As part of the localization module, the taxes are created automatically with their related financial account and configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean taxes list." msgstr "" @@ -10930,7 +11513,7 @@ msgstr "" msgid "Each document type can have a unique sequence per company. As part of the localization, the Document Type includes the country on which the document is applicable and the data is created automatically when the localization module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean fiscal document types list." msgstr "" @@ -11002,7 +11585,7 @@ msgstr "" msgid "**Use Documents**: This field is used to define if the journal will use Document Types. It is only applicable to Purchase and Sales journals that can be related to the different sets of document types available in Chile. By default, all the sales journals created will use documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Document type configuration on Journal." msgstr "" @@ -11046,7 +11629,7 @@ msgstr "" msgid "Save the CAF." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Steps to add a new CAF." msgstr "" @@ -11070,7 +11653,7 @@ msgstr "" msgid "In the Chilean localization the electronic Invoice workflow covers the Emission of Customer Invoices and the reception of Vendor Bills, in the next diagram we explain how the information transmitted to the SII and between the customers and Vendors." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Diagram with Electronic invoice transactions." msgstr "" @@ -11086,7 +11669,7 @@ msgstr "" msgid "You can manually change the document type if needed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Document type selection on invoices." msgstr "" @@ -11095,7 +11678,7 @@ msgid "Documents type 33: Electronic Invoice must have at least one item with ta msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:389 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:813 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 msgid "Validation and DTE Status" msgstr "" @@ -11108,8 +11691,8 @@ msgid "The DTE File (Electronic Tax Document) is created automatically and added msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:395 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:759 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:823 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:762 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 msgid "The DTE SII status is set as: Pending to be sent." msgstr "" @@ -11121,7 +11704,7 @@ msgstr "" msgid "The DTE Status is updated automatically by Odoo with a scheduled action that runs every day at night, if you need to get the response from the SII immediately you can do it manually as well. The DTE status workflow is as follows:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Transition of DTE statuses." msgstr "" @@ -11193,7 +11776,7 @@ msgstr "" msgid "When the Invoice is created as a result of another fiscal document, the information related to the originator document must be registered in the Tab Cross Reference, which is commonly used for credit or debit notes, but in some cases can be used on Customer Invoices as well. In the case of the credit and debit notes, they are set automatically by Odoo:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Invoice tab with origin document number and data." msgstr "" @@ -11206,7 +11789,7 @@ msgstr "" msgid "Once the invoice is accepted and validated by the SII and the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally valid:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Barcode and fiscal elements in the invoice report." msgstr "" @@ -11238,7 +11821,7 @@ msgstr "" msgid "The field DTE acceptation status is updated automatically." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Message with the commercial acceptance from the customer." msgstr "" @@ -11250,7 +11833,7 @@ msgstr "" msgid "Once the invoice has been Accepted by the SII **it can not be cancelled in Odoo**. In case you get a Claim for your customer the correct way to proceed is with a Credit Note to either cancel the Invoice or correct it. Please refer to the :ref:`chile/credit-notes` section for more details." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Invoice Comercial status updated to Claimed." msgstr "" @@ -11317,7 +11900,7 @@ msgstr "" msgid "When a cancellation or correction is needed over a validated invoice, a credit note must be generated. It is important to consider that a CAF file is required for the Credit Note, which is identified as document 64 in the SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Creation of CAF for Credit notes." msgstr "" @@ -11338,7 +11921,7 @@ msgstr "" msgid "In case you need to cancel or invalid an Invoice, use the button Add Credit note and select Full Refund, in this case the SII reference Code is automatically set to: Anula Documento de referencia." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Full invoice refund with SII reference code 1." msgstr "" @@ -11350,7 +11933,7 @@ msgstr "" msgid "If a correction in the invoice information is required, for example the Street Name, use the button Add Credit note,select Partial Refund and select the option “Solo corregir Texto”. In this case the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Partial refund to correct text including the corrected value." msgstr "" @@ -11358,7 +11941,7 @@ msgstr "" msgid "Odoo creates a Credit Note with the corrected text in an invoice and price 0." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Credit note with the corrected value on the invoice lines." msgstr "" @@ -11374,7 +11957,7 @@ msgstr "" msgid "When a correction on the amounts is required, use the button Add Credit note and select Partial Refund. In this case the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Credit note for partial refund to correct amounts, using the SII reference code 3." msgstr "" @@ -11395,7 +11978,7 @@ msgstr "" msgid "The most common use case for debit notes is to increase the value of an existing invoice, you need to select option 3 in the field Reference code SII:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Debit note for partial refund to crrect amounts, using the SII reference code 3." msgstr "" @@ -11403,7 +11986,7 @@ msgstr "" msgid "In this case Odoo automatically includes the source invoice in the cross reference section:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Invoice data on crossed reference section for debit notes." msgstr "" @@ -11415,7 +11998,7 @@ msgstr "" msgid "In Chile the debits notes are used to cancel a validated Credit Note, in this case just select the button Add debit note and select the first option in the wizard: *1: Anula Documentos de referencia.*" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Creating a debit note to cancel a credit note with the SII code reference 1." msgstr "" @@ -11443,7 +12026,7 @@ msgstr "" msgid "As soon as the vendor email with the attached DTE is received: 1. The vendor Bill mapping all the information included in the xml. 2. An email is sent to the vendor with the Reception acknowledgement. 3. The DTE status is set as: Acuse de Recibido Enviado" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Messages recorded in the chatter with the reception notification for the vendor." msgstr "" @@ -11455,7 +12038,7 @@ msgstr "" msgid "If all the commercial information is correct on your vendor bill then you can accept the document using the :guilabel:`Aceptar Documento` button. Once this is done the DTE Acceptation Status changes to :guilabel:`Accepted`` and an email of acceptance is sent to the vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Acceptance button in vendor bills to inform vendor the document is comercially accepted." msgstr "" @@ -11467,7 +12050,7 @@ msgstr "" msgid "In case there is a commercial issue or the information is not correct on your vendor bill, you can Claim the document before validating it, using the button: Claim, once this is done the DTE Acceptation Status change to: Claim and an email of acceptance is sent to the vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Claim button in vendor bills to inform the vendor all the document is comercially rejected." msgstr "" @@ -11491,7 +12074,7 @@ msgstr "" msgid "The Delivery Guide module includes sending the DTE to SII and the stamp in PDF reports for deliveries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Install Delivery Guide Module" msgstr "" @@ -11523,173 +12106,177 @@ msgstr "" msgid "Delivery Guide from a Sales Process" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:737 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:738 +msgid "A delivery guide should **not** be longer than one page or contain more than 60 product lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:740 msgid "When a Sales Order is created and confirmed, a Delivery Order is generated. After validating the Delivery Order, the option to create a Delivery Guide is activated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Create Delivery Guide Button" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:744 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:747 msgid "When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up, showing the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "An example sequence error when creating a Delivery Guide in Odoo" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:754 msgid "This warning message means the user needs to indicate the next sequence number Odoo has to take to generate the Delivery Guide, and only only happens the *first time* a Delivery Guide is created in Odoo. After the first document has been correctly generated, Odoo takes the CAFs next available number to generate the following Delivery Guide and so on." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:756 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:759 msgid "After the Delivery Guide is created:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:758 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:761 msgid "The DTE file (Electronic Tax Document) is automatically created and added to the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "DTE Status in SII and creation of DTE/XML" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:765 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:829 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:768 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:832 msgid "The DTE Status is automatically updated by Odoo with a scheduled action that runs every day at night. To get a response from the SII immediately, press the :guilabel:`Send now to SII` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:768 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:771 msgid "Once the Delivery Guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Printing Delivery Guide PDF" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:776 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 msgid "Electronic Receipt" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:778 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 msgid "To install the Electronic Receipt module, go to :menuselection:`Apps` and search for :guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:783 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 msgid "*Chile - Electronic Receipt* has a dependency with *Chile - Facturación Electrónica*. Odoo will install the dependency automatically when the E-invoicing Delivery Guide module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:789 msgid "This module contains the electronic receipt and daily sales report, which are automatically sent to SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Install Electronic Receipt module" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:793 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:796 msgid "Once all configurations have been made for Electronic Invoices (e.g., uploading a valid company certificate, setting up master data, etc.), Electronic Receipts need their own CAFs. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the CAFs for Electronic Receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:798 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:801 msgid "Electronic Receipts are useful when clients do not need an Electronic Invoice. By default, there is a partner in the database called *Anonymous Final Consumer* with a generic RUT 66666666-6 and taxpayer type of *Final Consumer*. This partner can be used for Electronic Receipts or a new record may be created for the same purpose." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:803 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:806 msgid "Although Electronic Receipts should be used for final consumers with a generic RUT, it can also be used for specific partners. After the partners and journals are created and configured, the Electronic Receipts are created in the standard way as Electronic Invoice, but the type of document :guilabel:`(39) Electronic Receipt` should be selected, like so:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Select type of Document: (39) Boleta Electrónica" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:815 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:818 msgid "When all of the Electronic Receipt information is filled, either manually or automatically from a Sales Order, proceed to validate the receipt. By default, Electronic Invoice is selected as the Document Type, however in order to validate the receipt correctly, make sure to edit the Document Type and change to Electronic Receipt." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:820 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:823 msgid "After the receipt is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:822 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:825 msgid "The DTE file (Electronic Tax Document) is created automatically and added to the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "DTE status in SII and creation of DTE/XML" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:832 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:835 msgid "Please refer to the :ref:`DTE Workflow ` for Electronic Invoices as the workflow for Electronic Receipt follows the same process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:836 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:839 msgid "Daily Sales Report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:838 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:841 msgid "Once Electronic Receipts have been created, the system creates a daily sales report containing all Electronic Receipts per day. This report is electronically stamped and sent to the SII overnight in XML format. These daily reports can be found in :menuselection:`Reports --> Daily Sales Reports`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Find Electronic Receipts in the Reports menu, under Daily Sales Reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:846 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:849 msgid "A list of daily reports is displayed with all daily DTE sent to SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "List of Daily Reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:852 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:855 msgid "If no Electronic Receipt was made on a particular day, the report is sent but it will not have any receipts in it. The report will also have an answer from the SII if it was accepted or rejected (depending on the company's certificate and validated receipts)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Daily Sales Book example" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:861 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:864 msgid "For Chilean localization, note that the feature tax included in the price is *not* supported for the Electronic Receipt." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:864 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:867 msgid "If a Daily Sales Report has already been created for a specific day in another system, the daily report in Odoo will be rejected due to the sequence number used. If that is the case, the user has to manually click on :guilabel:`Retry` in order for a new sequence number to be generated (this action is automatically done by Odoo). Afterwards, users can manually verify report status with SII or wait for Odoo to update status later at night." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:874 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:877 msgid "Balance Tributario de 8 Columnas" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:876 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:879 msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time, so that a real and complete knowledge of the status of a company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:880 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:883 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:899 msgid "You can find this report in :menuselection:`Accounting --> Accounting --> Reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Columns and data displayed in the report Balance Tributario 8 Columnas." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:887 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:890 msgid "Propuesta F29" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:889 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:892 msgid "The form F29 is a new system that the SII enabled to taxpayers, and that replaces the Purchase and Sales Books. This report is integrated by Purchase Register (CR) and the Sales Register (RV). Its purpose is to support the transactions related to VAT, improving its control and declaration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:893 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:None +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Parameters to required to generate the Report Propuesta F29" msgstr "" @@ -12925,7 +13512,7 @@ msgstr "" msgid "If these modules are not listed, :ref:`update the app list `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/germany.rst:None +#: ../../content/applications/finance/fiscal_localizations/germany.rst:-1 msgid "Upgrading Odoo Point of Sale from the Apps dashboard" msgstr "" @@ -12961,7 +13548,7 @@ msgstr "" msgid "You can then **register your company through fiskaly** by opening the *fiskaly* tab and clicking on the *fiskaly Registration* button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/germany.rst:None +#: ../../content/applications/finance/fiscal_localizations/germany.rst:-1 msgid "Button to register a company through fiskaly in Odoo" msgstr "" @@ -12981,7 +13568,7 @@ msgstr "" msgid "**fiskaly API key** and **secret** are the credentials the system uses to access the services offered by fiskaly." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/germany.rst:None +#: ../../content/applications/finance/fiscal_localizations/germany.rst:-1 msgid "fiskaly keys as displayed on Odoo" msgstr "" @@ -12993,7 +13580,7 @@ msgstr "" msgid "Create and link a Technical Security System to your PoS" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/germany.rst:None +#: ../../content/applications/finance/fiscal_localizations/germany.rst:-1 msgid "Create TSS option from a point of sale" msgstr "" @@ -13005,7 +13592,7 @@ msgstr "" msgid "To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the point of sale you want to edit, then check the box next to **Create TSS** and *Save*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/germany.rst:None +#: ../../content/applications/finance/fiscal_localizations/germany.rst:-1 msgid "Example of TSS ID and Client ID from fiskaly in Odoo Point of Sale" msgstr "" @@ -13025,7 +13612,7 @@ msgstr "" msgid "DSFinV-K" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/germany.rst:None +#: ../../content/applications/finance/fiscal_localizations/germany.rst:-1 msgid "Menu to export DSFinV-K" msgstr "" @@ -13061,7 +13648,7 @@ msgstr "" msgid "The creation of a DSFinV-K export triggers on export at fiskaly's side." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/germany.rst:None +#: ../../content/applications/finance/fiscal_localizations/germany.rst:-1 msgid "Pending DSFinV-K export on Odoo" msgstr "" @@ -13458,7 +14045,7 @@ msgstr "" msgid "Once the `l10_it_edi_sdicoop` module is installed, sending invoices via PEC mails is no longer possible." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:None +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 msgid "Italian localization modules" msgstr "" @@ -13490,7 +14077,7 @@ msgstr "" msgid ":guilabel:`PEC address email`: the certified email address of the company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:None +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 msgid "Company information to provide" msgstr "" @@ -13546,7 +14133,7 @@ msgstr "" msgid "You can check the current status of an invoice by the :guilabel:`Electronic invoicing` field. The XML file can be found in the **chatter** of the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:None +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 msgid "Electronic invoicing status (waiting for confirmation)" msgstr "" @@ -13602,12 +14189,12 @@ msgstr "" msgid "When in :guilabel:`Test (Experimental)` mode, all invoices sent *must* have a partner using one of the following fake :guilabel:`Codice Destinatario` given by the **Agenzia Delle Entrate**: `0803HR0` - `N8MIMM9` - `X9XX79Z`. Any real production :guilabel:`Codice Destinario` of your customers will not be recognized as valid by the test service." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:None +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 msgid "Italy's electronic document invoicing options" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:150 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Taxes configuration" msgstr "" @@ -13631,7 +14218,7 @@ msgstr "" msgid "To make an export invoice, make sure that the invoice lines all use a tax configured for **reverse charge**. The **Italian** localization contains an **example** of a reverse charge tax for export in the EU to be used as reference (`0% EU`, invoice label `00eu`), which can be found under :menuselection:`Accounting --> Configuration --> Taxes`. Exports are exempt from VAT, and therefore **reverse charge** taxes require the :guilabel:`Has exoneration of tax (Italy)` option ticked, with both the :guilabel:`Exoneration` kind and :guilabel:`Law Reference` filled in." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:None +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 msgid "External reverse charge settings" msgstr "" @@ -13949,7 +14536,7 @@ msgstr "" msgid "The Italian localization has a specific **tax grid** section for **reverse charge** taxes. These tax grids are identifiable by the :ref:`VJ ` tag, and can be found under :menuselection:`Accounting --> Reporting --> Audit Reports: Tax Report`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:None +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 msgid "Italian reverse charge tax grids" msgstr "" @@ -14093,7 +14680,7 @@ msgstr "" msgid "The **simplified annual declaration** is automatically generated. You can manually add values in all the fields to get a **complete annual declaration**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:None +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:-1 msgid "Odoo Accounting (Luxembourg localization) generates an annual tax declaration." msgstr "" @@ -14101,7 +14688,7 @@ msgstr "" msgid "To help you complete it, you can use the information provided on the :guilabel:`Tax Report`. To do so, go to :menuselection:`Accounting --> Report --> Audit Reports --> Tax Report`, then click on the :guilabel:`Tax Report` dropdown menu and select the type of report you want to display." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:None +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:-1 msgid "Dropdown menu to select the type of Tax Report" msgstr "" @@ -14166,7 +14753,7 @@ msgid "Have a `Certificate of Digital Seal `_, `Quadrum (formerly Finkok) `_ and `SW Sapien - Smarter Web `_." +msgid "Choose a PAC and purchase stamps. Currently the Mexican location in Odoo works with the following PACs: `Solución Factible `_, `Quadrum (formerly Finkok) `_ and `SW Sapien - Smarter Web `_." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:37 @@ -14181,7 +14768,7 @@ msgstr "" msgid "To install the Mexican localization module, go to :menuselection:`Apps`, then remove the default filter \"Apps\" and search for ``l10n_mx``." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Installation of the Mexican localization module in Odoo Apps" msgstr "" @@ -14245,7 +14832,7 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Accounting --> Customer Invoices`, and make sure that the option **Mexican Electronic Invoicing** is enabled. With this you will be able to generate the signed invoice and also generate the signed payment complement, all automatically integrated into the normal billing flow in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Steps to enable electronic invoicing" msgstr "" @@ -14257,7 +14844,7 @@ msgstr "" msgid "After verifying the general configuration, you must verify that the company is configured with the correct data. To do so, go to :menuselection:`Settings --> General Settings --> Companies`, and click on *Update information* under your company name." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Update the company's details in the Settings of Odoo" msgstr "" @@ -14293,7 +14880,7 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) --> Fiscal Regime`, and select the option that applies to your company from the drop-down list." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Set the Fiscal Regime in Odoo Accounting" msgstr "" @@ -14309,7 +14896,7 @@ msgstr "" msgid "When creating a contact to be invoiced in Odoo, the following information must be configured for invoice validation: **complete address** (including postal code, city, state, country, etc.) and the **VAT** number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Contact form example" msgstr "" @@ -14334,210 +14921,210 @@ msgid "Do the same for all the sales taxes that the company needs, either those msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:177 -msgid "For the 0% VAT tax, select the option *Exento* instead of *Tasa* within the **Factor Type** field." +msgid "For the 0% VAT tax, select the option :guilabel:`Tasa` within the :guilabel:`Factor Type` field. For the 0% VAT **exempt** tax, select the option :guilabel:`Exento` instead of :guilabel:`Tasa` within the :guilabel:`Factor Type` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:180 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:181 msgid "When registering a payment, Odoo will carry out the movement of taxes from the **Cash Basis Transition Account** to the account set in the **Definition** tab. For such movement, a tax base account will be used (\"Base Imponible de Impuestos en Base a Flujo de Efectivo\" - **do not eliminate this account**) in the Journal Entry when reclassifying taxes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Taxes accounts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:190 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:191 msgid "Products Configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:192 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:193 msgid "All products to be sold need to have the SAT code associated with their classification so that the invoices do not give an error when validating." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:195 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:196 msgid "To configure products, go to the **General Information** tab and in the **UNSPSC Product Category** field select the category that represents that product. The process can be done manually or through a bulk import." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Configure products" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:204 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:205 msgid "PAC Configuration to sign invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:206 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:207 msgid "Another important step to configure electronic invoicing in Odoo is to enter the PAC which you are working with and the credentials. That way, electronic invoicing will be enabled." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:210 -msgid "Remember that you must register directly with the PAC of your choice before you start creating invoices from Odoo. We have the following PACs available: `Quadrum `_, `Solución Factible `_ and `SW Sapien - Smarter Web `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:211 +msgid "Remember that you must register directly with the PAC of your choice before you start creating invoices from Odoo. We have the following PACs available: `Quadrum `_, `Solución Factible `_ and `SW Sapien - Smarter Web `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:215 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:216 msgid "You must process your **Private Key (CSD)** with the SAT institution before following these steps. If you do not have this information, try with the Test Credentials and return to this process when you have the SAT Credentials for your production environment to work with real transactions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:220 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:221 msgid "To add the credentials, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the **PAC MX** section, enter the name of your PAC with your credentials (PAC username and PAC password)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PAC credentials" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:229 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:230 msgid "If you check the checkbox **Test Environment**, it is not necessary to enter a PAC username and/or password, but you must select a PAC from the drop-down list." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:232 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:233 msgid "Finally, upload the digital certificates of the company within the section **MX Certificates**. Click on *Add a line*, a window will open, click on *Create* and from there you can upload your digital certificate, your key and your password. To finish, click on *Save and Close*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Certificate and key" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:241 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:242 msgid "If you still do not have one of the contracted PACs and you want to test electronic invoicing you can use the following SAT test certificates:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:244 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:245 msgid ":download:`Certificate `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:245 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:246 msgid ":download:`Certificate Key `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:246 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:247 msgid "**Password:** ``12345678a``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:248 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:249 msgid "You must also configure the company with a real address within Mexico (including all fields) and add ``EKU9003173C9`` as the **VAT** number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:252 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:253 msgid "Workflows" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:255 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:256 msgid "Electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:257 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:258 msgid "The invoicing process in Odoo is based on `Annex 20 `_ version 3.3 of electronic invoicing of the SAT." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:261 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:262 msgid "To start invoicing from Odoo, an invoice must be created using the standard invoicing flow, that is, either from a sales order or from the invoice menu in the Accounting application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:264 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:265 msgid "The invoice will be stamped after clicking on *Validate*, before that the status is still in draft mode and changes can be made to it. After validating the invoice, you can verify that it was successfully stamped, as it would look like this:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Creating an invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:272 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:273 msgid "The details of the invoice will be reflected in the Chatter, which is what you see on the right of the invoice in the attached image. There you can find your XML sent to the SAT and the status of the stamping, that is, if it was validated or not." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:276 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:277 msgid "To send the stamped invoice to your client, you can send the XML together with the PDF file directly from Odoo, by clicking the *Send and Print* button. You can also download the PDF file directly to your computer by clicking the *Print* button and selecting the desired option." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:281 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:282 msgid "Depending on the size of the screen, the Chatter can be seen next to or below the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:284 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:285 msgid "Invoicing Special Cases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:287 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:288 msgid "Foreign Trade Invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:289 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:290 msgid "The foreign trade invoicing process in Odoo is based on the corresponding `SAT regulation `_. SAT electronic invoicing version is 3.3." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:294 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:295 msgid "What do we mean when we talk about foreign trade?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:296 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:297 msgid "Since January 2018, the SAT requires a Foreign Trade Supplement in export transactions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:299 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:300 msgid "What is the Foreign Trade complement?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:301 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:302 msgid "It is an Annex to the electronic invoice that allows the identification of exporters and importers, in addition to expanding the description of the merchandise sold." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:305 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:306 msgid "What information can be incorporated in this new complement?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:307 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:308 msgid "Information on the operation type it covers." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:308 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:309 msgid "Tax identification data of the issuer, receiver or recipient of the merchandise." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:309 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:310 msgid "Description of the goods to be exported." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:312 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:313 msgid "Who is obliged to generate it?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:314 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:315 msgid "Taxpayers who carry out export operations of A1 type." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:317 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:318 msgid "To which exports does the A1 type apply?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:319 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:320 msgid "Entry of goods of foreign origin to remain in national territory for an unlimited time." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:320 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 msgid "Exit of goods from the country to stay abroad for an unlimited time." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:322 msgid "Definitive importation of vehicles by diplomatic and consular missions and offices of international organizations and their foreign personnel, in accordance with the import of vehicles in diplomatic exemption." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:326 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:327 msgid "Is Foreign Trade the same as Pedimentos?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:328 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:329 msgid "Not necessarily, the Pedimentos are directly related to the process of Importing goods, while the Foreign Trade Complement is related to the Exporting process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:332 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:333 msgid "Required Modules" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:334 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:335 msgid "In order to generate foreign trade invoices, the following modules must be installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:336 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:337 msgid "EDI for Mexico (l10n_mx_edi)" msgstr "" @@ -14545,7 +15132,7 @@ msgstr "" msgid "EDI para México" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:342 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:343 msgid "EDI for Mexico (l10n_mx_edi_extended)" msgstr "" @@ -14553,587 +15140,587 @@ msgstr "" msgid "EDI Advanced Features" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:349 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:350 msgid "Company" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:351 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:352 msgid "Configure the company with a valid postal code, and if you have a colony code, this should match with the corresponding Zip Code. At the same time, remember to place the Tax Identification Number (VAT Number - RFC)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Contact address configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:360 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:361 msgid "Receiving Client" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:362 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:363 msgid "Generally it will be a foreign client, in which you must verify that you have at least the following fields completed with the corresponding information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "External trade invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:370 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:371 msgid "The customer's delivery address must also contain the zip code." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:371 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:372 msgid "The format of the foreign VAT (Tax Identification Number) will be validated as appropriate in each Country (Example: Colombia ``123456789-1``)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:373 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:374 msgid "In the XML, the VAT is automatically replaced by the Generic VAT for abroad transactions: ``XEXX010101000``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:378 msgid "Products" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:379 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:380 msgid "At the product level there must also configure some parameters in the following fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "SAT product code" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Tariff fraction" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:390 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:391 msgid "You must select the **UMT Aduana** (Unit of Measure) in *KG* since it is only accepted by the SAT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:391 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:392 msgid "The weight refers to **the unit weight** of the product" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:392 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:393 msgid "The tariff item must be from the code UoM of Kilograms (**UoM = 01**)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:394 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:395 msgid "Although the product is sold in pieces or in units, the value that must be registered with customs in the tariff item must be reported in Kilograms." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:398 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:399 msgid "Invoicing Flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:400 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:401 msgid "When creating the foreign sales invoice, you must select the **Incoterm** corresponding and the **Need external trade?** checkbox must be checked. With this configuration enabled, the **PDF** and the complement **XML** of the invoice will have the necessary information to comply with the SAT regulations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:406 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:407 msgid "What is the certificate of origin and when is it used?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:408 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:409 msgid "The **Certificate Source** (or proof of origin) is the document that allows an importer or exporter to prove the country or region from which a good is considered to originate and serves to receive tariff preferences generally agreed in trade agreements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Incoterm on invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PDF external Trade" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:421 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:422 msgid "Assign Pedimentos" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:423 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:424 msgid "If your company imports products and you need to add the **Pedimentos** number in your invoices, you can also configure Odoo to record the process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:426 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:427 msgid "First, go to :menuselection:`Apps`, remove the \"Apps\" filter and search for ``Mexico``, ``mx`` or ``l10n_mx``. Then, install **Odoo Mexico Localization for Stock / Landing module (l10n_mx_edi_landing)**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "MX stock module" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:435 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:436 msgid "The l10n_mx_edi_landing module depends on the **Inventory** and **Sales** apps, since the products must be entered into inventory to be able to add their Pedimentos number to the corresponding receipt of products." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:439 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:440 msgid "Then, go to :menuselection:`Inventory --> Settings --> Settings`. Within the options, activate **Landed Costs**. This option will allow adding the Pedimentos number to the corresponding product receptions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Costos en destino" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:448 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:449 msgid "In order to use landed costs, the accounting configuration of the inventory valuation of the products must be configured as *Automated* and its costing method *Average* or *FIFO* (first in, first out)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:452 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:453 msgid "To associate the Pedimentos number indicated with an import (merchandise reception) a new **Landed Cost** must be created. They can be accessed through :menuselection:`Inventory --> Operations --> Landed Costs`. There you will find the option to attach the Pedimentos number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Customs number" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:461 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:462 msgid "You can only add the Pedimentos number once, so be careful when associating the correct number with the transfer(s)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:465 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:466 msgid ":doc:`/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:468 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:469 msgid "Payment Terms" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:470 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:471 msgid "The **Payment Terms** are already configured in Odoo when installing the Mexican localization, this means that if you go to :menuselection:`Accounting --> Configuration --> Payment Terms`, you will find the default list in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Payment terms" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:478 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:479 msgid "In Mexico you can have 2 types of payments: PPD or PUE. These are given by the **Payment Term** chosen (or if there is no chosen payment term it will be based on the due date of the invoice)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:483 msgid "PPD Payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:484 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:485 msgid "To configure PPD payments (payment in installments or deferred) it is only necessary to choose a date expiration date for your invoice and Odoo will detect if it is after the first day of the following month (in this case no payment term is set - with the payment term you can also stipulate if it will be PPDo PUE)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:490 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:491 msgid "PUE" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:492 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:493 msgid "To configure PUE payments (payment in a single payment) you must select an invoice due date within the same month or choose a payment term that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within the current month)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:497 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 msgid "Payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:499 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:500 msgid "`According to the SAT documentation `_, there may be 2 types of payments: **PUE** or **PPD**. In both cases the payment process in Odoo is the same, the difference of whether the payment is PUE or PPD lies in the payment term of the invoice - as indicated in the previous point in the **Payment Terms**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:505 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:506 msgid "If the payment is a PPD type, Odoo will generate the corresponding payment complement automatically when you *Confirm* it. If the payment is PUE, the payment complement will not be generated. The type of payment is visible from the invoice in the field called **Payment Policy** and takes the invoice date and the due date as parameters." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Payment policy" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:514 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 msgid "When configuring the contacts that will be used when making payments, you must configure the banks in the **Accounting** tab, place both the Bank, Account Number and CLABE." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Contact bank account" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:522 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:523 msgid "Register PPD Payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:524 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:525 msgid "If at the time of registering a payment it is of type PPD then a Payment Complement (XML) will be generated with its details." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:527 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:572 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:528 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:573 msgid "The payment can be registered from the invoice and once it is confirmed, the invoice will be paid and with its payment associated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PPD payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PPD payment information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:539 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:540 msgid "The journal will be the payment method where you receive or send the payment from. You must also associate a **Payment Way** and a Recipient Bank Account (this last one must be created within the contact associated with the invoice)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:543 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:544 msgid "Once the payment is made, it will be associated with the corresponding invoice and its status will be *In Payment* since the payment will be effectively validated when it is bank reconciled." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:547 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:548 msgid ":doc:`../accounting/bank/reconciliation/use_cases`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PPD payment created" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:554 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:555 msgid "The **Recipient Bank Account** is the one attached to the **Accounting** tab in the contact associated with the invoice, it must be valid so that the stamped payment complement can be created." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:559 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:560 msgid "When making a payment in MXN for an invoice in USD, the payment must be created using the :guilabel:`Register Payment` button **on the invoice view** and not separately as a payment. Otherwise, the payment CFDI is not correctly generated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:562 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:563 msgid "As such, a payment in MXN cannot be used to pay multiple invoices in USD. Rather, the payment should be separated into multiple payments created using the :guilabel:`Register Payment` button on the corresponding invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:567 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:568 msgid "Register PUE Payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:569 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:570 msgid "If at the time of registering a payment it is of the PUE type then in this case a Payment Complement (XML) will not be generated since it is not necessary." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PUE payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PUE payment information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PUE payment created" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:588 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:589 msgid "In this case it is not created as a payment supplement by the nature of it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:591 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:592 msgid "Down Payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:593 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:594 msgid "This is a special case in which we must receive an advance payment from a client to later be applied to an invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:597 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:598 msgid "`The official documentation for registration of down payments in Mexico `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:601 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:602 msgid "Process to create advance in Mexico" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:603 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:604 msgid "Issuance of electronic invoicing with the amount of the advance payment received." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:604 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:605 msgid "Issuance of the electronic invoice for the total value of the operation (full invoice). (CFDI Origin: 07 | Advance invoice, point 1)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:606 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:607 msgid "Issuance of the electronic invoice with the *Egreso* type. (CFDI Origin: 07 | Invoice_total, point 2)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:610 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:611 msgid "Steps to follow in Odoo" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:612 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:613 msgid "Preparation: Create the product" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:613 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:614 msgid "Down Payment issuance of the electronic invoice for the amount of the advance payment received" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:614 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:615 msgid "Issuance of the electronic invoice for the total value of the operation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:615 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:616 msgid "Add a credit note from the down payment invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:618 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:619 msgid "Preparation: Create the Product" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:620 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:621 msgid "The Down Payment product must be type *Service* and must use the **NSPSC Product Category**: *84111506 Servicios de facturación*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Down payment product" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:627 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:628 msgid "Add the down payment product as default to be used from the Odoo configurations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Down payment configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:634 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:635 msgid "Issuance of the electronic invoice for the value of the advance received" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:636 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:637 msgid "Create the Advance Payment Invoice: From the sales order, create an advance payment invoice for the percentage of the purchase to be paid in advance (or for a fixed amount)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Applying down payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:643 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:644 msgid "Validate invoice with the down payment product." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Confirm down payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Folio fiscal down payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:653 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:654 msgid "Register Payment to the advance payment invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Down payment invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Down payment registered" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:664 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:665 msgid "Issuance of the electronic invoice for the total value of the operation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:666 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:667 msgid "From the sales order, create an invoice for the total, that is, for all the order lines without discounting the advance." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Full invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:674 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:675 msgid "Remove the check mark from the **Deduct down payments** field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:676 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 msgid "Add the original CFDI of the advance payment invoice by adding ``07 |`` at the beginning + Folio Fiscal of the advance payment Invoice created in the previous step." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:679 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:680 msgid "Copy the Folio Fiscal of the following invoice following this example:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Folio full invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:685 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:686 msgid "And paste it in the draft invoice created from the Sales Order without deducting the advances:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "CFDI origen folio" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:691 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:692 msgid "Validate and copy the Folio Fiscal for later (in the example the Folio Fiscal copy is: 50E4FF06-4341-4006-A7C3-A7F653CBEFAE )" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:695 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:696 msgid "Add credit note from invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:697 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:698 msgid "Create a **Credit Note** from the down payment invoice (the corrective invoice must be edited prior to confirming it, see explanation below the 2 following images)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Creation of a Credit Note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Matching down payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:708 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 msgid "Before you *Confirm* the Credit Note, edit the Origin CFDI with ``07 | XXX`` instead of the prefix ``01 | XXX``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Modify folio fiscal" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "CFDI origen type" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:719 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:720 msgid "Now the invoice can be confirmed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Post credit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:725 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:726 msgid "Now the Credit Note (Advance Payment) must be applied to the total invoice, this is added at the bottom below the amount owed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Add credit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Down payment applied" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:736 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:737 msgid "Register a payment for the difference of the down payment and the total of the sale." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Residual amount payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:742 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:743 msgid "If you go to the XML of the invoice, you should see in CFDI related the type of relationship 07 and the Folio Fiscal of the advance payment invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "XML down payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:750 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:751 msgid "Discounts based on payment days" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:752 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:753 msgid "Cash discounts are incentives that you can offer to motivate customers to pay within a specified time period. For example, you offer a 2% discount if the customer pays you within the first 5 days of the invoice, when it is due in 30 days. This approach can greatly improve your average customer payments period." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:757 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:762 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:758 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:763 msgid "Create and assign the corresponding Payment Term" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:758 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:781 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:759 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:782 msgid "Register the Payment within the days of the discount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:759 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:807 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:760 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:808 msgid "Create a credit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:764 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:765 msgid "To configure the discount for advance payment, go to :menuselection:`Accounting --> Configuration --> Payment Terms` and click on *Create*. Add a Percentage type with a corresponding value (for example, 98% of the total price for a 2% discount) and the number of days for which the offer is valid (for example 5 days). You can also change the balance due type if necessary (in this example 30 days)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Discount payment term" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:774 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:775 msgid "Then when creating our Sales Order or Sales Invoice, assign the Payment Term created previously." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "discount on invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:783 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:784 msgid "Register the payment within the days in which the application of the discount was specified, in our case it is within 5 days after the creation of the Sales Invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Discount payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:790 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:791 msgid "Then go to the bottom of the invoice where the totals are located and there you will see 2 payments created, reset to draft and cancel the payment that does not correspond - the one related to the discount." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "See discount payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Mote to draft payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Cancel payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:809 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:810 msgid "Finally to close the cycle we must close the invoice, but as in this case we apply a discount, to close it correctly we must create a credit note specifying that the difference was given to the customer on a **Credit Note**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Discount credit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Reason of credit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:821 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:822 msgid "Adjust the amount to the remaining balance in the original invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Total credit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:827 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:828 msgid "Add the Credit Note to the original invoice so that it is settled." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Add credit note for discount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:834 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:835 msgid "Cancellation of invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:837 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:838 msgid "Before 72 Hours" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:839 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:840 msgid "If it is necessary to cancel an invoice validated and sent to the SAT in less than 72 hours follow the steps below." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:842 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:843 msgid "Request Cancellation" msgstr "" @@ -15141,11 +15728,11 @@ msgstr "" msgid "Cancel within 72 hours" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:848 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:849 msgid "The status of the **Electronic invoicing** changes to *Cancelled*" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:849 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:850 msgid "Click on *RESET TO DRAFT*" msgstr "" @@ -15153,7 +15740,7 @@ msgstr "" msgid "Invoice to draft" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:855 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:856 msgid "Click on *CANCEL ENTRY*" msgstr "" @@ -15161,372 +15748,372 @@ msgstr "" msgid "Cancel journal entry" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:862 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:863 msgid "After 72 Hours" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:864 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:865 msgid "If It is necessary to cancel an invoice validated and sent to the SAT more than 72 hours, the client must be asked to accept the cancellation, for this the following steps must be followed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:867 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:868 msgid "Click on *Request EDI Cancellation* to inform the SAT that you want to cancel the invoice, in this case the client has to enter the SAT webpage and approve it. (The status of the **Electronic invoicing** field in Odoo changes to *To Cancel*)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:870 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:871 msgid "When the client (Receiver / Customer) approves the Cancellation in their SAT portal it is now possible to Change the invoice to Draft and then click on *Cancel entry*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:872 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:873 msgid "Odoo synchronizes with the SAT to update the status of the **Electronic invoicing** with a scheduled action, Invoices canceled in the SAT will be canceled in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Cancel after 72 hours" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:879 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:880 msgid "After clicking on **Request EDI cancellation**, the status of the **Electronic invoicing** field will be *To Cancel* but the status of the SAT will be the same to *Valid*, it will remain active until the end customer / Recipient approves the cancellation in the SAT." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Check estado del PAC" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:887 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:888 msgid "Once canceled in the SAT, Odoo will synchronize the status of the SAT through scheduled actions that are executed every day to synchronize the statuses of the SAT, Electronic invoicing and Odoo (this scheduled action can be executed manually by entering with developer mode)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:891 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:892 msgid "If the invoice is canceled in the SAT, in Odoo it is also canceled, which allows you to switch the invoice to draft and finally cancel the invoice (*cancel entry*)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "PAC scheduled action" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:899 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:900 msgid "Cancel Paid Invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:901 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:902 msgid "If the invoice has already been paid, a credit note must be created from the invoice so that the originating CFDI is recognized and later cancel the original invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Cancel paid invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Credit note to cancel" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:913 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:914 msgid "Cancel Invoices from the previous period" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:917 msgid "Problem" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:918 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 msgid "If the invoice is from the previous month and the period is closed, the income has already been declared in Financial Reports and to the government. In Odoo, when canceling an invoice, the journal entry is eliminated as if the income already reported had not existed, this represents a fiscal problem because the income was already declared in the previous month." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:923 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 msgid "The problem resides when the fiscal period has been closed, in the current period you have to make the reverse entry and save the cancellation information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:926 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:927 msgid "Invoice to be canceled" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Previous period" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:932 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:933 msgid "This is how the Balance Sheet looks like:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Previous BS" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:938 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:939 msgid "If the invoice is canceled, the journal entry and the Balance Sheet looks like this after canceling:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "AR in BS" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:945 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:946 msgid "Solution" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:947 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:948 msgid "Close the fiscal period every month (Best Practice Mexican Localization)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:948 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:949 msgid "Cancel invoice in SAT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:949 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:950 msgid "Create a Manual Reversion entry (Journal Entry)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:950 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:951 msgid "Reconcile the open invoice with the reversal entry (Journal Entry)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:951 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:952 msgid "Change Electronic invoicing status to Cancelled with server action" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:954 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:955 msgid "Close accounting period each month (Best Practice Mexican Localization)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:956 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:957 msgid "If the accounting period is closed due to the blocking dates, Odoo will not allow to modify or add accounting entries of a date corresponding to that accounting period." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Closing fiscal period" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:964 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:965 msgid "Cancel invoice in the SAT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:966 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:967 msgid "If the accounting period is closed, and the invoice was canceled in the SAT, the status in Odoo will be published while the **Electronic invoicing** status will be *Sent* and the SAT status is *Cancelled*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Cancel in SAT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:975 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:976 msgid "Create Manual Reversal Journal Entry" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:977 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:978 msgid "The solution is to create the reversal journal entry manually dated in the current fiscal period and reconcile the open invoice with the reversion created manually." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:980 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:981 msgid "It must be clearly indicated in the reference that it is a cancellation (you can use a cancellation account for invoices from previous periods such as **Other Income**)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Manual reversal" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:988 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:989 msgid "Reconcile the open invoice with the reversal entry" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Reconcile open invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Open invoice paid" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:998 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:999 msgid "In the Balance Sheet and Trial balance they are now with the correct balances." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "New BS" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Up to date BS" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Balanza de comprobación" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1013 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1014 msgid "Change status of Electronic invoicing to Cancelled with server action" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1015 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1016 msgid "A server action can be created that modifies the status of the invoice to *Cancelled* once it is reconciled with the reversal entry (You should check this with support or with your Assigned Functional Consultant prior to performing this action)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Scheduled action PAC status" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Execute server action" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1028 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1029 msgid "Electronic Accounting" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1030 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1031 msgid "Accounting for Mexico in Odoo is composed of 3 reports:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1032 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1046 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1047 msgid "Electronic Chart of Accounts (Called and displayed as COA)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1034 msgid "Electronic Trial Balance." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1034 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1035 msgid "DIOT report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1036 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1037 msgid "1. and 2. are considered electronic accounting, and DIOT is a report only available in the context of accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1039 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1040 msgid "You can find all of those reports in :menuselection:`Accounting --> Reporting --> Mexico`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "MX reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1048 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1049 msgid "Electronic invoicing has never been so easy, just go to :menuselection:`Accounting -> Reports -> Mexico -> COA` and click the button **Export for SAT (XML)**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "COA for SAT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1056 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1057 msgid "How to add new accounts ?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1058 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1059 msgid "If you add an account with the NNN.YY.ZZ encoding convention where NNN.YY is a SAT encoding group, your account will be set up automatically." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1061 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1062 msgid "Example to add an Account for a new Bank account go to :menuselection:`Accounting --> Settings --> Chart of Account` and then create a new account in the «Create» button and try to create an account with the number 102.01.99 once you change to establish the name you will see an automatically configured label, the configured labels are the ones chosen to be used in the COA in XML." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Create account" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1072 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1073 msgid "What is the meaning of the tags?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1074 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1075 msgid "To know all the possible labels, you can read `Annex 24 `_ on the SAT website in the section called **Código agrupador de cuentas del SAT**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1079 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1080 msgid "When you install the l10n_mx module and your chart of accounts depends on it (this happens automatically when you install the configuration of Mexico as a country in your database), it will have the most common labels by default. If the tag you need is not created, you can create it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1085 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1086 msgid "Trial Balance" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1087 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1088 msgid "Exactly like the COA but with the credit and debit of the initial balance, once you have correctly configured your COA, you can go to :menuselection:`Reports --> Trial Balance` this is automatically generated and can be exported to XML using the button on the top **Export for SAT (XML)** with the previous selection of the period you want to export." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Electronic verification balance" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1096 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1097 msgid "All normal analysis and listed functions are available here as well as any normal Odoo Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1099 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1100 msgid "DIOT Report (Requires Accounting App)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1102 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1103 msgid "What is DIOT and the importance of presenting it SAT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1104 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1105 msgid "When it comes to procedures with the SAT Administration Service, we know that we should not neglect what we present." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1107 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1108 msgid "The DIOT is the Informative Declaration of Operations with Third Parties (DIOT), which is an additional obligation with VAT, where we must give the status of our operations to third parties, or what is considered the same, with our suppliers." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1111 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1112 msgid "This applies to both individuals and Personas Morales, so if we have VAT to present to the SAT and also deal with suppliers it is necessary to send the DIOT." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1115 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1116 msgid "When to file the DIOT and in what format ?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1117 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1118 msgid "It is easy to present the DIOT, since, like all formats, you can obtain it on the SAT page, it is the electronic form A-29 that you can find on the SAT website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1120 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1121 msgid "Every month if you have operations with third parties, it is necessary to present the DIOT, as we do with VAT, so if in January we have deals with suppliers, by February we must present the information relevant to said data." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1125 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1126 msgid "Where is DIOT presented?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1127 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1128 msgid "You can present DIOT in different ways, it is up to you which one you will choose and which one will be more comfortable for you since you will present it every month or every time you have dealings with suppliers." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1131 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1132 msgid "The A-29 form is electronic so you can present it on the SAT page, but this after having made up to 500 registrations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1134 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1135 msgid "Once these 500 records have been entered in the SAT, you must submit them to the Local Taxpayer Services Administration (ALSC) with correspondence to your tax address, these records can be submitted on a digital storage medium such as a CD or USB, which a Once validated, they will return you, so do not doubt that you will still have these discs and of course, your CD or USB." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1140 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1141 msgid "One more thing to know: batch loading?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1142 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1143 msgid "When reviewing the official SAT documents in DIOT, you will find the Batch load, and of course the first thing we think is what is that ?, and according to the SAT site it is:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1145 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1146 msgid "The \"batch load\" is the conversion of databases from records of transactions with suppliers made by taxpayers in text files (.txt). These files have the necessary structure for their application and import into the Informative Declaration of Operations with third parties system, avoiding direct capture and consequently, optimizing the time invested in their integration for the presentation in time and form to the SAT." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1151 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1152 msgid "You can use it to present the DIOT, since it is allowed, which will facilitate this operation, so that it does not exist to avoid being in line with the SAT in regards to the Informative Declaration of Operations with Third Parties." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1156 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1157 msgid "`official information `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1160 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1161 msgid "How to generate this report in Odoo?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1162 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1163 msgid "Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third partied (DIOT)`." msgstr "" @@ -15534,7 +16121,7 @@ msgstr "" msgid "DIOT report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1169 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1170 msgid "A report view is displayed, select the last month to report the immediately preceding month or leave the current month if it suits you." msgstr "" @@ -15542,243 +16129,243 @@ msgstr "" msgid "DIOT filter" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1176 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1177 msgid "Click on *Export (XLSX)* or *Print (TXT)*" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Print DIOT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1182 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1183 msgid "Save the downloaded file in a safe place, go to the SAT website and follow the necessary steps to declare it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1186 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1187 msgid "Important considerations about your supplier and invoice data for DIOT" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1188 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1189 msgid "All suppliers must have the fields configured in the accounting tab called \"DIOT Information\", the L10N MX Nationality field is completed by simply selecting the appropriate country in the address, not You need to do nothing else there, but the l10n MX type of operation must be configured in all your providers." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "DIOT configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1197 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1198 msgid "There are 3 VAT options for this report, 16%, 0% and exempt, one invoice line in Odoo is considered exempt if there is no tax on it, the other 2 taxes are already configured correctly." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1199 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1200 msgid "Remember that to pay an invoice that represents a prepayment, you must first request the invoice and then pay it and properly reconcile the payment following the standard Odoo procedure." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1201 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1202 msgid "You do not need to fill in all your partner data to try to generate the supplier invoice, you can correct this information when you generate the report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1203 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1204 msgid "Remember that this report only shows vendor invoices that were actually paid." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1205 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1206 msgid "If some of these considerations are not taken into account, a message like this will appear when you generate the DIOT in TXT with all the partners you need to verify this particular report, this is the reason why we recommend to use this report not only for exporting your legal information. obligation, but generate it before the end of the month and use it as your auditory process to see that all your partners are configured correctly." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "DIOT Error" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1216 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1217 msgid "Closing Fiscal Period in Odoo" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1218 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1219 msgid "Before proceeding to the close of the fiscal year, there are some steps that you should normally take to ensure that your accounting is correct, updated and accurate:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1221 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1222 msgid "Make sure that you have fully reconciled your bank account (s) through the end of the year and confirm that the closing book balances match the balances on your bank statements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1223 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1224 msgid "Verify that all customer invoices have been entered and approved." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1224 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1225 msgid "Confirm that you have entered and approved all vendor bills." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1225 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1226 msgid "Validate all expenses, ensuring their accuracy." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1226 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1227 msgid "Check that all payments received have been entered and recorded exactly." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1231 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1232 msgid "Run a **Tax Report**, and verify that your tax information is correct." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1232 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1233 msgid "Reconcile all accounts on your **Balance Sheet**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1234 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1235 msgid "Compare your bank balances in Odoo against the current bank balances on your statements. Use the report **Bank Reconciliation** to help you with this." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1236 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1237 msgid "Reconcile all cash and bank account transactions by running your **Old Accounts Receivable** and **Old Accounts Payable** reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1238 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1239 msgid "Audit your accounts, making sure you fully understand the transactions that affect them and the nature of the transactions, making sure to include loans and fixed assets." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1241 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1242 msgid "Run the optional function **Payments Matching**, under the *More* drop-down on the Journal options from the Accounting dashboard, validating any Vendor Bill and Customer Invoices with its payments. This step is optional, however it can assist the year-end process if all pending payments and invoices are reconciled, and it can lead to finding errors or mistakes in the system." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1246 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1247 msgid "Your accountant will probably like to check your items in the balance sheet and do some Journal Entries for:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1249 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1250 msgid "Manual year-end adjustments, using the **Journal Audit** report (For example, the **Current Earnings for the Year** and **Retained Earnings reports**)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1252 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1253 msgid "**Depreciation Journals**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1254 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1255 msgid "**Tax Adjustments**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1256 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1257 msgid "If your accountant is on the year-end audit, they will want to have copies of the balance sheet items (such as loans, bank accounts, prepayments, sales tax reports, etc ...) to compare against. your balances in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1260 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1261 msgid "During this process, it is a good practice setting the **Closing Date for Non-Advisers** to the last day of the preceding financial year, which is set under the accounting settings. In this way, the accountant can trust that no one else is changing the previous year's transactions while auditing the books." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1270 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1271 msgid "Accounting Closing Process" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1272 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1273 msgid "In Odoo there is no need to make a specific year-end entry to close the reporting income accounts . The result of the exercise is automatically calculated in the account type (Current Year Earnings) and the difference between Income - Expenses will be accumulated to calculate it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1276 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1277 msgid "The reports are created in real-time, which means that the **Income Report** corresponds directly to the closing date of the year that you specify in Odoo. In addition, at any time that you generate the **Income Report**, the start date will correspond to the start date of the **Fiscal Year** and the account balances will all be 0." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1281 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1282 msgid "As of December 31, the Balance Sheet shows the earnings of the Current Year that do not have been recognized (Account type Total Current Year Unallocated Earnings in MX account 305.01.01 ['current year earnings' type])" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Balance sheet closing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1289 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1290 msgid "The accountant should create a Journal Entry to recognize the result of the year in Accumulated Earnings from previous years on the account \"previous years results\" account (304.01.01 in Mexico) - that is an equity account." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1293 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1294 msgid "After posting the Journal Entry, click on *Mark as Closing Entry for the Fiscal Year*. This step is important because it is linked to the Trial Balance report. If this Journal Entry is not marked as a Closing Entry, the Trial Balance won't be correct." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1297 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1298 msgid "The simplified accounting entry would look like this:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Closing journal entry" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1303 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1304 msgid "Once the accountant has created the journal entry to locate the **Current Earnings for the Year**, they must set the **Closing Date** to the last day of the fiscal year. Making sure that before doing this, whether or not the current gain of the year in the **Balance Sheet** is properly reporting a balance 0." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Check BS closing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1313 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1314 msgid "Extra Recommended features" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1316 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1317 msgid "Contacts App (Free)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1318 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1319 msgid "If you want to properly manage your customers, suppliers and addresses, this module, even if it is not a technical need, it is highly recommended to install it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1322 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1323 msgid "Multi-currency (Requires Accounting application)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1324 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1325 msgid "In Mexico, almost all companies send and receive payments in different currencies. If you want to do this you can enable the use of multi-currency. You should also enable synchronization with the **Mexican Bank Service**, as this would allow you to automatically have the exchange rate from the SAT without having to manually create this information every day in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1329 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1330 msgid "Go to settings and enable the multi-currency feature." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Multi currency configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1336 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1337 msgid "Enabling Explicit errors on the CFDI using the XSD local validator (CFDI 3.3)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1338 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1339 msgid "Frequently you want receive explicit errors from the fields incorrectly set on the xml, those errors are better informed to the user if the check is enable, to enable the Check with xsd feature follow the next steps (with the :ref:`developer mode ` enabled)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1343 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1344 msgid "Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1344 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1345 msgid "Look for the Action called \"Download XSD files to CFDI\"" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1345 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1346 msgid "Click on button \"Create Contextual Action\"" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1346 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1347 msgid "Go to the company form :menuselection:`Settings --> Users&Companies --> Companies`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1347 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1348 msgid "Open any company you have." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1348 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1349 msgid "Click on \"Action\" and then on \"Download XSD file to CFDI\"." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Download XSD files to CFDI from the Companies list view on Odoo" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1354 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1355 msgid "Now you can make an invoice with any error (for example a product without code which is pretty common) and an explicit error will be shown instead a generic one with no explanation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1359 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1360 msgid "If you see an error like this:" msgstr "" @@ -15790,59 +16377,59 @@ msgstr "" msgid "``attribute decl. 'TipoRelacion', attribute 'type': The QName value '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_TipoRelacion' does not resolve to a(n) simple type definition., line 36``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1366 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1367 msgid "This can be caused by a database backup restored in another server, or when the XSD files are not correctly downloaded. Follow the same steps as above but:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1370 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1371 msgid "Go to the company in which the error occurs." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1371 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1372 msgid "Click on *Action* and then on *Download XSD file to CFDI*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1374 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1375 msgid "Common problems and errors" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1376 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1377 msgid "**Error messages** (Only applicable on CFDI 3.3):" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1378 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1379 msgid "``9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'minLength'] The value '' has a length of '0'; this underruns the allowed minimum length of '1'.``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1383 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1384 msgid "``9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'pattern'] The value '' is not accepted by the pattern '[^|]{1,100}'.``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1387 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1388 msgid "**Solution**: You forgot to set the proper \"Reference\" field in the product, please go to the product form and set your internal reference properly." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1391 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1432 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1463 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1484 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1492 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1392 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1433 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1464 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1485 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1493 msgid "**Error messages**:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1393 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1394 msgid "``6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is required but missing.``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1396 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1397 msgid "``5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is required but missing.``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1399 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1400 msgid "**Solution**: You forgot to set the proper \"Fiscal Position\" on the partner of the company. Go to customers, remove the customer filter and look for the partner called as your company and set the proper fiscal position which is the kind of business your company does related to SAT list of possible values, another option can be that you forgot to follow the considerations about fiscal positions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1406 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1407 msgid "You need to go to Fiscal Position settings and set the proper code (it is the first 3 numbers of the name), for example, for the test, you need to set 601, it will look like the picture." msgstr "" @@ -15850,61 +16437,61 @@ msgstr "" msgid "Fiscal position error" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1414 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1415 msgid "For testing purposes this value must be set to ``601 - General de Ley Personas Morales`` which is the one required for the VAT demo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1417 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1449 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1418 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1450 msgid "**Error message**:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1419 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1420 msgid "``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet 'enumeration'] The value '' is not an element of the set {'01', '02', '03', '04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', '26', '27', '28', '29', '30', '99'}``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1425 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1426 msgid "**Solution**: The payment method is required on your invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Payment method error" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1434 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1435 msgid "``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': [facet 'enumeration'] The value '' is not an element of the set {'00``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1437 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1451 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1438 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1452 msgid "``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'.``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1440 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1441 msgid "``5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but missing.``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1443 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1444 msgid "**Solution**: You must configure your company address correctly, this is a mandatory group of fields, you can go to your company configuration in :menuselection:`Settings --> Users & Companies --> Companies` and fill complete all the mandatory fields for your address by following the steps in this section: :ref:`mx-legal-info`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1456 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1457 msgid "**Solution**: The postal code of your company address is not valid for Mexico, please correct it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:None +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "ZIP code error" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1465 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1466 msgid "``18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1468 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1469 msgid "``34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.\", '')``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1472 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1473 msgid "**Solution**: Set the Mexican name for the 0% and 16% tax in your system and use it on the invoice. Your tax, which represents 16% VAT and 0%, must have the **Factor Type** field set to *Tasa*." msgstr "" @@ -15924,7 +16511,7 @@ msgstr "" msgid "``The XXXX attribute must be registered if the key of cce11: ComercioExterior: TipoOperacion registered is '1' or '2'.``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1490 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1491 msgid "**Solution**: It is necessary to specify the Incoterm." msgstr "" @@ -15936,39 +16523,39 @@ msgstr "" msgid "``The attribute cce11: Foreign Trade: Goods: Goods: Customs Unit must have the value specified in the catalog catCFDI: c_FraccionArancelaria column 'UMT' when the attribute cce11: Foreign Trade: Goods: Me``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1499 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1500 msgid "**Solution**: The Tariff Fraction must have the code of the unit of measure 01, corresponding to Kilograms." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1503 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1504 msgid "Glossary" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1505 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1506 msgid ":abbr:`CFDI (Comprobante Fiscal Digital por Internet)`: Online Digital Tax Receipt" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1506 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1507 msgid ":abbr:`CSD (Certificado de Sello Digital)`: Digital Seal Certificate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1507 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1508 msgid ":abbr:`PAC (Proveedores Autorizados de Certificación)`: Authorized Certification Provider" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1508 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1509 msgid "Stamp: Digital signature of the electronic invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1509 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1510 msgid "Addenda: Complement of information that can be attached to an Internet Digital Tax Receipt (CFDI) normally required by certain companies in Mexico such as Walmart, Tiendas Sorianas, etc." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1511 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1512 msgid ":abbr:`UUID (Universally Unique Identifier)`: It is the acronym in English of the Universally Unique Identifier. The UUID is the equivalent of Folio Fiscal, it is composed of 32 hexadecimal digits, shown in 5 groups separated by hyphens." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1514 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1515 msgid "LCO: List of Obliged Taxpayers (LCO) is a list issued by the SAT that accounts for all the taxpayers whom it authorizes the issuance of invoices and payroll receipts. This means that, to be able to electronically bill your clients, you must be in this database." msgstr "" @@ -16024,7 +16611,7 @@ msgstr "" msgid "Go to *Apps* and search for Peru, then click Install in the module Peru EDI. This module has a dependency with *Peru - Accounting*. In case this last one is not installed, Odoo installs it automatically within EDI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "The \"Module\" filter is set on \"Peru\"" msgstr "" @@ -16036,7 +16623,7 @@ msgstr "" msgid "In addition to the basic information in the Company, we need to set Peru as the Country, this is essential for the Electronic Invoice to work properly. The field **Address Type Code** represents the establishment code assigned by the SUNAT when companies register their RUC (Unique Contributor Registration):" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Company data for Peru including RUC and Address type code" msgstr "" @@ -16109,9 +16696,9 @@ msgstr "" msgid "IAP (Odoo In-App Purchase)" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 #: ../../content/applications/finance/fiscal_localizations/peru.rst:106 #: ../../content/applications/finance/fiscal_localizations/peru.rst:170 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None msgid "Digiflow" msgstr "" @@ -16128,7 +16715,7 @@ msgstr "" msgid "This is the default and the suggested option, considering the digital ceritificate is included as part of the service." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "IAP option as signature providers" msgstr "" @@ -16269,7 +16856,7 @@ msgstr "" msgid "In case you don’t use Odoo IAP, in order to generate the electronic invoice signature, a digital certificate with the extension ``.pfx`` is required. Proceed to this section and load your file and password." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "EDI Certificate wizard" msgstr "" @@ -16277,7 +16864,7 @@ msgstr "" msgid "The official currency exchange rate in Peru is provided by the Bank of Peru. Odoo can connect directly to its services and get the currency rate either automatically or manually." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Bank of Peru is displayed in Multicurrency Service option" msgstr "" @@ -16289,7 +16876,7 @@ msgstr "" msgid "As part of the localization module the taxes are created automatically with their related financial account and electronic invoice configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "List of default taxes" msgstr "" @@ -16301,7 +16888,7 @@ msgstr "" msgid "As part of the taxes configuration, there are three new fields required for electronic invoice, the taxes created by default have this data included, but in case you create new taxes make sure you fill in the fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Taxes EDI data for Peru" msgstr "" @@ -16329,7 +16916,7 @@ msgstr "" msgid "The information required for the document types is included by default so the user does not need to fill anything on this view:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Document Type list" msgstr "" @@ -16357,7 +16944,7 @@ msgstr "" msgid "This section indicates which EDI workflow is used in the invoice, for Peru we must select “Peru UBL 2.1”." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Journal EDI field" msgstr "" @@ -16369,7 +16956,7 @@ msgstr "" msgid "As part of the Peruvian localization, the identification types defined by the SUNAT are now available on the Partner form, this information is essential for most transactions either on the sender company and in the customer, make sure you fill in this information in your records." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Partner identification type" msgstr "" @@ -16381,7 +16968,7 @@ msgstr "" msgid "Additional to the basic information in your products, for the Peruvian localization, the UNSPC Code on the product is a required value to be configured." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "UNSPC Code on products" msgstr "" @@ -16425,7 +17012,7 @@ msgstr "" msgid "Once you check all the information in your invoice is correct, you can proceed to validate it. This action registers the account move and triggers the Electronic invoice workflow to send it to the OSE and the SUNAT. The following message is displayed at the top of the invoice:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Sending of EDI Invoice in blue" msgstr "" @@ -16442,7 +17029,7 @@ msgstr "" msgid "**To be Sent**: To be sent: Indicates the document is ready to be sent to the OSE, this can be done either automatically by Odoo with a *cron* that runs every hour, or the user can send it immediately by clicking on the button “Sent now”." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Send EDI manually" msgstr "" @@ -16450,7 +17037,7 @@ msgstr "" msgid "**Sent**: Indicates the document was sent to the OSE and was successfully validated. As part of the validation a ZIP file is downloaded and a message is logged in the chatter indicating the correct Government validation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Message on chatter when the invoice is valid" msgstr "" @@ -16490,7 +17077,7 @@ msgstr "" msgid "After the invoice is accepted and validated by the SUNAT, the invoice PDF report can be printed. The report includes a QR code, indicating the invoice is a valid fiscal document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Invoice PDF report" msgstr "" @@ -16506,7 +17093,7 @@ msgstr "" msgid "Once you run out of credits a red label is displayed at the top of the invoice indicating that additional credits are required, you can easily buy them by accessing the link provided in the message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Buying credits in the IAP" msgstr "" @@ -16523,7 +17110,7 @@ msgstr "" msgid "Some scenarios require an invoice cancellation, for example, when an invoice was created by mistake. If the invoice was already sent and validated by the SUNAT, the correct way to proceed is by clicking on the button Request Cancellation:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Request invoice cancellation button" msgstr "" @@ -16535,7 +17122,7 @@ msgstr "" msgid "**To Cancel**: Indicates the cancellation request is ready to be sent to the OSE, this can be done either automatically by Odoo with a *cron* that runs every hour, or the user can send it immediately by clicking on the button “Send now”. Once it is sent, a cancellation ticket is created, as a result the next message and CDR File are logged in the chatter:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Cancellation CDR sent by the SUNAT" msgstr "" @@ -16543,7 +17130,7 @@ msgstr "" msgid "**Cancelled**: Indicates the cancellation request was sent to the OSE and was successfully validated. As part of the validation a ZIP file is downloaded and a message is logged in the chatter indicating the correct Government validation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "nvoice after cancellation" msgstr "" @@ -16567,7 +17154,7 @@ msgstr "" msgid "The taxes included in the invoice lines should be EXP taxes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Exportation invoices main data" msgstr "" @@ -16623,7 +17210,7 @@ msgstr "" msgid "When a correction or refund is needed over a validated invoice, a credit note must be generated, for this just click on the button “Add Credit Note”, a part of the Peruvian localization you need to prove a Credit Reason selecting one of the options in the list." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Add Credit Note from invoice" msgstr "" @@ -16635,7 +17222,7 @@ msgstr "" msgid "By default the Credit Note is set in the document type:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:None +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Credit Note document type" msgstr "" @@ -16743,7 +17330,7 @@ msgstr "" msgid "To do so, you need to configure the Journal you usually use to issue invoices. Go to :menuselection:`Accounting --> Configuration --> Journals`, open the Journal you want to modify (By default, the Journal is named *Customer Invoices*), click en *Edit*, and open the *Advanced Settings* tab. In the **Communication Standard** field, select *Switzerland*, and click on *Save*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:None +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:-1 msgid "Configure your Journal to display your ISR as payment reference on your invoices in Odoo" msgstr "" @@ -16840,7 +17427,6 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 msgid "7.7%" msgstr "" @@ -16905,7 +17491,6 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 msgid "3.7%" msgstr "" @@ -17033,7 +17618,7 @@ msgstr "" msgid "Allows sending the tax report via the MTD-VAT API to HMRC." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:None +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:-1 msgid "Odoo uk packages" msgstr "" @@ -17157,7 +17742,7 @@ msgstr "" msgid "Offering several payment methods increases the chances of getting paid in time, or even immediately, as you make it more convenient for your customers to pay with the payment method they prefer and trust." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:None +#: ../../content/applications/finance/payment_acquirers.rst:-1 msgid "Pay online in the customer portal and select which payment acquirer to use." msgstr "" @@ -17190,228 +17775,222 @@ msgid "When selected, Odoo displays your payment information with a payment refe msgstr "" #: ../../content/applications/finance/payment_acquirers.rst:0 -msgid "SEPA Direct Debit" +msgid ":doc:`SEPA Direct Debit <../finance/accounting/receivables/customer_payments/batch_sdd>`" msgstr "" #: ../../content/applications/finance/payment_acquirers.rst:0 -msgid "Your customers can sign a SEPA Direct Debit mandate online and get their bank account charged directly. :doc:`Click here <../finance/accounting/receivables/customer_payments/batch_sdd>` for more information about this payment method." +msgid "Your customers can sign a SEPA Direct Debit mandate online and get their bank account charged directly." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:61 +#: ../../content/applications/finance/payment_acquirers.rst:60 msgid "Online Payment Providers" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:64 +#: ../../content/applications/finance/payment_acquirers.rst:63 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 msgid "Redirection to the acquirer website" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:64 +#: ../../content/applications/finance/payment_acquirers.rst:63 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:81 msgid "Payment from Odoo" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:64 +#: ../../content/applications/finance/payment_acquirers.rst:63 msgid "Save Cards" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:64 +#: ../../content/applications/finance/payment_acquirers.rst:63 msgid "Capture Amount Manually" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:67 +#: ../../content/applications/finance/payment_acquirers.rst:66 msgid ":doc:`Adyen `" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:67 -#: ../../content/applications/finance/payment_acquirers.rst:70 -#: ../../content/applications/finance/payment_acquirers.rst:72 -#: ../../content/applications/finance/payment_acquirers.rst:72 -#: ../../content/applications/finance/payment_acquirers.rst:72 -#: ../../content/applications/finance/payment_acquirers.rst:72 -#: ../../content/applications/finance/payment_acquirers.rst:75 -#: ../../content/applications/finance/payment_acquirers.rst:77 -#: ../../content/applications/finance/payment_acquirers.rst:77 -#: ../../content/applications/finance/payment_acquirers.rst:77 -#: ../../content/applications/finance/payment_acquirers.rst:79 -#: ../../content/applications/finance/payment_acquirers.rst:82 -#: ../../content/applications/finance/payment_acquirers.rst:84 -#: ../../content/applications/finance/payment_acquirers.rst:86 -#: ../../content/applications/finance/payment_acquirers.rst:86 -#: ../../content/applications/finance/payment_acquirers.rst:86 +#: ../../content/applications/finance/payment_acquirers.rst:66 +#: ../../content/applications/finance/payment_acquirers.rst:69 +#: ../../content/applications/finance/payment_acquirers.rst:71 +#: ../../content/applications/finance/payment_acquirers.rst:74 +#: ../../content/applications/finance/payment_acquirers.rst:76 +#: ../../content/applications/finance/payment_acquirers.rst:78 +#: ../../content/applications/finance/payment_acquirers.rst:81 +#: ../../content/applications/finance/payment_acquirers.rst:83 +#: ../../content/applications/finance/payment_acquirers.rst:85 msgid "✔" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:70 +#: ../../content/applications/finance/payment_acquirers.rst:69 msgid "Alipay" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:72 +#: ../../content/applications/finance/payment_acquirers.rst:71 msgid ":doc:`Authorize.Net `" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:75 +#: ../../content/applications/finance/payment_acquirers.rst:74 msgid "Buckaroo" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:77 +#: ../../content/applications/finance/payment_acquirers.rst:76 msgid "Ingenico" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:79 +#: ../../content/applications/finance/payment_acquirers.rst:78 msgid ":doc:`PayPal `" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:82 +#: ../../content/applications/finance/payment_acquirers.rst:81 msgid "PayUMoney" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:84 +#: ../../content/applications/finance/payment_acquirers.rst:83 msgid "SIPS" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:86 +#: ../../content/applications/finance/payment_acquirers.rst:85 #: ../../content/applications/finance/payment_acquirers/stripe.rst:3 msgid "Stripe" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:90 +#: ../../content/applications/finance/payment_acquirers.rst:89 msgid "Some of these Online Payment Providers can also be added as :doc:`Bank Accounts <../finance/accounting/bank/setup/bank_accounts>`, but this is **not** the same process as adding them as Payment Acquirers. Payment Acquirers allow customers to pay online, and Bank Accounts are added and configured on your Accounting app to do a bank reconciliation, which is an accounting control process." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:101 +#: ../../content/applications/finance/payment_acquirers.rst:100 msgid "Some of the features described in this section are available only with some Payment Acquirers. Refer to :ref:`the table above ` for more details." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:107 +#: ../../content/applications/finance/payment_acquirers.rst:106 msgid "Add a new Payment Acquirer" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:109 -msgid "To add a new Payment acquirer and make it available to your customers, go to :menuselection:`Accounting / Website --> Configuration --> eCommerce: Payment Acquirers`, look for your payment acquirer, install the related module, and activate it. To do so, open the payment acquirer and change its state from *Disabled* to *Enabled*." +#: ../../content/applications/finance/payment_acquirers.rst:108 +msgid "To add a new Payment acquirer and make it available to your customers, go to :menuselection:`Accounting / Website --> Configuration --> Payment Acquirers`, look for your payment acquirer, install the related module, and activate it. To do so, open the payment acquirer and change its state from *Disabled* to *Enabled*." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:None +#: ../../content/applications/finance/payment_acquirers.rst:-1 msgid "Click on install, then on activate to make the payment acquirer available on Odoo." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:119 +#: ../../content/applications/finance/payment_acquirers.rst:118 msgid "We recommend using the *Test Mode* on a duplicated database or a test database. The Test Mode is meant to be used with your test/sandbox credentials, but Odoo generates Sales Orders and Invoices as usual. It isn't always possible to cancel an invoice, and this could create some issues with your invoices numbering if you were to test your payment acquirers on your main database." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:127 -#: ../../content/applications/finance/payment_acquirers/adyen.rst:24 +#: ../../content/applications/finance/payment_acquirers.rst:126 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:28 msgid "Credentials tab" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:129 +#: ../../content/applications/finance/payment_acquirers.rst:128 msgid "If not done yet, go to the **Online Payment Provider**'s website, create an account, and make sure to have the credentials required for third-party use. Odoo requires these credentials to communicate with the Payment Acquirer and get the confirmation of the *payment authentication*." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:133 +#: ../../content/applications/finance/payment_acquirers.rst:132 msgid "The form in this section is specific to the Payment Acquirer you are configuring. Please refer to the related documentation for more information." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:139 +#: ../../content/applications/finance/payment_acquirers.rst:138 msgid "Configuration tab" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:141 +#: ../../content/applications/finance/payment_acquirers.rst:140 msgid "You can change the Payment Acquirer front-end appearance by modifying its name under the **Displayed as** field and which credit card icons to display under the **Supported Payment Icons** field." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:147 +#: ../../content/applications/finance/payment_acquirers.rst:146 msgid "Save and reuse Credit Cards" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:149 +#: ../../content/applications/finance/payment_acquirers.rst:148 msgid "With the **Save Cards** feature, Odoo can store **Payment Tokens** in your database, which can be used for subsequent payments, without having to reenter the payment details. This is particularly useful for subscriptions' recurring payments." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:156 +#: ../../content/applications/finance/payment_acquirers.rst:155 msgid "Place a hold on a card" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:158 +#: ../../content/applications/finance/payment_acquirers.rst:157 msgid "If the **Capture Amount Manually** field is enabled, the funds are reserved for a few days on the customer's card, but not charged yet. You must then go to the related Sales Order and manually *capture* the funds before its automatic cancellation, or *void the transaction* to unlock the funds from the customer's card." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:166 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:74 +#: ../../content/applications/finance/payment_acquirers.rst:165 msgid "Payment Flow" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:168 +#: ../../content/applications/finance/payment_acquirers.rst:167 msgid "Choose in the **Payment Flow** field if to redirect the user to the payment acquirer's portal to authenticate the payment, or if to stay on the current page and authenticate the payment from Odoo." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:172 +#: ../../content/applications/finance/payment_acquirers.rst:171 msgid "Some features are available only if you select *Redirection to the acquirer website*." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:175 +#: ../../content/applications/finance/payment_acquirers.rst:174 msgid "When configuring a payment acquirer with the payment flow :guilabel:`Payment from Odoo`, the payment acquirer is visible only to people who have an account and are logged in on the related database. To add a payment acquirer visible to everyone, the payment flow has to be set to :guilabel:`Redirection to the acquirer website`." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:183 +#: ../../content/applications/finance/payment_acquirers.rst:182 msgid "Countries" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:185 +#: ../../content/applications/finance/payment_acquirers.rst:184 msgid "Restrict the use of the Payment Acquirer to a selection of countries. Leave this field blank to make the Payment Acquirer available to all countries." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:191 +#: ../../content/applications/finance/payment_acquirers.rst:190 msgid "Payment Journal" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:193 +#: ../../content/applications/finance/payment_acquirers.rst:192 msgid "The **Payment Journal** selected for your Payment Acquirer must be a *Bank* journal." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:196 +#: ../../content/applications/finance/payment_acquirers.rst:195 msgid "In many cases, Odoo automatically creates a new **Journal** and a new **Account** when you activate a new Payment Acquirer. Both of them are preset to work out-of-the-box, but we strongly recommend you to make sure these fields are correctly set according to your accounting needs, and adapt them if necessary." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:204 +#: ../../content/applications/finance/payment_acquirers.rst:203 msgid "Messages tab" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:206 +#: ../../content/applications/finance/payment_acquirers.rst:205 msgid "Change here the messages displayed by Odoo after a payment's confirmation or failure." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:211 +#: ../../content/applications/finance/payment_acquirers.rst:210 msgid "Multi-company environment" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:213 -msgid "If you have multiple companies on your database and wish to use the same payment acquirer for several or all of them, switch to the company on which the payment acquirer is configured, then go to :menuselection:`Accounting / Website --> Configuration --> Payments: Payment Acquirers` and select the payment acquirer to use. Then, click :menuselection:`Action --> Duplicate`, and in the :guilabel:`Company` field, set the company for which you want to have that payment acquirer available. Configure the rest of the fields according to your needs, and :guilabel:`Save`." +#: ../../content/applications/finance/payment_acquirers.rst:212 +msgid "If you have multiple companies on your database and wish to use the same payment acquirer for several or all of them, switch to the company on which the payment acquirer is configured, then go to :menuselection:`Accounting / Website --> Configuration --> Payment Acquirers` and select the payment acquirer to use. Then, click :menuselection:`Action --> Duplicate`, and in the :guilabel:`Company` field, set the company for which you want to have that payment acquirer available. Configure the rest of the fields according to your needs, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:221 +#: ../../content/applications/finance/payment_acquirers.rst:220 msgid "Creating a payment acquirer from the :guilabel:`Create` button is not supported. You *must* use the :guilabel:`Duplicate` action instead." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:227 +#: ../../content/applications/finance/payment_acquirers.rst:226 msgid "Accounting perspective" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:229 +#: ../../content/applications/finance/payment_acquirers.rst:228 msgid "The **Bank Payments** that go directly to one of your bank accounts follow their usual reconciliation workflows. However, payments recorded with **Online Payment Providers** require you to consider how you want to record your payments' journal entries. We recommend you to ask your accountant for advice." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:234 +#: ../../content/applications/finance/payment_acquirers.rst:233 msgid "Odoo default method is to record the payments on a *Current Assets Account*, on a dedicated *Bank Journal*, once the *Payment Authentication* is confirmed. At some point, you transfer the funds from the *Payment Acquirer* to your *Bank Account*." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:238 +#: ../../content/applications/finance/payment_acquirers.rst:237 msgid "Here are the requirements for this to work:" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:242 +#: ../../content/applications/finance/payment_acquirers.rst:241 msgid "The Journal's **type** must be *Bank Journal*." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:243 +#: ../../content/applications/finance/payment_acquirers.rst:242 msgid "Select the right **Default Debit Account** and **Default Credit Account**." msgstr "" @@ -17423,35 +18002,35 @@ msgstr "" msgid "This implies that the Journal Entry is recorded directly when your Odoo database receives the confirmation of the *Payment Authentication* from the Online Payment Provider." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:249 +#: ../../content/applications/finance/payment_acquirers.rst:248 msgid "Current Asset Account" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:251 +#: ../../content/applications/finance/payment_acquirers.rst:250 msgid "The Account's **type** is *Current Assets*" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:252 +#: ../../content/applications/finance/payment_acquirers.rst:251 msgid "The Account must **Allow Reconciliation**" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:255 +#: ../../content/applications/finance/payment_acquirers.rst:254 msgid "In many cases, Odoo automatically creates a new **Journal** and a new **Current Asset Account** when you activate a new Payment Acquirer. You can modify them if necessary." msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:260 +#: ../../content/applications/finance/payment_acquirers.rst:259 msgid ":doc:`../finance/accounting/receivables/customer_payments/recording`" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:261 +#: ../../content/applications/finance/payment_acquirers.rst:260 msgid ":doc:`payment_acquirers/wire_transfer`" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:262 +#: ../../content/applications/finance/payment_acquirers.rst:261 msgid ":doc:`payment_acquirers/authorize`" msgstr "" -#: ../../content/applications/finance/payment_acquirers.rst:263 +#: ../../content/applications/finance/payment_acquirers.rst:262 msgid ":doc:`payment_acquirers/paypal`" msgstr "" @@ -17472,84 +18051,88 @@ msgid ":ref:`payment_acquirers/add_new`" msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:18 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:121 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 #: ../../content/applications/finance/payment_acquirers/paypal.rst:206 msgid ":doc:`../payment_acquirers`" msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:26 -msgid "Odoo needs your **API Credentials** to connect with your Adyen account, which comprise:" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/adyen.rst:28 -msgid "**Merchant Account**: The code of the merchant account to use with Adyen." -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/adyen.rst:29 -msgid ":ref:`API Key `: The API key of the webservice user." +#: ../../content/applications/finance/payment_acquirers/adyen.rst:21 +msgid "Adyen works only with customers processing **more** than **10 million annually** or invoicing a **minimum** of **1.000** transactions **per month**." msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:30 -msgid ":ref:`HMAC Key `: The HMAC key of the webhook." +msgid "Odoo needs your **API Credentials** to connect with your Adyen account, which comprise:" msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:31 -msgid ":ref:`Checkout API URL `: The base URL for the Checkout API endpoints." +#: ../../content/applications/finance/payment_acquirers/adyen.rst:32 +msgid "**Merchant Account**: The code of the merchant account to use with Adyen." msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:33 -msgid "You can copy your credentials from your Adyen account, and paste them in the related fields under the **Credentials** tab." +msgid ":ref:`API Key `: The API key of the webservice user." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:34 +msgid ":ref:`HMAC Key `: The HMAC key of the webhook." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:35 +msgid ":ref:`Checkout API URL `: The base URL for the Checkout API endpoints." msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:37 +msgid "You can copy your credentials from your Adyen account, and paste them in the related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:41 msgid "If you are trying Adyen as a test, with a *test account*, change the **State** to *Test Mode*. We recommend doing this on a test Odoo database, rather than on your main database." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:43 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:47 msgid "API Key" msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:45 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:49 msgid "In order to retrieve the API Key, log into your Adyen account, go to :menuselection:`Developers --> API Credentials`. - If you already have an API user, open it. - If you don't have an API user yet, click on **Create new credential**. Go to :menuselection:`Authentication` and get or generate your **API Key**. Be careful to copy your API key as you'll not be allowed to get it later without generating a new one." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:55 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:59 msgid "HMAC key" msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:57 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:61 msgid "In order to retrieve the HMAC Key, you'll need to configure a `Standard Notification` webhook. For this, log into your Adyen account then go to :menuselection:`Developers --> Webhooks --> Add webhook --> Add Standard notification`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:None +#: ../../content/applications/finance/payment_acquirers/adyen.rst:-1 msgid "Configure a webhook." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:65 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:69 msgid "There, in :menuselection:`General --> Server Configuration --> URL`, enter your server address followed by `/payment/adyen/notification` and in :menuselection:`General --> Server Configuration --> Method`, select `HTTP Post`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:None +#: ../../content/applications/finance/payment_acquirers/adyen.rst:-1 msgid "Enter the notification URL." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:73 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:77 msgid "Then continue in :menuselection:`Security --> HMAC Key --> Generate new HMAC key`. Be careful to copy it as you'll not be allowed to get it later without generating a new one." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:76 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:80 msgid "You have to save the webhook to finalize its creation." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:81 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:85 msgid "URLs" msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:83 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:87 msgid "To retrieve the URLs, log into your Adyen account, go to :menuselection:`Developers --> API URLs`. Pick one of the URLs listed next to **Checkout API** as your **Checkout API URL**." msgstr "" -#: ../../content/applications/finance/payment_acquirers/adyen.rst:None +#: ../../content/applications/finance/payment_acquirers/adyen.rst:-1 msgid "Get the links for the different API." msgstr "" @@ -17614,152 +18197,151 @@ msgid "Authorize.Net" msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:5 -msgid "`Authorize.Net `__ is a United States-based online payment solution provider, allowing businesses to accept **credit cards**." +msgid "`Authorize.Net `_ is a United States-based online payment solution provider allowing businesses to accept **credit cards**. Among others, it offers the ability to process customer payments after delivery." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:None -msgid "Authorize.Net logo" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:12 -msgid "This Payment Acquirer offers additional options that are not available for other :doc:`Payment Acquirers <../payment_acquirers>`, such as the ability to process your customer's payment after delivery." -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:17 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:10 msgid "Authorize.Net account" msgstr "" +#: ../../content/applications/finance/payment_acquirers/authorize.rst:12 +msgid "First, choose a plan and `create an Authorize.Net account `_." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:15 +msgid "Odoo needs the Authorize.Net account's **API credentials and keys** to connect to it, which comprises the:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:18 +msgid "API login ID," +msgstr "" + #: ../../content/applications/finance/payment_acquirers/authorize.rst:19 -msgid "If not done yet, choose a plan and `Sign Up for an Authorize.Net account `__." +msgid "Transaction key, and" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:20 +msgid "Signature key." msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:22 -msgid "Odoo needs your **API Credentials & Keys** to connect with your Authorize.Net account, which comprise:" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:25 -msgid "API Login ID" +msgid "To retrieve them, log in to Authorize.Net and go to :menuselection:`Account --> Security Settings: API Credentials & Keys`. While the :guilabel:`API Login ID` is displayed, both keys need to be generated." msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:26 -msgid "Transaction Key" +msgid "To do so, select :guilabel:`New Transaction Key` and click :guilabel:`Submit`. Copy the key and store it somewhere secure as it will not be displayed afterward. Repeat the same process for the :guilabel:`Signature Key`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:27 -msgid "Signature Key" +#: ../../content/applications/finance/payment_acquirers/authorize.rst:-1 +msgid "Generating the transaction and signature keys on Authorize.Net" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:29 -msgid "To retrieve them, log into your Authorize.Net account, go to :menuselection:`Account --> Security Settings --> General Security Settings --> API Credentials & Keys`, and generate your **Transaction Key** and **Signature Key**." +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 +msgid "`Authorize.Net Getting Started Guide `_" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:None -msgid "Generate your Transaction Key and Signature Key on your Authorize.Net account" +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 +msgid "Refer to the :doc:`payment acquirers documentation <../payment_acquirers>` for more information about general configuration options." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:39 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:119 -msgid "`Authorize.Net: Getting Started Guide `__" +#: ../../content/applications/finance/payment_acquirers/authorize.rst:44 +msgid "To activate Authorize.Net as a payment acquirer in Odoo, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers`. Find :guilabel:`Authorize.Net`, click the :guilabel:`Activate` button, and change the :guilabel:`State` to :guilabel:`Enabled`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 -msgid "Payment Acquirer Configuration" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:45 -msgid "To configure Authorize.Net as Payment Acquirer in Odoo, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers`, open **Authorize.Net**, and change the **State** to *Enabled*. Don't forget to click on *Save* once you've set everything up." -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:50 -msgid "Please refer to the :doc:`Payment Acquirers documentation <../payment_acquirers>` to read how to configure this payment acquirer." -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:49 #: ../../content/applications/finance/payment_acquirers/paypal.rst:133 msgid "Credentials" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:56 -msgid "Copy your credentials from your Authorize.Net account (API Login Id, API Transaction Key, and API Signature Key), paste them in the related fields under the **Credentials** tab, then click on **Generate Client Key**." +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 +msgid "Fill in the :guilabel:`API Login Id`, :guilabel:`API Transaction Key`, and :guilabel:`API Signature Key` fields with the values displayed or generated on Authorize.Net's :guilabel:`API Credentials & Keys` page, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 -msgid "The **API Client Key** is necessary only if you select *Payment from Odoo* option as :ref:`Payment Flow `." +#: ../../content/applications/finance/payment_acquirers/authorize.rst:56 +msgid "An :guilabel:`API Client Key` is only necessary if the :guilabel:`Payment from Odoo` option is selected as :ref:`Payment Flow `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:60 +msgid "To test Authorize.Net with a **sandbox account**, first change the :guilabel:`State` field to :guilabel:`Test Mode`. It is recommended to do so on a test Odoo database, rather than on a production database." msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:65 -msgid "If you are trying Authorize.Net as a test, with a *sandbox account*, change the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, rather than on your main database." +msgid "If the :guilabel:`Test Mode` is used with the credentials of a non-sandbox account, it will result in the following error: *The merchant login ID or password is invalid or the account is inactive*." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 -msgid "If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account instead of a sandbox.authorize.net account, it results in the following error: *The merchant login ID or password is invalid or the account is inactive*." +#: ../../content/applications/finance/payment_acquirers/authorize.rst:70 +msgid "Payment flow" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:76 -msgid "The **Payment Flow** lets you decide if to redirect the user to the payment acquirer's portal to authenticate the payment, or if to stay on the current page and authenticate the payment from Odoo. This field is under the **Configuration** tab." +#: ../../content/applications/finance/payment_acquirers/authorize.rst:72 +msgid "It is possible either to redirect users to Authorize.Net's portal to authenticate the payment or to keep users on the current page and authenticate the payment from Odoo." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:80 -msgid "If you select *Redirection to the acquirer website*, make sure you add a **Default Receipt URL** and a **Default Relay Response URL** to your Authorize.net account." +#: ../../content/applications/finance/payment_acquirers/authorize.rst:75 +msgid "To configure the payment flow, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers --> Authorize.Net --> Configuration tab`. Under :guilabel:`Payment Flow`, select :guilabel:`Redirection to the acquirer website` or :guilabel:`Payment from Odoo` and :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:83 -msgid "To do so, log into your Authorize.Net account, go to :menuselection:`Account --> Transaction Format Settings --> Transaction Response Settings --> Response/Receipt URLs`, and set the default links:" +msgid "If :guilabel:`Payment from Odoo` is selected, an :guilabel:`API Client Key` is needed. To generate one, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers --> Authorize.Net --> Credentials tab`. Click :guilabel:`Generate Client Key` to automatically fill in the :guilabel:`API Client Key` field and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 -msgid "Default Receipt URL:" +#: ../../content/applications/finance/payment_acquirers/authorize.rst:91 +msgid "If :guilabel:`Redirection to the acquirer website` is selected, a :guilabel:`Default Receipt URL` and :guilabel:`Default Relay Response URL` should be added to the Authorize.Net account." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 -msgid "*https://[yourcompany.odoo.com]*/**payment/authorize/return**" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 -msgid "Default Relay Response URL:" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 -msgid "*https://[yourcompany.odoo.com]*/**shop/confirmation**" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 -msgid "Failing to complete this step results in the following error:" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 -msgid "*The referrer, relay response or receipt link URL is invalid.*" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/authorize.rst:96 -msgid "Capture the payment after the delivery" +#: ../../content/applications/finance/payment_acquirers/authorize.rst:94 +msgid "To do so, log in to Authorize.Net, and go to :menuselection:`Account --> Transaction Format Settings: Response/Receipt URLs`. Click :guilabel:`Add URL`, enter the URL following the format below, and click :guilabel:`Submit`:" msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:98 -msgid "The **Capture Amount Manually** field is under the **Configuration** tab. If enabled, the funds are reserved for 30 days on the customer's card, but not charged yet." +msgid ":guilabel:`Default Receipt URL`: add `/payment/authorize/return` after the main website URL." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:None -msgid "Authorize.Net Configuration tab on Odoo" +#: ../../content/applications/finance/payment_acquirers/authorize.rst:101 +msgid "`https://example.odoo.com/payment/authorize/return`" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:105 -msgid "To capture the payment, go to the related Sales Order and click on *Capture Transaction*. If the order is canceled, you can click on *Void Transaction* to unlock the funds from the customer's card." +#: ../../content/applications/finance/payment_acquirers/authorize.rst:103 +msgid ":guilabel:`Default Relay Response URL`: add `/shop/confirmation` after the main website URL." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:None -msgid "Hold the credit card payment until you capture or revoke it on Odoo" +#: ../../content/applications/finance/payment_acquirers/authorize.rst:106 +msgid "`https://example.odoo.com/shop/confirmation`" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:113 -msgid "After **30 days**, the transaction is **voided automatically** by Authorize.net." +#: ../../content/applications/finance/payment_acquirers/authorize.rst:-1 +msgid "Adding the response and receipt URLs on Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "Failing to complete this step results in the following error: *The referrer, relay response or receipt link URL is invalid*." msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:116 -msgid "With other payment acquirers, you can manage the capture in their own interfaces, not from Odoo." +msgid "Capture payments after delivery" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "To reserve funds for 30 days on the customer's card without charging them yet, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers --> Authorize.Net --> Configuration tab`, enable :guilabel:`Capture Amount Manually`, and :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:122 +msgid "To capture the payment, go to the related sales order and click :guilabel:`Capture Transaction`. If the order is canceled, click :guilabel:`Void Transaction` to unlock the funds from the customer's card." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:-1 +msgid "Capturing the payment manually" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:130 +msgid "After **30 days**, transactions are **voided automatically** by Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "`Authorize.Net: Getting Started Guide `_" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:136 #: ../../content/applications/finance/payment_acquirers/paypal.rst:207 msgid ":doc:`../../websites/ecommerce/shopper_experience/payment_acquirer`" msgstr "" @@ -18008,7 +18590,7 @@ msgstr "" msgid "To enable some of these local payment methods with Stripe, list them as supported payment icons. To do so, go to :menuselection:`Payment Acquirers --> Stripe --> Configuration` and add the desired payment methods in the **Supported Payment Icons** field. If the desired payment method is already listed, you don't have anything to do." msgstr "" -#: ../../content/applications/finance/payment_acquirers/stripe.rst:None +#: ../../content/applications/finance/payment_acquirers/stripe.rst:-1 msgid "Select and add icons of the payment methods you want to enable" msgstr "" @@ -18021,39 +18603,67 @@ msgid "When configuring a payment acquirer with the payment flow :guilabel:`Paym msgstr "" #: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:3 -msgid "How to get paid with wire transfers" +msgid "Wire transfers" msgstr "" #: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:5 -msgid "**Wire Transfer** is the default payment method available. The aim is providing your customers with your bank details so they can pay on their own. This is very easy to start with but slow and inefficient process-wise. Opt for payment acquirers as soon as you can!" +msgid "The **Wire transfer** payment method allows you to provide payment instructions to your customers, such as the bank details and communication. They are displayed:" msgstr "" -#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:12 -msgid "How to provide customers with payment instructions" +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:8 +msgid "at the end of the checkout process, once the customer has selected :guilabel:`Wire transfer` as a payment method and clicked the :guilabel:`Pay now` button:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:0 +msgid "Payment instructions at checkout" msgstr "" #: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:14 -msgid "Put your payment instructions in the **Thanks Message** of your payment method." +msgid "on the customer portal:" msgstr "" -#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:19 -msgid "They will appear to the customers when they place an order." +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:0 +msgid "Payment instructions on the customer portal" msgstr "" -#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:25 -msgid "How to manage an order once you get paid" +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:20 +msgid "While this method is very accessible and requires minimal setup, it is very inefficient process-wise. We recommend setting up a :doc:`payment acquirer <../payment_acquirers>` instead." msgstr "" -#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:27 -msgid "Whenever a customer pays by wire transfer, the order stays in an intermediary stage **Quotation Sent** (i.e. unpaid order). When you get paid, you confirm the order manually to launch the delivery." +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:22 +msgid "Online orders remain in the :guilabel:`Quotation sent` (i.e., unpaid order) stage until you receive the payment and :guilabel:`Confirm` the order." msgstr "" -#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:33 -msgid "How to create other manual payment methods" +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:26 +msgid "**Wire transfer** can be used as a template for other payment methods that are processed manually, such as checks, by renaming or duplicating it." msgstr "" -#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:35 -msgid "If you manage a B2B business, you can create other manually-processed payment methods like paying by check. To do so, just rename *Wire Transfer* or duplicate it." +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:32 +msgid "**Wire Transfer** is installed and enabled by default." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:34 +msgid "To configure it, go to :menuselection:`Accounting / Website --> Configuration --> Payment Acquirers`, and open the :guilabel:`Wire Transfer` card. Then, select the :guilabel:`Communication` to be used in the :guilabel:`Configuration` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:38 +msgid ":guilabel:`Based on Document Reference`: sales order or invoice number" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:39 +msgid ":guilabel:`Based on Customer ID`: customer identifier" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:41 +msgid "Define the payment instructions in the :guilabel:`Messages` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:-1 +msgid "Define payment instructions" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:47 +msgid ":doc:`../accounting/getting_started/cheat_sheet`" msgstr "" #: ../../content/applications/finance/sign.rst:3 @@ -18200,7 +18810,7 @@ msgstr "" msgid "Users can freely edit auto-completed fields." msgstr "" -#: ../../content/applications/finance/sign.rst:None +#: ../../content/applications/finance/sign.rst:-1 msgid "Company field example in Odoo Sign" msgstr "" @@ -18212,6 +18822,6 @@ msgstr "" msgid "Next, write a *Tip*. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process. You can also use a *Placeholder* text to be displayed inside the field before it is completed." msgstr "" -#: ../../content/applications/finance/sign.rst:None +#: ../../content/applications/finance/sign.rst:-1 msgid "Tip and placeholder example in Odoo Sign" msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index eda62d954..7de226229 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -32,7 +32,7 @@ msgstr "" msgid "By default, an *Apps* filter is applied. If you want to search for modules, click on *Filters* and select *Extra*." msgstr "" -#: ../../content/applications/general/apps_modules.rst:None +#: ../../content/applications/general/apps_modules.rst:-1 msgid "Add \"Extra\" filter in Odoo Apps" msgstr "" @@ -217,168 +217,204 @@ msgid "Don't lose your authenticator, if you do, you will need an *Odoo Administ msgstr "" #: ../../content/applications/general/auth/azure.rst:3 -msgid "OAuth" +msgid "Microsoft Azure sign-in authentication" msgstr "" #: ../../content/applications/general/auth/azure.rst:5 msgid "Due to specific requirements in Azure's OAuth implementation, Microsoft Azure OAuth identification is NOT compatible with Odoo at the moment." msgstr "" +#: ../../content/applications/general/auth/azure.rst:9 +msgid ":doc:`../../productivity/calendar/outlook`" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:10 +msgid ":doc:`/administration/maintain/azure_oauth`" +msgstr "" + #: ../../content/applications/general/auth/google.rst:3 msgid "Google Sign-In Authentication" msgstr "" #: ../../content/applications/general/auth/google.rst:5 -msgid "The **Google Sign-In Authentication** is a useful function that allows your users to sign in to Odoo with their Google account." +msgid "The *Google Sign-In Authentication* is a useful function that allows Odoo users to sign in to their database with their Google account." msgstr "" #: ../../content/applications/general/auth/google.rst:8 -msgid "This is particularly helpful if your organization uses Google Workforce and you want the employees within your organization to connect to Odoo with their Google Accounts." +msgid "This is particularly helpful if the organization uses Google Workspace, and wants employees within the organization to connect to Odoo using their Google Accounts." msgstr "" -#: ../../content/applications/general/auth/google.rst:14 +#: ../../content/applications/general/auth/google.rst:12 +msgid ":doc:`/applications/productivity/calendar/google`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:13 +msgid ":doc:`/administration/maintain/google_oauth`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:18 #: ../../content/applications/general/voip/axivox.rst:16 #: ../../content/applications/general/voip/onsip.rst:13 msgid "Configuration" msgstr "" -#: ../../content/applications/general/auth/google.rst:16 -msgid "The integration of the Google sign-in function requires configuration both on Google and on Odoo." +#: ../../content/applications/general/auth/google.rst:20 +msgid "The integration of the Google sign-in function requires configuration both on Google *and* Odoo." msgstr "" -#: ../../content/applications/general/auth/google.rst:21 +#: ../../content/applications/general/auth/google.rst:25 msgid "Google API Dashboard" msgstr "" -#: ../../content/applications/general/auth/google.rst:23 +#: ../../content/applications/general/auth/google.rst:27 msgid "Go to the `Google API Dashboard `_." msgstr "" -#: ../../content/applications/general/auth/google.rst:24 -msgid "Make sure the right project is opened. If you don't have a project yet, click on *Create Project*, fill out the project name and other details of your company, and click on *Create*." +#: ../../content/applications/general/auth/google.rst:28 +msgid "Make sure the right project is opened. If there isn't a project yet, click on :guilabel:`Create Project`, fill out the project name and other details of the company, and click on :guilabel:`Create`." msgstr "" #: ../../content/applications/general/auth/google.rst:0 -msgid "Filling out the details of a new project" -msgstr "" - -#: ../../content/applications/general/auth/google.rst:32 -msgid "Choose the name of your own company from the drop-down menu." +msgid "Filling out the details of a new project." msgstr "" #: ../../content/applications/general/auth/google.rst:37 +msgid "Choose the name of the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:42 msgid "OAuth consent screen" msgstr "" -#: ../../content/applications/general/auth/google.rst:39 +#: ../../content/applications/general/auth/google.rst:44 msgid "On the left side menu, click on :menuselection:`OAuth consent screen`." msgstr "" #: ../../content/applications/general/auth/google.rst:0 -msgid "Google oauth consent selection menu" +msgid "Google OAuth consent selection menu." msgstr "" -#: ../../content/applications/general/auth/google.rst:45 -msgid "Choose one of the options **(Internal / External)** as instructed, and click on *Create*." +#: ../../content/applications/general/auth/google.rst:50 +msgid "Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and click on :guilabel:`Create`." msgstr "" #: ../../content/applications/general/auth/google.rst:0 -msgid "Choice of a user type in oauth consent" +msgid "Choice of a user type in OAuth consent." msgstr "" -#: ../../content/applications/general/auth/google.rst:51 -msgid "Fill out your details and domain info, then click on *Save and Continue*." +#: ../../content/applications/general/auth/google.rst:58 +msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used." msgstr "" -#: ../../content/applications/general/auth/google.rst:52 -msgid "On the **Scopes** page, leave all fields as is, and click on *Save and Continue*." +#: ../../content/applications/general/auth/google.rst:62 +msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users." msgstr "" -#: ../../content/applications/general/auth/google.rst:57 +#: ../../content/applications/general/auth/google.rst:65 +msgid "Fill out the required details and domain info, then click on :guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:66 +msgid "On the :menuselection:`Scopes` page, leave all fields as is, and click on :guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:68 +msgid "Next, if continuing in testing mode (*External*), add the email addresses being configured under the :guilabel:`Test users` step by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:71 +msgid "Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:76 msgid "Credentials" msgstr "" -#: ../../content/applications/general/auth/google.rst:59 +#: ../../content/applications/general/auth/google.rst:78 msgid "On the left side menu, click on :menuselection:`Credentials`." msgstr "" #: ../../content/applications/general/auth/google.rst:0 -msgid "Credentials button menu" +msgid "Credentials button menu." msgstr "" -#: ../../content/applications/general/auth/google.rst:65 -msgid "Click on *Create Credentials* and select **OAuth client ID**." +#: ../../content/applications/general/auth/google.rst:84 +msgid "Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`." msgstr "" #: ../../content/applications/general/auth/google.rst:0 -msgid "Oauth client id selection" -msgstr "" - -#: ../../content/applications/general/auth/google.rst:71 -msgid "Select **Web Application** as the Application type. Now configure the allowed pages on which you will be redirected." -msgstr "" - -#: ../../content/applications/general/auth/google.rst:74 -msgid "In order to achieve this, in the **Authorized redirect URIs** field, enter your database's domain immediately followed by ``/auth_oauth/signin``. For example: ``https://mydomain.odoo.com/auth_oauth/signin``, then click on *Create*." -msgstr "" - -#: ../../content/applications/general/auth/google.rst:0 -msgid "Creating oauth client id" -msgstr "" - -#: ../../content/applications/general/auth/google.rst:85 -msgid "Google Authentication on Odoo" +msgid "OAuth client id selection." msgstr "" #: ../../content/applications/general/auth/google.rst:90 -msgid "Retrieve the Client ID" +msgid "Select :guilabel:`Web Application` as the :guilabel:`Application Type`. Now, configure the allowed pages on which Odoo will be redirected." msgstr "" -#: ../../content/applications/general/auth/google.rst:92 -msgid "Once you have done the previous steps, two keys are generated on the Google API Dashboard: *Client ID* and *Client Secret*. Copy the *Client ID*." +#: ../../content/applications/general/auth/google.rst:93 +msgid "In order to achieve this, in the :guilabel:`Authorized redirect URIs` field, enter the database's domain immediately followed by `/auth_oauth/signin`. For example: `https://mydomain.odoo.com/auth_oauth/signin`, then click on :guilabel:`Create`." msgstr "" -#: ../../content/applications/general/auth/google.rst:None -msgid "Google OAuth Client ID generated" -msgstr "" - -#: ../../content/applications/general/auth/google.rst:102 -msgid "Odoo activation" +#: ../../content/applications/general/auth/google.rst:97 +msgid "Now that the *OAuth client* has been created, a screen will appear with the :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the :guilabel:`Client ID` for later, as it will be necessary for the configuration in Odoo, which will be covered in the following steps." msgstr "" #: ../../content/applications/general/auth/google.rst:104 -msgid "Go to :menuselection:`Odoo General Settings --> Integrations` and activate **OAuth Authentication**." +msgid "Google Authentication on Odoo" msgstr "" -#: ../../content/applications/general/auth/google.rst:108 -msgid "You may have to log in again after this step." +#: ../../content/applications/general/auth/google.rst:109 +msgid "Retrieve the Client ID" msgstr "" -#: ../../content/applications/general/auth/google.rst:110 -msgid "Go back to :menuselection:`General Settings --> Integrations`, activate **Google Authentication**, then fill out the *Client ID* with the key from the Google API Dashboard, and *Save*." +#: ../../content/applications/general/auth/google.rst:111 +msgid "Once the previous steps are complete, two keys are generated on the Google API Dashboard: :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the :guilabel:`Client ID`." msgstr "" -#: ../../content/applications/general/auth/google.rst:0 -msgid "Filling out the client id in Odoo settings" +#: ../../content/applications/general/auth/google.rst:-1 +msgid "Google OAuth Client ID generated." msgstr "" #: ../../content/applications/general/auth/google.rst:121 -msgid "Log in to Odoo with Google" +msgid "Odoo activation" msgstr "" #: ../../content/applications/general/auth/google.rst:123 -msgid "To link your Google account to your Odoo profile, click on *Log in with Google* when you are asked to choose a new password." +msgid "Go to :menuselection:`Odoo General Settings --> Integrations` and activate :guilabel:`OAuth Authentication`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:127 +msgid "Odoo may prompt the user to log-in again after this step." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:129 +msgid "Go back to :menuselection:`General Settings --> Integrations --> OAuth Authentication`, activate the selection and :guilabel:`Save`. Next, return to :menuselection:`General Settings --> Integrations --> Google Authentication` and activate the selection. Then fill out the :guilabel:`Client ID` with the key from the Google API Dashboard, and :guilabel:`Save`." msgstr "" #: ../../content/applications/general/auth/google.rst:0 -msgid "Reset password screen with \"Log in with Google\" button" +msgid "Filling out the client id in Odoo settings." msgstr "" -#: ../../content/applications/general/auth/google.rst:130 -msgid "Existing users must :ref:`reset their password ` to access the *reset password* page, while new users can directly click on *Log in with Google* instead of choosing a new password." +#: ../../content/applications/general/auth/google.rst:139 +msgid "Google OAuth2 configuration can also be accessed by clicking on :guilabel:`OAuth Providers` under the :guilabel:`OAuth Authentication` heading in :menuselection:`Integrations`." msgstr "" -#: ../../content/applications/general/auth/google.rst:135 +#: ../../content/applications/general/auth/google.rst:145 +msgid "Log in to Odoo with Google" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:147 +msgid "To link the Google account to the Odoo profile, click on :guilabel:`Log in with Google` when first logging into Odoo." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Reset password screen with \"Log in with Google\" button." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:155 +msgid "Existing users must :ref:`reset their password ` to access the :menuselection:`Reset Password` page, while new users can directly click on :guilabel:`Log in with Google`, instead of choosing a new password." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:160 msgid "`Google Cloud Platform Console Help - Setting up OAuth 2.0 `_" msgstr "" @@ -426,326 +462,6 @@ msgstr "" msgid "In **Template User**, indicate a template for the new profiles created. If left blanked, the admin profile will be used as template." msgstr "" -#: ../../content/applications/general/calendars.rst:5 -msgid "Calendars" -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3 -msgid "Synchronize Google Calendar with Odoo" -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5 -msgid "Synchronize Google Calendar with Odoo to see and manage meetings from both platforms (updates go in both directions). This integration helps organize your schedule so you never miss a meeting." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9 -msgid "Setup in Google" -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:12 -msgid "Enable Google Calendar API" -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:14 -msgid "Begin by creating a new Google API project and enabling the Google Calendar API. Then, go to the `Google API Console `_ and log into your Google account." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18 -msgid "If this is your first time visiting this page, Google will prompt you to enter a country and agree to the Terms of Service. Select a country from the drop-down list and agree to the :abbr:`ToS (Terms of Service)`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22 -msgid "Next, click :guilabel:`Select a project` and select or create an API project to store credentials." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Create a new API project to store credentials." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:29 -msgid "Give the API Project a clear name like \"Odoo Sync\" so you can easily find it." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:31 -msgid "Then, open the API Project and click :guilabel:`Enable APIs and Services`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Enable APIs and Services on the API Project." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:37 -msgid "After that, search for *Google Calendar API* using the search bar and select :guilabel:`Google Calendar API` from the search results. Click :guilabel:`Enable`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Enable the Google Calendar API." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:45 -msgid "Create credentials" -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:47 -msgid "Now that you have created your API project and enabled the Google Calendar API, you need to create credentials. Begin by clicking :guilabel:`Create Credentials`. Google will then guide you through four steps to create your API credentials." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51 -msgid "In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google Calendar API` and :guilabel:`User Data` options. Then, click :guilabel:`Next`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Select Google Calendar API and User Data for the Credential Type." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:58 -msgid "In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the :guilabel:`App name` field, select your email address for the :guilabel:`User support email` field, and type your email address for the :guilabel:`Developer contact information` section. Then, click :guilabel:`Save and Continue`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:63 -msgid "Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and Continue`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:65 -msgid "In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website application` for the :guilabel:`Application Type` field and type *My Odoo Database* for the :guilabel:`Name`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:68 -msgid "Under the :guilabel:`Authorized JavaScript Origins` section, click :guilabel:`+ Add URI` and type your company's Odoo URL address." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:71 -msgid "Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ Add URI` and type your company's Odoo URL address followed by */google_account/authentication*. Finally, click :guilabel:`Create` and :guilabel:`Done`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Add the authorized JavaScript origins and the authorized redirect URIs." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:79 -msgid "After successfully creating a new API project, enabling the Google Calendar API, and generating the Google Calendar API credentials, you should now have a Client ID and Client Secret." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83 -msgid "Client ID & Client Secret" -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:85 -msgid "The **Client ID** and the **Client Secret** are both needed to connect Google Calendar to Odoo. Find the Client ID and the Client Secret by opening the Google Cloud Platform navigation menu and going to :menuselection:`API & Services --> Credentials --> OAuth 2.0 Client IDs`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89 -msgid "Next, locate the credentials you just created for the Google Calendar API. Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page will redirect to the edit page, where you can view the Client ID and the Client Secret." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Click Edit OAuth Client to view the credential details." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:98 -msgid "Setup in Odoo" -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:100 -msgid "Once the Client ID and the Client Secret are located, open the Odoo database and go to :menuselection:`Settings --> General Settings --> Integrations --> Google Calendar`. Check the box next to :guilabel:`Google Calendar`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "The Google Calendar checkbox in General Settings." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:108 -msgid "Next, copy and paste the Client ID and the Client Secret from the Google Calendar API Credentials page into their respective fields below the :guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112 -msgid "Finally, open the Calendar module in Odoo and click on the :guilabel:`Google` sync button to sync Google Calendar with Odoo." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Click the Google sync button in Odoo Calendar to sync Google Calendar with Odoo." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:120 -msgid "The first time you sync your Google Calendar with Odoo, the page will redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` to authorize Odoo to access Google Calendar." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Give Odoo permission to access Google Calendar." -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:127 -msgid "Now, Odoo Calendar is successfully synced with Google Calendar!" -msgstr "" - -#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:None -msgid "Successfully sync between Odoo and Google Calendar." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3 -msgid "Synchronize Outlook Calendar with Odoo" -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5 -msgid "Synchronizing a user's Outlook Calendar with Odoo is useful for keeping track of their tasks and appointments across all related applications." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9 -msgid "Register the application with Microsoft Azure" -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:11 -msgid "To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account is needed. Creating an account is free for users who have never tried or paid for Azure. For more information, `click here `_." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15 -msgid "Refer to `Microsoft's documentation `_ on how to set up an Azure AD Tenant (also called an *environment*), which is a representation of an organization to manage and register apps." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19 -msgid "Then, `Register an Application `_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:25 -msgid "When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and copy the Odoo database URI (URL) followed by `/microsoft_account/authentication`." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29 -msgid "Enter `https://www.companyname.odoo.com/microsoft_account/authentication` for the :guilabel:`Redirect URI`." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None -msgid "The \"Supported account type\" and \"Redirect URI\" settings in the Microsoft Azure AD portal." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:36 -msgid "For more information on the restrictions and limitations of URIs, `check this page `_." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:39 -msgid "Regarding the application credentials, the user *must* add a client secret, which allows Odoo to authenticate itself, requiring no interaction from the user's side. :guilabel:`Certificates` are optional." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43 -msgid "To do add a client secret, click :guilabel:`Add a certificate or secret` and then click :guilabel:`New client secret`. Next, type a :guilabel:`Description` and select when the client secret :guilabel:`Expires`." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47 -msgid "Since resetting the synchronization can be tricky, Odoo recommends setting the maximum allowed expiration date for the client secret (24 months), so there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to generate the client secret (:guilabel:`Secret ID`)." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:52 -msgid "Configuration in Odoo" -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:54 -msgid "In the Odoo database, go to :menuselection:`Settings --> General Settings --> Integrations` and activate the :guilabel:`Outlook Calendar` setting." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None -msgid "The \"Outlook Calendar\" setting activated in Odoo." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:61 -msgid "From the Microsoft Azure portal, under the :guilabel:`Overview` section of the application, copy the :guilabel:`Application (Client) ID`, and paste it into the :guilabel:`Client ID` field in Odoo." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None -msgid "The \"Client ID\" in the Microsoft Azure portal." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:68 -msgid "In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` section, copy the :guilabel:`Client Secret Value` and paste it into the :guilabel:`Client Secret` field in Odoo." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None -msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:75 -msgid "Finally, on the Odoo :menuselection:`Settings --> General Settings` page, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:80 -msgid "Sync with Outlook" -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84 -msgid "Odoo highly recommends testing the Outlook calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Outlook Calendar with the user's production database." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88 -msgid "If the user has any past, present, or future events on their Odoo calendar before syncing their Outlook calendar, Outlook will treat the events pulled from Odoo's calendar during the sync as new events, causing an email notification to be sent from Outlook to all the event attendees." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92 -msgid "To avoid unwanted emails being sent to all past, present, and future event attendees, the user must add the events from the Odoo calendar to the Outlook calendar before the first ever sync, delete the events from Odoo, and then start the sync." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96 -msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Outlook will still send a notification to all event participants every time an event is edited (created, deleted, unarchived, or event date/time changed), with no exceptions. This is a limitation that cannot be fixed from Odoo's side." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:101 -msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:108 -msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:" -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:110 -msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:111 -msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:112 -msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:113 -msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114 -msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115 -msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118 -msgid "Sync Odoo Calendar and Outlook" -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:120 -msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None -msgid "The \"Outlook\" sync button in Odoo Calendar." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:128 -msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132 -msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook `. The configuration of Microsoft's Azure account is only done once, as Azure AD tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users." -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:139 -msgid ":doc:`../../../sales/crm/optimize/outlook_extension`" -msgstr "" - -#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:140 -msgid ":doc:`../google/google_calendar_credentials`" -msgstr "" - #: ../../content/applications/general/developer_mode.rst:5 msgid "Developer Mode (debug mode)" msgstr "" @@ -762,7 +478,7 @@ msgstr "" msgid "The debug mode can be activated in the Odoo database settings. Go to :menuselection:`Settings --> General Settings --> Developer Tools` and click on :guilabel:`Activate the developer mode`. At least one application needs to be installed for the :guilabel:`Developer Tools` section to appear in the :guilabel:`Settings` module." msgstr "" -#: ../../content/applications/general/developer_mode.rst:None +#: ../../content/applications/general/developer_mode.rst:-1 msgid "Overview of the debug options under settings in Odoo." msgstr "" @@ -786,7 +502,7 @@ msgstr "" msgid "For the *Odoo Debug* extension, a single click enables a normal version of the mode, while a double click enables it with assets. To deactivate it, use a single click." msgstr "" -#: ../../content/applications/general/developer_mode.rst:None +#: ../../content/applications/general/developer_mode.rst:-1 msgid "View of Odoo's debug icon in a Google Chrome toolbar." msgstr "" @@ -798,7 +514,7 @@ msgstr "" msgid "In Odoo, the command palette tool has a command to activate the debug mode. First, open the command palette tool with the keyboard shortcut `ctrl+k` and then type `debug`. A command will show up to activate the debug mode." msgstr "" -#: ../../content/applications/general/developer_mode.rst:None +#: ../../content/applications/general/developer_mode.rst:-1 msgid "Command palette with debug command." msgstr "" @@ -810,7 +526,7 @@ msgstr "" msgid "The debug mode can also be activated by adding an extra query string to the database's URL. In the URL, add `?debug=1` or `?debug=true` after `/web`. To deactivate the debug mode, change the value to `?debug=0` instead." msgstr "" -#: ../../content/applications/general/developer_mode.rst:None +#: ../../content/applications/general/developer_mode.rst:-1 msgid "Overview of a URL with the debug mode command added." msgstr "" @@ -826,7 +542,7 @@ msgstr "" msgid "Once developer mode is activated, the developer mode tools can be accessed from the :guilabel:`Open Developer Tools` button, the bug icon located in the header of the Odoo database." msgstr "" -#: ../../content/applications/general/developer_mode.rst:None +#: ../../content/applications/general/developer_mode.rst:-1 msgid "Overview of a console page and the debug icon being shown in Odoo." msgstr "" @@ -1114,7 +830,7 @@ msgstr "" msgid "Here is a typical configuration for a G Suite server." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:None +#: ../../content/applications/general/email_communication/email_servers.rst:-1 msgid "The typical G Suite configuration on Odoo." msgstr "" @@ -1338,7 +1054,7 @@ msgstr "" msgid "To add a new one, click on *Create* and choose the type of document this template is used with. In the example below, the template would be sent to job applicants." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "New email template form in Odoo" msgstr "" @@ -1414,7 +1130,7 @@ msgstr "" msgid "To check the **fields available**, click on the link next to Applies to. For the example we use the Portal: new user template, so we click on Portal user Config." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Template is capable of using the field of the defined Models." msgstr "" @@ -1422,7 +1138,7 @@ msgstr "" msgid "By clicking on the link, you are redirected to the model, in this case the ``Portal user Config`` model that lists all the fields that you can use within your mail template." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Existing fields of a model" msgstr "" @@ -1434,7 +1150,7 @@ msgstr "" msgid "See below an example with the email field that was added in the template and its result as well as some other placeholders already present by default." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Adding a field on a template and see the result" msgstr "" @@ -1446,7 +1162,7 @@ msgstr "" msgid "Now that you know the *fields* that can be used, you can use one of them with a function. For this example, we add the creation date, *create_date* field to the body of the template ‘Portal: new user’ along with the ``format_date`` function so that the user knows when he was invited." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Example of the format_date on a create_date field" msgstr "" @@ -1462,7 +1178,7 @@ msgstr "" msgid "Find below the result of the e-mail received in the recipient's mailbox with the modifications applied." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Rendering of the format_date function on a create_date field" msgstr "" @@ -1478,7 +1194,7 @@ msgstr "" msgid "Here is the result once the function is adapted in the template." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Adapted rendering of the format_date" msgstr "" @@ -1567,7 +1283,7 @@ msgstr "" msgid "Although the field *reply to* is available within the mail templates, **this field is only used for mass mailing** mode (this means when sending templates on what we call bulk emailing). You can send emails in bulk in almost every app that has a list view. Select the records you want and click on the action button. If you have an option to send an email, you will see a mail composer with possible values to define:" msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Composer in mass mailing mode after selecting multiple quotations." msgstr "" @@ -1575,7 +1291,7 @@ msgstr "" msgid "You can also define them by default on the template:" msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:None +#: ../../content/applications/general/email_communication/email_template.rst:-1 msgid "Reply-to field on template." msgstr "" @@ -1675,7 +1391,7 @@ msgstr "" msgid "The first indicator showing you that the email has not been sent is the red envelope next to the date and time of the message." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:None +#: ../../content/applications/general/email_communication/faq.rst:-1 msgid "Red envelope displayed in chatter" msgstr "" @@ -1687,7 +1403,7 @@ msgstr "" msgid "You reached your daily limit:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:None +#: ../../content/applications/general/email_communication/faq.rst:-1 msgid "Warning in Odoo upon email limit reached" msgstr "" @@ -1739,7 +1455,7 @@ msgstr "" msgid "Wait until 11pm UTC for the reset and click on the retry button: The :ref:`Developer mode ` must be activated. Then, go to :menuselection:`Settings --> Technical --> Emails`" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:None +#: ../../content/applications/general/email_communication/faq.rst:-1 msgid "Retry button of an emails" msgstr "" @@ -1787,7 +1503,7 @@ msgstr "" msgid "The emails considered urgent (communication from one person to another one such as Sales Orders, Invoices, Purchase Orders, etc.) are sent directly." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:None +#: ../../content/applications/general/email_communication/faq.rst:-1 msgid "Email scheduled to be sent later." msgstr "" @@ -1887,7 +1603,7 @@ msgstr "" msgid "With Odoo, you can export the values from any field in any record. To do so, activate the list view on the items that need to be exported, click on *Action*, and, then, on *Export*." msgstr "" -#: ../../content/applications/general/export_import_data.rst:None +#: ../../content/applications/general/export_import_data.rst:-1 msgid "view of the different things to enable/click to export data" msgstr "" @@ -1895,7 +1611,7 @@ msgstr "" msgid "Pretty simple, this action still comes with some specificities. In fact, when clicking on *Export*, a pop-up window appears with several options for the data to export:" msgstr "" -#: ../../content/applications/general/export_import_data.rst:None +#: ../../content/applications/general/export_import_data.rst:-1 msgid "overview of all the options to take into account when exporting data in Odoo" msgstr "" @@ -2396,11 +2112,11 @@ msgstr "" msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`/developer/howtos/provide_iap_services`." msgstr "" -#: ../../content/applications/general/users.rst:7 -msgid "Users & Companies" +#: ../../content/applications/general/users.rst:5 +msgid "Users and companies" msgstr "" -#: ../../content/applications/general/users.rst:9 +#: ../../content/applications/general/users.rst:7 msgid "Odoo defines a *user* as someone who has access to a database to perform daily tasks. You can add as many users as you need and, in order to restrict the type of information each user can access, rules can be applied. Users and access rights can be added and changed at any point." msgstr "" @@ -2424,7 +2140,7 @@ msgstr "" msgid "Under *Users*, have a list of the current ones. The ones with administrative rights are shown in black." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:None +#: ../../content/applications/general/users/access_rights.rst:-1 msgid "View of a group’s form emphasizing the tab users in Odoo" msgstr "" @@ -2432,7 +2148,7 @@ msgstr "" msgid "*Inherited* means that users added to this application group are automatically added to the following ones. In the example below, users who have access to the group *Administrator* of *Sales* also have access to *Website/Restricted Editor* and *Sales/User: All Documents*." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:None +#: ../../content/applications/general/users/access_rights.rst:-1 msgid "View of a group’s form emphasizing the tab inherited in Odoo" msgstr "" @@ -2444,7 +2160,7 @@ msgstr "" msgid "The *Menus* tab is where you define which menus (models) the user can have access to." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:None +#: ../../content/applications/general/users/access_rights.rst:-1 msgid "View of a group’s form emphasizing the tab menus in Odoo" msgstr "" @@ -2468,7 +2184,7 @@ msgstr "" msgid "*Delete*: the values of that object can be deleted by the user." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:None +#: ../../content/applications/general/users/access_rights.rst:-1 msgid "View of a group’s form emphasizing the tab access rights in Odoo" msgstr "" @@ -2480,7 +2196,7 @@ msgstr "" msgid "A record rule is written using a *Domain*. Domains are conditions used to filter or searching data. Therefore, a domain expression is a list of conditions. For each rule, choose among the following options: *Read*, *Write*, *Create* and *Delete* values." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:None +#: ../../content/applications/general/users/access_rights.rst:-1 msgid "View of a group’s form emphasizing the tab record rules in Odoo" msgstr "" @@ -2504,7 +2220,7 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Manage Companies` and fill in the form with your company’s information. If a *Parent Company* is selected, records are shared between the two companies (as long as both environments are active)." msgstr "" -#: ../../content/applications/general/users/companies.rst:None +#: ../../content/applications/general/users/companies.rst:-1 msgid "Overview of a new company's form in Odoo" msgstr "" @@ -2520,7 +2236,7 @@ msgstr "" msgid "Switch between or select multiple companies by enabling their selection boxes to activate them. The grayed company is the one which environment is in use. To switch environments, click on the company’s name. In the example below, the user has access to three companies, two are activated, and the environment in use is of *JS Store US*." msgstr "" -#: ../../content/applications/general/users/companies.rst:None +#: ../../content/applications/general/users/companies.rst:-1 msgid "View of the companies menu through the main dashboard in Odoo" msgstr "" @@ -2536,7 +2252,7 @@ msgstr "" msgid "*Adding a company*: the record is visible to users logged in to that specific company." msgstr "" -#: ../../content/applications/general/users/companies.rst:None +#: ../../content/applications/general/users/companies.rst:-1 msgid "View of a product's form emphasizing the company field in Odoo Sales" msgstr "" @@ -2548,7 +2264,7 @@ msgstr "" msgid "Once companies are created, manage your employees' :doc:`Access Rights ` for *Multi Companies*." msgstr "" -#: ../../content/applications/general/users/companies.rst:None +#: ../../content/applications/general/users/companies.rst:-1 msgid "View of an user form emphasizing the multi companies field under the access rights tabs\n" "in Odoo" msgstr "" @@ -2585,7 +2301,7 @@ msgstr "" msgid "To set documents' formats according to each company, *activate* and *select* the respective one and, under *Settings*, click on *Configure Document Layout*." msgstr "" -#: ../../content/applications/general/users/companies.rst:None +#: ../../content/applications/general/users/companies.rst:-1 msgid "View of the settings page emphasizing the document layout field in Odoo" msgstr "" @@ -2625,7 +2341,7 @@ msgstr "" msgid "Now, activate the *Inter-Company Transactions* option under *Settings*. With the respective company *activated* and *selected*, choose if you would like operations between companies to be synchronized at an invoice/bills level or at a sales/purchase orders level." msgstr "" -#: ../../content/applications/general/users/companies.rst:None +#: ../../content/applications/general/users/companies.rst:-1 msgid "View of the settings page emphasizing the inter company transaction field in Odoo" msgstr "" @@ -2637,7 +2353,7 @@ msgstr "" msgid "*Example:* an invoice posted on JS Store Belgium, for JS Store US, automatically creates a vendor bill on the JS Store US, from the JS Store Belgium." msgstr "" -#: ../../content/applications/general/users/companies.rst:None +#: ../../content/applications/general/users/companies.rst:-1 msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo" msgstr "" @@ -2649,7 +2365,7 @@ msgstr "" msgid "*Example:* when a sale order for JS Store US is confirmed on JS Store Belgium, a purchase order on JS Store Belgium is automatically created (and confirmed if the *Automatic Validation* feature was enabled)." msgstr "" -#: ../../content/applications/general/users/companies.rst:None +#: ../../content/applications/general/users/companies.rst:-1 msgid "View of the purchase created on JS Store US from JS Store Belgium in Odoo" msgstr "" @@ -2669,6 +2385,30 @@ msgstr "" msgid ":doc:`../../finance/accounting/others/multicurrencies/how_it_works`" msgstr "" +#: ../../content/applications/general/users/delete_account.rst:3 +msgid "Deleting an Odoo.com Account" +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:5 +msgid "To delete your Odoo.com account, access the delete option by clicking on the user icon. The delete option can be accessed by going to :menuselection:`My Account --> Edit Security Settings --> Delete Account`. It can also be accessed by going to https://www.odoo.com/my/home." +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:10 +msgid "Deleting an Odoo account is irreversible. Take caution when performing this action as the Odoo.com account will not be retrievable." +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:13 +msgid "Upon clicking the :guilabel:`Delete Account` button, a pop-up window will appear, asking you to confirm the account deletion." +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:-1 +msgid "Clicking on the Delete Account button will populate a window verifying the change." +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:20 +msgid "Confirm the deletion by entering the :guilabel:`password` and the :guilabel:`login` for the account being deleted. Click the :guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + #: ../../content/applications/general/users/language.rst:3 msgid "Change language" msgstr "" @@ -2722,7 +2462,7 @@ msgid "To change the language for a different user, choose :menuselection:`Users msgstr "" #: ../../content/applications/general/users/language.rst:61 -msgid ":doc:`../../websites/website/publish/translate`" +msgid ":doc:`../../websites/website/configuration/translate`" msgstr "" #: ../../content/applications/general/users/manage_users.rst:3 @@ -2749,7 +2489,7 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Manage Users` and click on *Create*." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:None +#: ../../content/applications/general/users/manage_users.rst:-1 msgid "View of the settings page emphasizing the manage users field in Odoo" msgstr "" @@ -2761,7 +2501,7 @@ msgstr "" msgid "The list of applications shown is based on the applications installed on the database." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:None +#: ../../content/applications/general/users/manage_users.rst:-1 msgid "View of a user’s form emphasizing the access rights tab in Odoo" msgstr "" @@ -2769,7 +2509,7 @@ msgstr "" msgid "When you are done editing the page and have *Saved* it, an invitation email is automatically sent to the user. The user must click on it to accept the invitation and create a login." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:None +#: ../../content/applications/general/users/manage_users.rst:-1 msgid "View of a user’s form with a notification that the invitation email has been sent in Odoo" msgstr "" @@ -2781,7 +2521,7 @@ msgstr "" msgid "With the :ref:`developer mode ` activated, *User Types* can be selected." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:None +#: ../../content/applications/general/users/manage_users.rst:-1 msgid "View of a user’s form in developer mode emphasizing the user type field in Odoo" msgstr "" @@ -2821,7 +2561,7 @@ msgstr "" msgid "To do so, go to :menuselection:`Settings --> Permissions`, activate **Password Reset** and *Save*." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:None +#: ../../content/applications/general/users/manage_users.rst:-1 msgid "Enabling Password Reset in Odoo Settings" msgstr "" @@ -2841,7 +2581,7 @@ msgstr "" msgid "This email contains all the instructions needed to reset the password, along with a link redirecting the user to an Odoo login page." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:None +#: ../../content/applications/general/users/manage_users.rst:-1 msgid "Example of an email with a password reset link for an Odoo account" msgstr "" @@ -2853,7 +2593,7 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Users & Companies --> Users` and select a user to access its form. Click on the *Action* button and select *Change Password*." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:None +#: ../../content/applications/general/users/manage_users.rst:-1 msgid "Change another user's password on Odoo" msgstr "" @@ -2881,7 +2621,7 @@ msgstr "" msgid "Note that if not handled correctly, it may be the source of a lot of inconsistent multi-company behaviors. Therefore, a good knowledge of Odoo is required. For technical explanations refer to :doc:`this ` documentation." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:None +#: ../../content/applications/general/users/manage_users.rst:-1 msgid "View of a user’s form emphasizing the multi companies field in Odoo" msgstr "" @@ -2953,7 +2693,7 @@ msgstr "" msgid "From the main Odoo dashboard, select the :guilabel:`Contacts` application. If the contact is not yet created in the database, click on the :guilabel:`Create` button, enter the details of the contact, and then click :guilabel:`Save`. Otherwise, choose an existing contact, and then click on the :guilabel:`Action` drop-down menu located at the top-center of the interface." msgstr "" -#: ../../content/applications/general/users/portal.rst:None +#: ../../content/applications/general/users/portal.rst:-1 msgid "Use the Contacts application to give portal access to users" msgstr "" @@ -2977,7 +2717,7 @@ msgstr "" msgid "To grant portal access, first enter the contact's :guilabel:`Email` they will use to log into the portal. Then, check the box under the :guilabel:`In Portal` column. Optionally, add text to the invitation message the contact will receive. Then click :guilabel:`Apply` to finish." msgstr "" -#: ../../content/applications/general/users/portal.rst:None +#: ../../content/applications/general/users/portal.rst:-1 msgid "An email address and corresponding checkbox for the contact need to be filled in before\n" "sending a portal invitation." msgstr "" @@ -3211,7 +2951,7 @@ msgstr "" msgid "Go to :menuselection:`Apps` and install the **VoIP Module**." msgstr "" -#: ../../content/applications/general/voip/axivox.rst:None +#: ../../content/applications/general/voip/axivox.rst:-1 msgid "VoIP module installation on an Odoo database" msgstr "" @@ -3231,7 +2971,7 @@ msgstr "" msgid "**VoIP Environment**: set as *Production*" msgstr "" -#: ../../content/applications/general/voip/axivox.rst:None +#: ../../content/applications/general/voip/axivox.rst:-1 msgid "Integration of Axivox as VoIP provider in an Odoo database" msgstr "" @@ -3251,7 +2991,7 @@ msgstr "" msgid "**SIP Password**: the Axivox *SIP Password*" msgstr "" -#: ../../content/applications/general/voip/axivox.rst:None +#: ../../content/applications/general/voip/axivox.rst:-1 msgid "Integration of Axivox user in the Odoo user preference" msgstr "" @@ -3279,7 +3019,7 @@ msgstr "" msgid "Your number is the one provided by Axivox." msgstr "" -#: ../../content/applications/general/voip/axivox.rst:None +#: ../../content/applications/general/voip/axivox.rst:-1 msgid "Incoming VoIP call in Odoo" msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index dc3770697..f5971998c 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -78,10 +78,9 @@ msgid "When you have scanned all the items of the location, validate the invento msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:3 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:6 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:6 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:6 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:6 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:6 #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:6 @@ -214,8 +213,6 @@ msgid "If you have different storage locations in your warehouse, you can add ad msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:37 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:50 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:45 msgid "Receipts" msgstr "" @@ -228,7 +225,6 @@ msgid "If you want the product to enter WH/Stock in our example, you can simply msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:52 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery.rst:5 msgid "Delivery Orders" msgstr "" @@ -345,20 +341,14 @@ msgid "The barcode scanning features can save you a lot of time usually lost swi msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:12 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:37 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:50 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:51 #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:6 #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:15 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:15 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:17 @@ -367,7 +357,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:66 #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:26 #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:9 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 msgid "Configuration" msgstr "" @@ -419,670 +409,6 @@ msgstr "" msgid "Warehouse Management" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:3 -msgid "Send Products to Customers Directly from Suppliers (Drop-shipping)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:6 -msgid "What is Drop-Shipping?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:8 -msgid "Drop-Shipping is a system that allows orders taken from your store to be shipped straight from your supplier to your customer. On a usual delivery system, products are sent from your supplier to your warehouse to be put in stock and then shipped to your customers after ordering." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:13 -msgid "With drop-shipping, no item is stocked. When a customer places an order in your shop, the item is delivered straight from the supplier to the customer. Therefore, the product doesn't need to get through your warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:19 -msgid "Points to be Considered while Implementing Drop-Shipping" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:24 -msgid "Use drop-shipping only for the products you can't or don't want to keep in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:22 -msgid "One reason is that you'll always make smaller margins on items that are drop-shipped, so you should keep it only for items that take up a lot of space in your warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:30 -msgid "Drop-shipping is best for niche products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:27 -msgid "Chances are that products that are in high demand are being offered by large suppliers at a fraction of the price you'll be able to charge, so using a more costly shipping method won't be financially rewarding. But if your product is unique, then it makes sense!" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:33 -msgid "To protect your customers from bad experiences." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:33 -msgid "Test drop-shipping companies for yourself beforehand and list the best ones." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:37 -msgid "Make sure time is not against you." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:36 -msgid "Drop-shipping should take a reasonable amount of time and surely not more than it would have taken you to handle it all by yourself. It's also nice to be able to provide your customers with a tracking number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:44 -msgid "Items have to be available from your supplier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:40 -msgid "It's good to know if the product you're selling is available upstream. If you don't have that information, inform your customers that you don't hold the item in stock and that it's subject to availability from a third party." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:47 -msgid "For more information and insights about Drop-Shipping, you can read our blog: `*What is drop-shipping and how to use it* `__." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:52 -msgid "Configure Drop-Shipping" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:54 -msgid "Activate the functionality in the *Purchase* application by going to :menuselection:`Configuration --> Settings`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:60 -msgid "Then, go to the *Inventory* app, in :menuselection:`Configuration --> Settings` to activate the *Multi-Step Routes* feature. It will allow you to make the *Route* field appear on the sale order lines to specify you send a product via drop-shipping." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:68 -msgid "Now, in the *Sales* app, go to :menuselection:`Products --> Products`. Select the product you would like to drop-ship and add a vendor pricelist which contains the right supplier, via the purchase tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:76 -msgid "Send Products from the Suppliers Directly to the Customers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:78 -msgid "Create a *Sales Order* and add the product on which you just set the vendor. Add the *Route* field thanks to the widget on the right of the sale order line. Now, you are able to specify that your products’ route is *Drop-Shipping*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:89 -msgid "Once the sale order is confirmed, Odoo automatically generates a *Request for Quotation* for the supplier who will proceed to the drop-shipping. You can find it in the *Purchase* app, with the sale order as *Source Document*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:97 -msgid "Once this *Purchase Order* is confirmed, a *Receipt Order* is created and linked to it. The source location is the vendor location and the destination location is the customer location. Then, the product won’t go through your own stock when you validate the dropship document." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:105 -msgid "You can also easily access the dropship document directly from your inventory dashboard." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:3 -msgid "How to choose the right inventory flow to handle delivery orders?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:5 -msgid "Depending on factors such as the type of items you sell, the size of your warehouse, the number of orders you register everyday... the way you handle deliveries to your customers can vary a lot." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:9 -msgid "Odoo allows you to handle shipping from your warehouse in 3 different ways:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:12 -msgid "**One step (shipping)**: Ship directly from stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:14 -msgid "**Two steps (pick + ship)**: Bring goods to output location before shipping" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:17 -msgid "**Three steps (pick + pack + ship)**: Make packages into a dedicated location, then bring them to the output location for shipping" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:20 -msgid "For companies having a rather small warehouse and that do not require high stock of items or don't sell perishable items, a one step shipping is the simplest solution, as it does not require a lot of configuration and allows to handle orders very quickly." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:25 -msgid "Using inventory methods such as FIFO, LIFO and FEFO require to have at least two steps to handle a shipment. The picking method will be determined by the removal strategy, and the items removed will then be shipped to the customer. This method is also interesting if you hold larger stocks and especially when the items you stock are big in size." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:31 -msgid "The three steps system becomes useful in more specific situations, the main one being for handling very large stocks. The items are transferred to a packing area, where they will be assembled by area of destination, and then set to outbound trucks for final delivery to the customers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:40 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:53 -msgid "One step flow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:42 -msgid "Please read documentation on :doc:`one_step`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:45 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:58 -msgid "Two steps flow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:47 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:60 -msgid "Please read documentation on :doc:`two_steps`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:50 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:63 -msgid "Three steps flow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:52 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:65 -msgid "Please read documentation on :doc:`three_steps`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:3 -msgid "How can I change the label type?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:8 -msgid "With Odoo, you can choose among different types of labels for your delivery orders. Follow the steps below and give an appropriate label type to your delivery." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:15 -msgid "In the **Inventory** module, Go to **Configuration** and click on **Delivery methods**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:18 -msgid "Choose a delivery method and then click on **Edit**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:23 -msgid "In the **Pricing** tab, under **Fedex label stock type**, you can choose one of the label types available. The availability will vary depending on the carrier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:30 -msgid "Once this is done, you can see the result if you go to the Sales module and you create a new sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:33 -msgid "As you confirm the sale and validate the delivery with the carrier for which you have modified the label type, The label will appear in your history." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/label_type.rst:46 -msgid "The default label type is paper letter, and if you choose the label type bottom half for example, here is the difference :" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:3 -msgid "Process Delivery Orders in one Step (Shipping)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:5 -msgid "There is no configuration needed to deliver in one step. The default outgoing shipments are configured to be directly delivered from the stock to the customers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:9 -msgid "However, if advanced routes have been activated and you set another shipping configuration on your warehouse, you can set it back to the one-step delivery configuration. Go to :menuselection:`Inventory --> Configuration --> Warehouses` and edit the warehouse in question." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:14 -msgid "Then, choose *Deliver goods directly* as your *Outgoing Shipments* strategy." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:21 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:45 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:47 -msgid "Create a Sales Order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:23 -msgid "In the *Sales* application, create a quotation with some storable products to deliver and confirm it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:26 -msgid "Notice that we now see 1 delivery associated with this *sales order* in the stat button above the sales order. If you click on the 1 Delivery stat button, you should now see your delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:34 -msgid "Process a Delivery" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:36 -msgid "You can also find the *delivery order* directly from the *Inventory* application. In the dashboard, you can click the *1 TO PROCESS* button under the Delivery Orders Kanban card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:43 -msgid "Enter the picking that you want to process. You will be able to click on *Validate* to complete the move if you have products in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/one_step.rst:49 -msgid "Once you *Validate* the delivery order, the products leave your *WH/Stock location* and are moved to the *Customer location*. You can easily see that the delivery took place thanks to the status of the document which is now *Done*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:3 -msgid "Process Delivery Orders in three Steps (Pick + Pack + Ship)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:5 -msgid "When an order goes to the shipping department for final delivery, Odoo is set up by default to utilize a one-step operation: once all goods are available, they are able to be shipped in a single delivery order. However, that process may not reflect reality and your company could require more steps before shipping." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:11 -msgid "With the delivery in 3 steps (Pick + Pack + Ship), the items will be picked to be transferred to a packing area. Then, they will be moved to an output location before being effectively shipped to the customers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:15 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:19 -msgid "Activate Multi-Step Routes" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:17 -msgid "The first step is to allow using *multi-step routes*. Indeed, routes provide a mechanism to chain different actions together. In this case, we will chain the picking step to the shipping step." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:22 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:21 -msgid "To allow *multi-step routes*, go to :menuselection:`Inventory --> Configuration --> Settings` and activate the option. Note that activating *Multi-Step Routes* will also activate *Storage Locations*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:30 -msgid "Configure Warehouse for Delivery in 3 Steps" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:32 -msgid "Once *Multi-Step Routes* has been activated, you can go to :menuselection:`Inventory --> Configuration --> Warehouse` and enter the warehouse which will use delivery in 3 steps. You can then select the option *Pack goods, send goods in output and then deliver (3 steps)* for *Outgoing Shipments*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:40 -msgid "Activating this option will lead to the creation of two new locations, *Output* and *Packing Zone*. If you want to rename it go to :menuselection:`Inventory --> Configuration --> Locations`, *Select* the one you want to rename and update its name." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:47 -msgid "In the *Sales* application, you can create a quotation with some storable products to deliver. Once you confirm the quotation, three pickings will be created and automatically linked to your sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:54 -msgid "If you click the button, you should now see three different pickings:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:56 -msgid "The first one with a reference PICK to designate the picking process," -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:58 -msgid "The second one with the reference PACK that is the packing process," -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:60 -msgid "The last one with a reference OUT to designate the shipping process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:66 -msgid "Process the Picking, Packing, and Delivery" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:68 -msgid "The picking operation is the first one to be processed and has a *Ready* status while the other ones are *Waiting Another Operation*. The Packing operation will become *Ready* as soon as the picking one is marked as done." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:73 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:71 -msgid "You can enter the picking operation from here, or access it through the inventory dashboard." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:79 -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:77 -msgid "In case you have the product in stock, it has automatically been reserved and you can simply validate the picking document." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:85 -msgid "Once the picking has been validated, the packing order is ready to be processed. Thanks to the fact that the documents are chained, the products which have been previously picked are automatically reserved on the packing order which can be directly validated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/three_steps.rst:96 -msgid "Once the packing has been validated, the delivery order is ready to be processed. Here again, it is directly ready to be validated in order to transfer the products to the customer location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:3 -msgid "Process Delivery Orders in two Steps (Pick + Ship)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:5 -msgid "When an order goes to the shipping department for final delivery, Odoo is set up by default to utilize a one-step operation: once all goods are available, they are able to be shipped in a single delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:9 -msgid "However, your company's business process may have one or more steps that happen before shipping. In the two steps process, the products which are part of the delivery order are picked in the warehouse and brought to an output location before being effectively shipped." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:29 -msgid "Warehouse configuration" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:31 -msgid "Once *Multi-Step Routes* has been activated, you can go to :menuselection:`Inventory --> Configuration --> Warehouse` and enter the warehouse which will use delivery in 2 steps. You can then select the option *Send goods in output and then deliver (2 steps)* for Outgoing Shipments." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:39 -msgid "Activating this option will lead to the creation of a new *Output* location. If you want to rename it go to :menuselection:`Inventory --> Configuration --> Locations`, Select Output and update its name." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:49 -msgid "In the *Sales* application, you can create a quotation with some storable products to deliver. Once you confirm the quotation, two pickings will be created and automatically linked to your sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:56 -msgid "If you click on the *2 Delivery* button, you should now see two different pickings, one with a reference *PICK* to designate the picking process and another one with a reference *OUT* to designate the shipping process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:65 -msgid "Process the Picking and the Delivery" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:67 -msgid "The picking operation is the first one to be processed and has a *Ready* status while the delivery operation will only become *Ready* once the picking operation has been marked as done." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/two_steps.rst:83 -msgid "Once the picking has been validated, the delivery order is ready to be processed. Thanks to the fact that the documents are chained, the products which have been previously picked are automatically reserved on the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming.rst:5 -msgid "Incoming Shipments" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:3 -msgid "How to choose the right flow to handle receipts?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:8 -msgid "Depending on factors such as the type of items you receive, the size of your warehouse, the number of receipt you register everyday... the way you handle receipts to your customers can vary a lot." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:12 -msgid "Odoo allows you to handle receipts from your warehouse in 3 different ways:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:15 -msgid "**One step**: Receive goods directly in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:17 -msgid "**Two steps**: Unload in input location then go to stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:19 -msgid "**Three steps**: Unload in input location, go through a quality control before being admitted in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:22 -msgid "Odoo uses **routes** to define exactly how you will handle the different receipt steps. The configuration is done at the level of the warehouse. In standard, the reception is a one step process, but changing the configuration can allow to have 2 or even 3 steps." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:27 -msgid "The principles are the following:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:29 -msgid "**One step**: You receive the goods directly in your stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:31 -msgid "**Two steps**: You receive the goods in an input area then transfer them from input area to your stock. As long as the goods are not transferred in your stock, they will not be available for further processing." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:36 -msgid "**Three steps**: In many companies, it is necessary to assess the received good. The goal is to check that the products correspond to the quality requirements agreed with the suppliers. Adding a quality control step in the goods receipt process can become essential." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:42 -msgid "You receive the goods in an input area, then transfer them into quality area for quality control. When your quality check process finishes then you can move the goods from QC to stock. Of course, you may change the quantity and only transfer to Stock the quantity that is valid and decide that you will return the quantity that is not good." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:55 -msgid "This is the default configuration in Odoo." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:68 -msgid ":doc:`../delivery/inventory_flow`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/handle_receipts.rst:69 -msgid ":doc:`/applications/inventory_and_mrp/purchase/advanced/analyze`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:3 -msgid "Process a Receipt in one step (Receipt)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:5 -msgid "There is no configuration needed to receive in one step. The default incoming shipments are configured to be directly received from the vendors to the stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:9 -msgid "However, if advanced routes have been activated and you set another incoming configuration on your warehouse, you can set it back to the one-step receipt configuration. To do so, go to :menuselection:`Configuration --> Warehouses` and edit the warehouse in question." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:14 -msgid "Set the *Incoming Shipments* option to *Receive goods directly (1 step)*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:21 -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:50 -msgid "Create a Purchase Order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:23 -msgid "To create a *Request for Quotation*, go to the *Purchase* application and click on *Create*. Then, add some storable products to receive and confirm the *RfQ*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:27 -msgid "Notice that, now, we see 1 receipt associated with the purchase order you just created. If you click on the button, you will see your receipt order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:35 -msgid "Process a Receipt" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:37 -msgid "You can also fin the receipt directly from the *Inventory* app. When on the dashboard, you can click the *1 TO PROCESS* button under the *Receipts* Kanban card. Then, you will see your receipt." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:44 -msgid "Now, enter the picking that you want to process. You will be able to click on *Validate* to complete the move directly as products coming from suppliers are considered as being always available." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:49 -msgid "If you have :guilabel:`Storage Locations` activated, you can click the hamburger menu next to the :guilabel:`Done quantity` to specify the location(s) where you are storing the received product(s)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:56 -msgid "Once you *Validate* the receipt, the products leave the *Supplier Location* to enter your *WH/Stock Location*. You can easily see that the receipt took place thanks to the status of the document, which is now *Done*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:3 -msgid "Process a Receipt in three steps (Input + Quality + Stock)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:5 -msgid "Quality is essential for most companies. To make sure we maintain quality throughout the supply chain, it only makes sense that we assess the quality of the products received from suppliers. To do so, we will add a quality control step." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:9 -msgid "Odoo uses routes to define how to handle the different receipt steps. Configuration of those routes is done at the warehouse level. By default, the reception is a one-step process, but it can also be configured to have two-steps or three-steps processes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:13 -msgid "The three-steps flow works as follows: you receive the goods in your receiving area, then transfer them into a quality area for quality control (QC). When the quality check is completed, the goods that match the QC requirements are moved to stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:20 -msgid "The first step is to allow the use of *Multi-Step Routes*. Routes provide a mechanism to chain different actions together. In this case, we will chain the picking step to the shipping step." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:23 -msgid "To enable *Multi-Step Routes*, go to :menuselection:`Inventory --> Configuration --> Settings` and activate the option." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -msgid "View of the features to enable in order to use multi-step routes for goods reception" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:31 -msgid "By default, activating *Multi-Step Routes* also activates *Storage Locations*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:35 -msgid "Configure warehouse for receipt in 3-steps" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:37 -msgid "Once *Multi-Step Routes* has been activated, go to :menuselection:`Inventory --> Configuration --> Warehouse` and enter the warehouse which should work with the 3-steps reception. Then, select *Receive goods in input, then quality and then stock (3 steps)* for *Incoming Shipments*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -msgid "View of the incoming shipment strategy to choose to receive goods in three steps" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:45 -msgid "Activating this option leads to the creation of two new locations: *Input* and *Quality Control*. To rename them, go to :menuselection:`Inventory --> Configuration --> Locations` and select the one you want to rename." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:52 -msgid "To start the 3-steps reception process, create a *Request for Quotation* from the *Purchase* app, add some storable products to it and confirm. Then, three pickings are created with your *Purchase Order* as the source document:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:56 -msgid "The first one with a reference *IN* to designate the receipt process;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:59 -msgid "The second one with a reference *INT*, which is the move to the quality control zone;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:62 -msgid "The last one with a reference *INT* to designate the move to stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -msgid "View of the three moves created by the purchase of products in three steps strategy" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:69 -msgid "Process the receipt, quality control and entry in stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:71 -msgid "As the receipt operation is the first one to be processed, it has a *Ready* status while the others are *Waiting Another Operation*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:74 -msgid "To access the receipt operation, click on the button from the *Purchase Order* or go back to the *Inventory* app dashboard and click on *Receipts*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -msgid "View of the button to click to see the receipts that need to be processed" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:81 -msgid "In the receipt order, products are always considered available because they come from the supplier. Then, the receipt can be validated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -msgid "View of the move (internal transfer) from the reception area to the warehouse input area" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:88 -msgid "Once the receipt has been validated, the transfer to quality becomes *Ready*. And, because the documents are chained to each other, products previously received are automatically reserved on the transfer. Then, the transfer can be directly validated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -msgid "View of the button to click to see the internal transfers that need to be processed" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -msgid "View of the move (internal transfer) from the input area to the quality control area" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:100 -msgid "Now, the transfer that enters the products to stock is *Ready*. Here, it is again ready to be validated in order to transfer the products to your stock location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/three_steps.rst:None -msgid "View of the move (internal transfer) from the quality control area to the stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:3 -msgid "Process a Receipt in two steps (Input + Stock)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:8 -msgid "Odoo uses routes to define exactly how you will handle the different receipt steps. The configuration is done at the *Warehouse* level. By default, the reception is a one-step process, but changing the configuration can allow you to have 2 steps." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:13 -msgid "The 2 steps flow is like this: you receive the goods in an input area, then transfer them to your stock. As long as the goods are not transferred in your stock, they will not be available for further processing." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:21 -msgid "The first step is to allow using *multi-step routes*. Indeed, routes provide a mechanism to chain different actions together. In this case, we will chain the unload step in the input area to the step entering the products in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:26 -msgid "To allow *multi-step routes*, go to :menuselection:`Configuration --> Settings` and activate the feature. By default, activating *multi-step routes* will also activate *Storage Locations*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:34 -msgid "Configure warehouse for receipt in 2 steps" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:36 -msgid "Once *multi-step routes* is activated, you can go to :menuselection:`Configuration --> Warehouse` and enter the warehouse which will use receipt in 2 steps. Then, you can select the option *Receive goods in input and then stock (2 steps)* for *Incoming Shipments*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:44 -msgid "Activating this option will lead to the creation of a new *Input* location. If you want to rename it, you can go to :menuselection:`Configuration --> Locations --> Select Input` and update its name." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:52 -msgid "Create a purchase order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:54 -msgid "In the *Purchase* application, you can create a *Request for Quotation* with some storable products to receive from a supplier. Once the *RfQ* is confirmed, the receipt picking will be created and automatically linked to your purchase order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:62 -msgid "Now, by clicking on the *1 Receipt* button, you will see the first picking which will allow entering the product in the *input location*. Then, another picking, an internal transfer, has been created in order to move the products to *Stock*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:68 -msgid "Process the receipt and the internal transfer" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:70 -msgid "The receipt is the first one to be processed and has a *Ready* status while the internal transfer will only become *Ready* once the receipt has been marked as *Done*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:74 -msgid "You can enter the receipt operation from the purchase order, or access it through the inventory dashboard." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:80 -msgid "By default, a receipt is always considered as ready to be processed. Then, you will be able to directly click on *Validate* to mark it as done." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:87 -msgid "Once the receipt has been validated, the internal transfer is ready to be processed. As documents are chained, the products which have been received are automatically reserved on the internal transfer. Once the transfer is validated, those products enter the stock and you will be able to use them to fulfill customer deliveries or manufacture products." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers.rst:5 msgid "Lots and Serial Numbers" msgstr "" @@ -1091,323 +417,958 @@ msgstr "" msgid "What's the difference between lots and serial numbers?" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:8 msgid "Introduction" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:8 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:10 msgid "In Odoo, lots and serial numbers have similarities in their functional system but are different in their behavior. They are both managed within the **Inventory**, **Purchases** and **Sales** app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:14 msgid "**Lots** correspond to a certain number of products you received and store altogether in one single pack." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:17 msgid "**Serial numbers** are identification numbers given to one product in particular, to allow to track the history of the item from reception to delivery and after-sales." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:22 msgid "When to use" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:24 msgid "**Lots** are interesting for products you receive in great quantity and for which a lot number can help in reportings, quality controls, or any other info. Lots will help identify a number of pieces having for instance a production fault. It can be useful for a batch production of clothes or food." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:28 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:30 msgid "**Serial numbers** are interesting for items that could require after-sales service, such as smartphones, laptops, fridges, and any electronic devices. You could use the manufacturer's serial number or your own, depending on the way you manage these products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:36 msgid "When not to use" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:38 msgid "Storing consumable products such as kitchen roll, toilet paper, pens and paper blocks in lots would make no sense at all, as there are very few chances that you can return them for production fault." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:42 msgid "On the other hand, giving a serial number to every product is a time-consuming task that will have a purpose only in the case of items that have a warranty and/or after-sales services. Putting a serial number on bread, for instance, makes no sense at all." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:48 msgid ":doc:`serial_numbers`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:49 msgid ":doc:`lots`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:3 -msgid "Expiration Dates" +msgid "Expiration dates" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:5 -msgid "In many companies, products have expiration dates and they should be managed based on those dates. In the food industry, for example, tracking and managing product stock based on expiration dates is mandatory to avoid selling expired products to customers." +msgid "In Odoo, *expiration dates* can be used to manage and track the lifecycles of perishable products, from purchase to sale. Using expiration dates reduces product loss due to unexpected expiry, and helps to avoid sending expired products to customers." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:9 -msgid "With Odoo, you can track and manage your products based on their expiration dates, even if they are already tracked by lots or serial numbers." +msgid "In Odoo, only products that are tracked using *lots* and *serial numbers* can be assigned expiration information. Once a lot or serial number has been assigned, an expiration date can be set. This is especially helpful for companies (such as food manufacturers) that consistently, or exclusively, buy and sell perishable products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:17 +msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:18 -msgid "Application configuration" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:19 +msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:18 -msgid "To use expiration date tracking, open the *Inventory* application and go to :menuselection:`Configuration --> Settings` and activate the *Lots & Serial Numbers* and *Expiration Dates* features." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:19 +msgid "Enable expiration dates" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:26 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:28 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:68 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:90 -msgid "Product configuration" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:21 +msgid "To enable the use of *expiration dates*, go to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Traceability` section. Then, click the checkbox to enable the :guilabel:`Lots & Serial Numbers` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:28 -msgid "Now, you can define different dates in the *inventory tab* of the product form:" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:25 +msgid "Once that feature is activated, a new option will appear to enable :guilabel:`Expiration Dates`. Click that checkbox to enable the feature, and be sure to :guilabel:`Save` changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:30 -msgid "Product Use Time: the number of days before the goods start deteriorating, without being dangerous. This is used to calculate the Best before date on each lot/serial number received." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Enabled lots and serial numbers and expiration dates settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:32 -msgid "Product Life Time: the number of days before the goods may become dangerous and must not be consumed. This is used to calculate the Expiration date on each lot/serial number received." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:33 +msgid "Once the :guilabel:`Lots & Serial Numbers` feature is activated, additional features appear to :guilabel:`Display Lots & Serial Numbers on Delivery Slips`; to :guilabel:`Display Lots & Serial Numbers on Invoices`; and to :guilabel:`Display Expiration Dates on Delivery Slips`. Activating these features helps with end-to-end traceability, making it easier to manage product recalls, identify \"bad\" batches of products, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:34 -msgid "Product Removal Time: shows the number of days before the goods should be removed from the stock. This is used to calculate the Removal date on each lot/serial number received." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:40 +msgid "Configure expiration dates on products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:36 -msgid "Product Alert Time: refers to the number of days before an alert should be raised on the lot/serial number. This is used to calculate the Alert date on each lot/serial number received. Once the Alert date is reached, an Activity is assigned on the relevant lot/serial number to the Responsible user defined on the Product." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:42 +msgid "Once the :guilabel:`Lots & Serial Numbers` and :guilabel:`Expiration Dates` features have been enabled in the settings of the *Inventory* app, expiration information can be configured on individual products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:45 -msgid "Expiration Date on Lots/Serial Numbers" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:46 +msgid "To do so, go to :menuselection:`Inventory app --> Products --> Products`, and select a product to edit. Selecting a product reveals the product form for that particular item. Once on the product form, click :guilabel:`Edit` in the upper-left corner to make changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:47 -msgid "When receiving a product into inventory, the dates will automatically be updated on the corresponding lot/serial number. These updates will be based on the receipt date of the product and the days set on the product form." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:51 +msgid "To be tracked using lots or serial numbers, or to configure expiration information, products *must* have their :guilabel:`Product Type` set as :guilabel:`Storable Product` under the :guilabel:`General Information` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:58 -msgid "Expiration Alerts" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:55 +msgid "Then, click the :guilabel:`Inventory` tab, and scroll down to the :guilabel:`Traceability` section. From here, make sure that either :guilabel:`By Unique Serial Number` or :guilabel:`By Lots` is checked." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:60 -msgid "You can access expiration alerts from the *inventory* app. To do so, go to :menuselection:`Master Data --> Lots/Serial Numbers`. There, you can use the pre-existing filter to show all the lots/serial numbers that have exceeded their respective alert dates." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:59 +msgid "Once it is, a new :guilabel:`Expiration Date` checkbox appears that must also be clicked. When both are enabled, a new :guilabel:`Dates` field appears to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:63 +msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed in order to assign lot numbers to the existing stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:68 +msgid "For processing large quantities of products on receipts or deliveries, it is recommended to track using lots, so multiple products can be traced back to the same lot, if any issues arise." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Expiration dates configuration on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:75 +msgid "Under the :guilabel:`Dates` field, there are four categories of expiration information to configure for the product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:78 +msgid ":guilabel:`Expiration Time`: the number of days after receiving products (either from a vendor or in stock after production) in which goods may become dangerous and should not be used or consumed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:80 +msgid ":guilabel:`Best Before Time`: the number of days before the expiration date in which the goods start deteriorating, **without** necessarily being dangerous yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:82 +msgid ":guilabel:`Removal Time`: the number of days before the expiration date in which the goods should be removed from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:84 +msgid ":guilabel:`Alert Time`: the number of days before the expiration date in which an alert should be raised on goods in a particular lot or containing a particular serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:88 +msgid "The values entered into these fields automatically compute the expiration date for goods entered into stock, whether purchased from a vendor or manufactured in-house." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:91 +msgid "Once all the expiration information has been configured, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:94 +msgid "If the :guilabel:`Dates` field is not populated with any values for expiration information, dates (and lots) can be manually assigned upon receipts and deliveries in and out of the warehouse. Even when assigned, they can still be overwritten and changed manually if needed, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:99 +msgid "Set expiration dates on receipts with lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:101 +msgid "Generating expiration dates for **incoming** goods can be done directly from the purchase order. To create a purchase order, go to the :menuselection:`Purchase` app and click :guilabel:`Create` to create a new request for quotation (RFQ)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:105 +msgid "Then, fill out the information by adding a :guilabel:`Vendor`, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:108 +msgid "Choose the desired quantity to order by changing the number in the :guilabel:`Quantity` column, and click :guilabel:`Confirm Order`. This converts the :abbr:`RFQ (request for quotation)` into a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:112 +msgid "Click the :guilabel:`Receipt` smart button at the top of the purchase order to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:116 +msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities causes a :guilabel:`User Error` popup to appear. The popup requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` cannot be validated without an assigned lot or serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:0 +msgid "User error popup when validating an order with no lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:125 +msgid "From here, click the :guilabel:`Additional Options` menu (hamburger) icon located on the far-right of the product line. When clicked, a :guilabel:`Detailed Operations` pop-up will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:128 +msgid "In this pop-up, click :guilabel:`Add a line`, and assign a lot or serial number under the :guilabel:`Lot/Serial Number Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:131 +msgid "An expiration date automatically populates, based on the configuration on the product form (if previously configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:135 +msgid "If the :guilabel:`Dates` field on the product form has not been configured, this date can be manually entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:138 +msgid "After the expiration date has been established, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Finally, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Detailed operations popup showing expiration dates for ordered products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:145 +msgid "A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document; the :guilabel:`Product` being traced; the :guilabel:`Lot/Serial #`; and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:151 +msgid "Set expiration dates on manufactured products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:153 +msgid "Expiration dates can also be generated for products manufactured in-house. To assign expiration dates to manufactured products, a manufacturing order (MO) needs to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:156 +msgid "To create a :abbr:`MO (manufacturing order)`, go to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, and click :guilabel:`Create`. Choose a product to manufacture from the :guilabel:`Product` field drop-down menu, then select the :guilabel:`Quantity` to produce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Manufacturing order for product with expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:165 +msgid "To manufacture a product, there must be materials to consume in the lines in the :guilabel:`Product` column. This can be achieved either by creating a :guilabel:`Bill of Material` for the :guilabel:`Product`, or manually adding materials to consume by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:170 +msgid "Once ready, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:172 +msgid "Next to :guilabel:`Lot/Serial Number`, either select an existing lot number from the drop-down menu, or click the green :guilabel:`+` sign to automatically assign a new lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:175 +msgid "Then, select a number of units for the :guilabel:`Quantity` field, and click :guilabel:`Mark as Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:178 +msgid "Click on the :guilabel:`External Link` icon in the assigned :guilabel:`Lot/Serial Number` field. A pop-up appears, revealing a detail form for that specific number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:181 +msgid "On that pop-up, under the :guilabel:`Dates` tab, all expiration information that was previously configured for the product is displayed. That same information is also available on the detail form for that specific product, or by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Dates tab with expiration information for specific lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:191 +msgid "Sell products with expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:193 +msgid "Selling perishable products with expiration dates is done the same as any other type of product. The first step in selling perishable products is to create a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:196 +msgid "To do that, go to :menuselection:`Sales app --> Create` to create a new quotation, and fill out the information on the sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:199 +msgid "Add a :guilabel:`Customer`, click :guilabel:`Add a product` to add the desired products to the :guilabel:`Product` lines, and set a :guilabel:`Quantity` for the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:202 +msgid "Then, click the :guilabel:`Other Info` tab. Under the :guilabel:`Delivery` section, change the :guilabel:`Delivery Date` to a date after the expected date, and click the :guilabel:`green checkmark` icon to confirm the date. Finally, click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:206 +msgid "Next, click the :guilabel:`Delivery` smart button at the top of the sales order to see the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:209 +msgid "On the warehouse receipt form, click :guilabel:`Validate`, and then :guilabel:`Apply` in the accompanying pop-up window, to automatically process all :guilabel:`Done` quantities, and deliver the products to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:213 +msgid "If the products are delivered before the :guilabel:`Alert Date` set on the product form, then no alerts will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:217 +msgid "To sell perishable products with expiration dates, the :guilabel:`Removal Strategy` for the :guilabel:`Location` the products are stored in must be set to :abbr:`FEFO (First Expiry, First Out)`. If there is not enough stock of perishable products in one lot, Odoo will automatically take the remaining quantity required from a second lot with the next-soonest expiration date. Removal strategies can also be set on :guilabel:`Product Categories`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:224 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:209 +msgid ":doc:`/applications/inventory_and_mrp/inventory/routes/strategies/removal`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:227 +msgid "View expiration dates for lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:229 +msgid "To view (and/or group) all products with expiration dates by lot number, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:232 +msgid "Once there, remove any default search filters from the :guilabel:`Search...` bar. Then, click :guilabel:`Group By`, choose :guilabel:`Add Custom Group`, and select the :guilabel:`Expiration Date` parameter from the drop-down menu. Finally, click :guilabel:`Apply` to apply the filter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:236 +msgid "Doing so breaks down all perishable products, their expiration dates, and the assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Group by expiration dates on lots and serial numbers page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:243 +msgid "Expiration alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:245 +msgid "To see expiration alerts, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:247 +msgid "Then, click into a :guilabel:`Lot/Serial Number` with perishable products. Doing so reveals the serial number detail form. On the serial number detail form, click the :guilabel:`Dates` tab to see all expiration information related to the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:251 +msgid "To edit the form, click :guilabel:`Edit` in the upper-left corner of the form, then change the :guilabel:`Expiration Date` to today's date (or earlier), and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:255 +msgid "After saving, the lot number form displays a red :guilabel:`Expiration Alert` at the top of the form to indicate that the products in this lot are either expired or expiring soon. From here, click back to the :guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:259 +msgid "To see the new expiration alert, or any expiration alerts for products that are expired (or will expire soon), remove all of the search filters from the :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:263 +msgid "Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Expiration alert for product past the expiration date." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:3 -msgid "Manage lots of identical products" +msgid "Use lots to manage groups of products" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:5 -msgid "Lots are useful for products you receive in great quantity and for which a lot number can help in reporting, quality controls, or any other info. Lots will help identify a number of pieces having, for instance, a production fault. It can be useful for a batch production of clothes or food." +msgid "*Lots* are one of the two ways to identify and track products in Odoo. A lot usually indicates a specific batch of an item that was received, is currently stored, or was shipped from a warehouse, but can also pertain to a batch of products manufactured in-house, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:11 -msgid "Odoo has the capacity to manage lots, ensuring compliance with the traceability requirements imposed by the majority of industries." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:9 +msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps to identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their lifecycles." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:14 -msgid "The double-entry management in Odoo enables you to run very advanced traceability." +msgid "Lots are useful for products that are manufactured or received in large quantities (such as clothes or food), and can be used to trace a product back to a group. This is especially useful when managing product recalls or expiration dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:18 -msgid "Setting Up" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:20 +msgid "Enable lots & serial numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:21 -msgid "Application Configuration" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:24 +msgid "To track products using lots, the *Lots & Serial Numbers* feature must be enabled. Go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:23 -msgid "First, you need to activate the tracking of lot numbers. To do so, go to :menuselection:`Inventory --> Configuration --> Settings` and tick *Lots & Serial Numbers*. Then, click on save." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 +msgid "Enabled lots and serial numbers feature in inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:31 -msgid "Product Configuration" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:33 -msgid "Now, you have to configure which products you want to track by serial numbers." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:34 +msgid "Track products by lots" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:36 -msgid "Go to :menuselection:`Master Data --> Products` and open the product of your choice. There, click on *Edit* and select *Tracking by Lots* in the inventory tab." +msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be configured to be tracked using lots. To do this, go to the :menuselection:`Inventory app --> Products --> Products`, and choose a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:47 -msgid "Manage Lots" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:40 +msgid "Once on the product form, click :guilabel:`Edit` to make changes to the form. Then, click the :guilabel:`Inventory` tab. In the :guilabel:`Traceability` section, click :guilabel:`By Lots`. Then, click :guilabel:`Save` to save changes. Existing or new lot numbers can now be assigned to newly-received or manufactured batches of this product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:52 -msgid "In order to receive a product tracked by lots, you have to specify its lot numbers. You have several ways of doing so:" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:46 +msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed to assign lot numbers to the existing stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:55 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:65 -msgid "Manually assign the different lot numbers" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 +msgid "Enabled tracking by lots feature on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:57 -msgid "Copy/paste lot numbers from an Excel file" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:54 +msgid "Create new lots for products already in stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:59 -msgid "First, you need to open the detailed operations of your picking." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:56 +msgid "New lots can be created for products already in stock with no assigned lot number. To do this, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a separate page where a new :guilabel:`Lot/Serial Number` is generated automatically." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:67 -msgid "When opening the detailed operations, you can click on *Add a line*. Then, you will be able to fill the lot number in. Once done, you can click on *Add a line* again to register a new lot number." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:62 +msgid "While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:66 +msgid "Once the new :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:70 +msgid "This form also provides the option to adjust the :guilabel:`Quantity`, assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and assign this specific lot or serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:75 -msgid "Copy/paste lot number from an Excel file" +msgid "A detailed description of this specific lot or serial number can also be added in the :guilabel:`Description` tab below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:77 -msgid "Once the spreadsheet containing the lot numbers you received from your supplier and copy the list. Then, you can paste them in the *Lot/Serial Number Name* column for Odoo to automatically create the necessary lines. After that, you will have to manually enter the number of products that are contained in each one of the lots." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:79 +msgid "When all desired configurations are complete, click the :guilabel:`Save` button to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 +msgid "New lot number creation form with assigned product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:84 +msgid "After a new lot number has been created, saved, and assigned to the desired product, navigate back to the product form in the :menuselection:`Inventory` app, by going to :menuselection:`Products --> Products`, and selecting the product to which this newly-created lot number was just assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:88 +msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new lot number. When additional quantity of this product is received or manufactured, this new lot number can be selected and assigned to it." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:93 -msgid "Operation Types" +msgid "Manage lots for shipping and receiving" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:95 -msgid "Of course, you also have the possibility to define how you will manage lots for each operation type. To do so, open the *Inventory* app and go to :menuselection:`Configuration --> Operation Types`." +msgid "Lot numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, lot numbers are assigned directly on the purchase order form. For outgoing goods, lot numbers are assigned directly on the sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:99 -msgid "For each type (receipts, internal transfers, deliveries, …), you can decide if you allow to create new lot numbers or only use existing ones. By default, the creation of new lots is only allowed at product reception, and using existing lot numbers isn’t allowed in this operation. If you have inter-warehouse transfers and track products by lots, it can be useful to allow using existing lot numbers in receipts too." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:100 +msgid "Manage lots on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:102 +msgid "Assigning lot numbers to **incoming** goods can be done directly from the purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:104 +msgid "To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:107 +msgid "On this :abbr:`RFQ (request for quotation)`, fill out the necessary information by adding a :guilabel:`Vendor`, and adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` (under the :guilabel:`Products` tab)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:111 +msgid "Choose the desired quantity of the product to order by changing the number in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:114 +msgid "Once the :abbr:`RFQ (request for quotation)` has been filled out, click :guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is confirmed, it becomes a :guilabel:`Purchase Order`, and a :guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:120 +msgid "Clicking :guilabel:`Validate` before assigning a lot number to the ordered product quantities will result in a :guilabel:`User Error` pop-up. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a lot number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 +msgid "Add lot/serial number user error popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:129 +msgid "From here, click the :guilabel:`Additional Options` menu, represented by a :guilabel:`hamburger (four horizontal lines)` icon, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:133 +msgid "In this pop-up, configure a number of different fields, including the assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:136 +msgid "There are two ways to assign lot numbers: **manually** and **copy/paste**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:138 +msgid "**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the location the products will be stored in under the :guilabel:`To` column. Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:0 +msgid "Assign lot number detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:147 +msgid "If quantities should be processed in multiple locations and lots, click :guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for additional quantities. Repeat until the :guilabel:`Quantity Done` matches the :guilabel:`Demand`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:151 +msgid "**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with all of the lot numbers received from the supplier (or manually chosen to assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column. From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the lot number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:0 +msgid "List of lot numbers copied on excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:161 +msgid "Once all product quantities have been assigned a lot number, click :guilabel:`Confirm` to close the pop-up. Then, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:164 +msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #` assigned, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:170 +msgid "Manage lots on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:172 +msgid "Assigning lot numbers to **outgoing** goods can be done directly from the sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:174 +msgid "To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app --> Create`. Doing so reveals a new, blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:177 +msgid "On this blank quotation form, fill out the necessary information by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:181 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:219 +msgid "Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:183 +msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, it becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:187 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:225 +msgid "Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:190 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:228 +msgid "From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:194 +msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with the full :guilabel:`Reserved` quantity taken from that specific lot (if there is enough stock in that particular lot)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:198 +msgid "If there is insufficient stock in that lot, or if partial quantities of the :guilabel:`Demand` should be taken from multiple lots, change the quantity in the :guilabel:`Done` column to only include that specific part of the total quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:203 +msgid "The lot automatically chosen for delivery orders varies, depending on the selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will also depend on the quantity ordered, and if there is enough quantity in one lot to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:211 +msgid "Then, click :guilabel:`Add a line`, select an additional (different) :guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 +msgid "Detailed operations popup for source lot number on sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:219 +msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:224 +msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order, if the product quantities shared the same lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:228 +msgid "Manage lots for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:230 +msgid "In Odoo, the creation of new lots is only allowed upon **receiving** products from a purchase order, by default. **Existing** lot numbers cannot be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:233 +msgid "For sales orders, the opposite is true: new lot numbers cannot be created on the delivery order, only existing lot numbers can be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:236 +msgid "To change the ability to use new (or existing) lot numbers on any operation type, go to the :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:240 +msgid "For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:245 +msgid "For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. Be sure to click the :guilabel:`Save` button to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 +msgid "Enabled traceability setting on operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:254 +msgid "For inter-warehouse transfers involving products tracked by lots, it can be useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for warehouse receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:258 msgid "Lots traceability" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:113 -msgid "The lot number given to the products allows you to keep track of where they were received, put in stock, to whom they were sold and where they were shipped to." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:260 +msgid "Manufacturers and companies can refer to traceability reports to see the entire lifecycle of a product: where (and when) it came from, where it was stored, and who (and when) it went to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:117 -msgid "To track an item, open the *Inventory* module and, in :menuselection:`Master Data --> Lots/Serial Numbers`, click on the lot number corresponding to your search." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:263 +msgid "To see the full traceability of a product, or group by lots, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :menuselection:`Lots/Serial Numbers` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:124 -msgid "When you open the *Traceability* information, you see in which documents the lot number has been used." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:267 +msgid "From here, products with lot numbers assigned to them will be listed by default, and can be expanded to show the lot numbers those products have assigned to them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:130 -msgid "Now, if you want to locate the lot number, you can do so by clicking on the *Location* stat button." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:270 +msgid "To group by lots (or serial numbers), begin by removing any filters in the search bar. Then, click the :guilabel:`Group By` drop-down, select :guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from the drop-down menu. Then, click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:274 +msgid "Doing so displays all existing lots and serial numbers, and can be expanded to show all quantities of products with that assigned number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 +msgid "Lots and serial numbers traceability report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:282 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:317 +msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:3 -msgid "Work with serial numbers" +msgid "Use serial numbers to track products" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:5 -msgid "To track products with serial numbers, you can use the serial number tracking. With them, you can track the current location of the product and, when the products are moved from one location to another, the system will automatically identify the current location of the product, based on its last movement." +msgid "*Serial numbers* are one of the two ways to identify and track products in Odoo. A serial number is a unique identifier assigned incrementally (or sequentially) to an item or product, used to distinguish it from other items and products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:11 -msgid "If you want to do it or run very advanced traceability, the Odoo double-entry management is the feature you need." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:9 +msgid "Serial numbers can consist of many different types of characters: they can be strictly numerical, they can contain letters and other typographical symbols, or they can be a mix of all of the above." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:15 -msgid "Configurations" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:12 +msgid "The goal of assigning serial numbers to individual products is to make sure that every item's history is identifiable when it travels through the supply chain. This can be especially useful for manufacturers that provide after-sales services to products that they sell and deliver." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:20 -msgid "First, you need to activate the serial numbers tracking. To do so, go to :menuselection:`Configuration --> Settings` in the *Inventory* application. Then, enable the feature and hit save." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:22 +msgid "To track products using serial numbers, the :guilabel:`Lots & Serial Numbers` feature must be enabled. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` button to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:30 -msgid "Now, you have to configure the products you want to track by serial numbers. To do so, go to :menuselection:`Master Data --> Products` and open the product of your choice. Edit it and select *Tracking By Unique Serial Number* in the *Inventory tab*. Then, click on save." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "Enabled lots and serial numbers setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:42 -msgid "Manage Serial Numbers" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:32 +msgid "Configure serial number tracking on products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:47 -msgid "To receive a product that is tracked by serial number, you have to specify its serial number. Of course, you have several ways of doing so:" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:34 +msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be tracked using serial numbers. To configure this, go to :menuselection:`Inventory app --> Products --> Products`, and choose a desired product to track." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:38 +msgid "Once on the product form, click :guilabel:`Edit`, and click the :guilabel:`Inventory` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:40 +msgid "Once on the product form, click :guilabel:`Edit`, navigate to the :guilabel:`Inventory` tab, and scroll to the :guilabel:`Traceability` section. Then, select the :guilabel:`By Unique Serial Number` option, and click :guilabel:`Save` to save the changes. Existing or new serial numbers can now be selected and assigned to newly-received or manufactured batches of this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "Enabled serial number tracking on product form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:50 -msgid "Manual assignation" +msgid "If a product doesn't have a serial number assigned to it, a user error pop-up window will appear. The error message states that the product(s) in stock have no lot/serial number. However, a lot/serial number can be assigned to the product by making an inventory adjustment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:52 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:73 -msgid "Multi-assignation" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:55 +msgid "Create new serial numbers for products already in stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:54 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:89 -msgid "Copy/pasting from an Excel file" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:56 -msgid "Whatever could be your favorite way to assign serial numbers, you firstly need to open the detailed operations of your picking." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:57 +msgid "New serial numbers can be created for products already in stock with no assigned serial number. To do this, go to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a blank lots/serial numbers form. On this form, a new :guilabel:`Lot/Serial Number` is generated automatically." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:63 -msgid "Manual assignation of the different serial numbers" +msgid "While Odoo automatically generates a new lot/serial number to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:65 -msgid "When opening the detailed operations, you can click on *Add a line*. Then, you will be able to fill in the serial number field. Once done, you can click again on *Add a line* to register a new serial number." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:67 +msgid "Once the :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:75 -msgid "By using the multi-assignation of serial numbers, Odoo will automatically create the necessary lines. To do so, you have to enter the first serial number of your set and the number of products you have to assign a serial number to." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:71 +msgid "This form also provides the option to adjust the :guilabel:`Quantity`, to assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and to assign this specific lot/serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:80 -msgid "Once done, click on *Assign Serial Numbers* and Odoo will do the rest." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:76 +msgid "A detailed description of this specific lot/serial number can also be added in the :guilabel:`Description` tab below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:91 -msgid "To use copy/pasting, open the spreadsheet containing the serial numbers you received and copy the list. Then, past them in the *Lot/Serial Number Name* column of the wizard. Doing so, Odoo will automatically create the lines you need." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "New serial number created for existing product stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:106 -msgid "Operation types" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:85 +msgid "After a new serial number has been created, assigned to the desired product, and saved, navigate back to the product form, by going to :menuselection:`Products --> Products`, and selecting the product that this newly-created serial number was just assigned to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:108 -msgid "You also have the possibility to define how you will manage lots for each operation type. To define it, go to :menuselection:`Configuration --> Operation Types` in the *Inventory* app." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:89 +msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new serial number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:112 -msgid "For each type, you can decide if you allow the creation of new lot numbers or want to use existing ones. By default, the creation of new lots is only allowed at product reception." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:93 +msgid "Manage serial numbers for shipping and receiving" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:120 -msgid "If you have inter-warehouse transfers and track products by lots, it can be useful to allow using existing lot numbers in receipts too." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:95 +msgid "Serial numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, serial numbers are assigned directly on the purchase order form. For outgoing goods, serial numbers are assigned directly on the sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:124 -msgid "Serial Number traceability" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:100 +msgid "Manage serial numbers on receipts" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:126 -msgid "Using serial numbers allows you to keep track of where the products were received, put in stock, to whom they were sold, and where they were shipped to." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:102 +msgid "Assigning serial numbers to **incoming** goods can be done directly from the purchase order (PO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:130 -msgid "Tracking an item is easy: open the *Inventory* app, and go to :menuselection:`Master Data --> Lots/Serial Numbers` and click on the serial number corresponding to your search. Then, open the *Traceability* information. There, you will see in which documents the serial number has been used." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:104 +msgid "To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:140 -msgid "And, if you want to locate a serial number, you can do so by clicking on the *Location* button available on the serial number form." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:107 +msgid "On this :abbr:`RFQ (request for quotation)` form, fill out the necessary information, by adding a :guilabel:`Vendor`, and by adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product`, under the :guilabel:`Products` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:111 +msgid "Choose the desired quantity of the product to order, by changing the number in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:114 +msgid "When the necessary configurations are complete, click :guilabel:`Confirm Order`. This will convert the :abbr:`RFQ (request for quotation)` to a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:117 +msgid "Then, click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form page for that specific :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:121 +msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities will cause a :guilabel:`User Error` pop-up to appear. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a serial number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "User error popup prompting serial number entry." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:134 +msgid "In this pop-up, configure a number of different fields, including the assignation of a serial number (or serial numbers) under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:138 +msgid "There are three ways to do this: manually assigning serial numbers, automatically assigning serial numbers, and copy/pasting serial numbers from a spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:142 +msgid "Assign serial numbers manually" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:144 +msgid "To assign serial numbers manually, click :guilabel:`Add a line` from the :guilabel:`Detailed Operations` pop-up, and first choose the location where the product will be stored under the :guilabel:`To` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:148 +msgid "Then, type a new :guilabel:`Serial Number Name`, and set the :guilabel:`Done` quantity in the appropriate columns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:151 +msgid "Repeat this process for the quantity of products shown in the :guilabel:`Demand` field, and until the :guilabel:`Quantity Done` field displays the correct (matching) number of products processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:155 +msgid "Assign serial numbers automatically" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:157 +msgid "If a large quantity of products need individual serial numbers assigned to them, Odoo can automatically generate and assign serial numbers to each of the individual products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:160 +msgid "To accomplish this, start with the :guilabel:`First SN` field in the :guilabel:`Detailed Operations` pop-up window, and type the first serial number in the desired order to be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:163 +msgid "Then, in the :guilabel:`Number of SN` field, type the total number of items that need newly-generated unique serial numbers assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:166 +msgid "Finally, click :guilabel:`Assign Serial Numbers`, and a list will populate with new serial numbers matching the ordered quantity of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "Automatic serial number assignment in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:174 +msgid "Copy/paste serial numbers from a spreadsheet" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:176 +msgid "To copy and paste serial numbers from an existing spreadsheet, first populate a spreadsheet with all of the serial numbers received from the supplier (or manually chosen upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:181 +msgid "From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the serial number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "List of serial numbers copied in Excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:189 +msgid "For purchase orders that include large quantities of products to receive, the best method of serial number assignment is to automatically assign serial numbers using the :guilabel:`Assign Serial Numbers` button located on the :abbr:`PO (purchase order)`. This prevents any serial numbers from being reused or duplicated, and improves traceability reporting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:194 +msgid "Once all product quantities have been assigned a serial number, click the :guilabel:`Confirm` button to close the pop-up. Then, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:197 +msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:202 +msgid "Once all product quantities have been assigned a serial number, click :guilabel:`Confirm` to close the popup, and click :guilabel:`Validate`. A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:209 +msgid "Manage serial numbers on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:211 +msgid "Assigning serial numbers to **outgoing** goods can be done directly from the sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:213 +msgid "To create an :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing so reveals a new, blank quotation form. On this blank quotation form, fill out the necessary information, by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab), by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:221 +msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, the quotation becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:232 +msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with each product of the total :guilabel:`Reserved` quantity listed with their unique serial numbers (most likely listed in sequential order)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:236 +msgid "To manually change a product's serial number, click the drop-down menu under :guilabel:`Lot/Serial Number`, and choose (or type) the desired serial number. Then, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:240 +msgid "Finally, click the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "Serial numbers listed in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:246 +msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:251 +msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order (PO), if any of the product quantities shared a serial number assigned during receipt of that specific :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:256 +msgid "Manage serial numbers for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:258 +msgid "By default in Odoo, the creation of new serial numbers is only allowed upon **receiving** products from a purchase order. **Existing** serial numbers cannot be used. For sales orders, the opposite is true: new serial numbers cannot be created on the delivery order, only existing serial numbers can be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:263 +msgid "To change the ability to use new (or existing) serial numbers on any operation type, go to :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:267 +msgid "For the :guilabel:`Receipts` operation type, found on the :guilabel:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Receipts` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:273 +msgid "For the :guilabel:`Delivery Orders` operation type, located on the :guilabel:`Operations Types` page, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Delivery Orders` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Be sure to click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "Enabled traceability setting in operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:284 +msgid "Serial number traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:286 +msgid "Manufacturers and companies can refer to the traceability reports to see the entire lifecycle of a product: where it came from (and when), where it was stored, and who it went to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:289 +msgid "To see the full traceability of a product, or group by serial numbers, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:293 +msgid "From here, products with serial numbers assigned to them will be listed by default, and can be expanded to show what serial numbers have been specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:296 +msgid "To group by serial numbers (or lots), first remove any default filters from the search bar in the upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:301 +msgid "Doing so reveals all existing serial numbers and lots, and can be expanded to show all quantities of products with that assigned number. For unique serial numbers that are not reused, there should be just one product per serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 +msgid "Serial numbers reporting page with drop-down lists." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:310 +msgid "For additional information regarding an individual serial number (or lot number), click the line item for the serial number to reveal that specific serial number's :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number, and any operations made using that serial number." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/misc.rst:5 @@ -1430,7 +1391,7 @@ msgstr "" msgid "To activate the batch picking option, go to :menuselection:`Inventory --> Configuration --> Configuration` and enable *Batch Pickings*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of the inventory settings. Process to enable the batch pickings option in the Odoo Inventory app" msgstr "" @@ -1438,7 +1399,7 @@ msgstr "" msgid "Then, go to :menuselection:`Inventory --> Operations --> Batch Transfers` and hit the create button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of the new menu, Batch Transfers, under operations" msgstr "" @@ -1446,7 +1407,7 @@ msgstr "" msgid "Now, determine the batch transfer responsible and the type of transfers you want to include in the batch. To add the types of transfers, click on *Add a line*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of a Batch Transfers form" msgstr "" @@ -1454,7 +1415,7 @@ msgstr "" msgid "In the example below, a filter was applied to only see the transfers that are in the *Pick* step. After that, the different transfers that needed to be included in the batch transfer were selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of the list of transfers to choose for a single batch transfer and how to add them\n" "to the batch transfer" msgstr "" @@ -1463,7 +1424,7 @@ msgstr "" msgid "To see the products to pick for the different transfers, click on *Select*. If *Multi-locations* has been activated, the document also shows the locations they have been reserved from." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of a batch transfer list. Products to pick with their source and target locations" msgstr "" @@ -1475,7 +1436,7 @@ msgstr "" msgid "From the *Transfers List View*, select transfers that should be included in the Batch. Then, select *Add to batch* from the *Action* list." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of the process to add transfers to a batch transfer from the transfers list view" msgstr "" @@ -1483,7 +1444,7 @@ msgstr "" msgid "Next, determine if you want to add the transfers to an existing draft batch transfer or create a new one." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "Option to add a responsible to a batch transfer so it can be confirmed" msgstr "" @@ -1495,7 +1456,7 @@ msgstr "" msgid "While gathering the products, you can edit the batch transfer and update the *Quantity done* for each product. Once everything has been picked, select *Validate* so the different transfers contained in the batch are validated too." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of an in progress batch transfer" msgstr "" @@ -1503,12 +1464,12 @@ msgstr "" msgid "In case all the products cannot be picked, you can create backorders for each individual transfer which couldn’t be completely processed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "How to handle batch transfers with unavailable products. Creation of a backorder inside\n" "of a batch transfer" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of how backorders are handled in Odoo's batch transfers" msgstr "" @@ -1520,7 +1481,7 @@ msgstr "" msgid "Enter the *Barcode* application, select the *Batch Transfers* menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of the Odoo Barcode app dashboard" msgstr "" @@ -1528,7 +1489,7 @@ msgstr "" msgid "Then, you can enter the batch transfer on which you want to work. Batch transfers can easily be grouped per responsible if necessary." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of the batch transfers dashboard inside of the Barcode app" msgstr "" @@ -1536,7 +1497,7 @@ msgstr "" msgid "In the batch transfer, products are classified per location. The source document is visible on each line and a color-code helps differentiate them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of an in progress batch transfer with the Odoo Barcode application" msgstr "" @@ -1544,7 +1505,7 @@ msgstr "" msgid "To see the products to pick from another location, click on the *Next* button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 msgid "View of a ready and completed batch transfer inside of the Odoo Barcode application" msgstr "" @@ -1553,39 +1514,127 @@ msgid "Once all the products have been picked, click on *Validate* (on the last msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:3 -msgid "Manage Stock that you don't own" +msgid "Consignment: buy and sell stock without owning it" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:5 -msgid "Sometimes, suppliers can offer you to store and sell products without having to buy those items. This technique is called *consignee stock*." +msgid "Most of the time, products stored in a company's warehouse are either purchased from suppliers, or are manufactured in-house. However, suppliers will sometimes let companies store and sell products in the company's warehouse, without having to buy those items up-front. This is called *consignment*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:8 -msgid "Consignee stock is a great way for manufacturers and suppliers to launch new products. As resellers may be reluctant to buy a product they are not sure to be able to sell, consignee stock will allow them to offer an item to check its market without having to pay for it in the first place." +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:10 +msgid "Consignment is a useful method for suppliers to launch new products, and easily deliver to their customers. It's also a great way for the company storing the products (the consignee) to earn something back for their efforts. Consignees can even charge a fee for the convenience of storing products they don't actually own." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:14 -msgid "Of course, Odoo has the ability to manage those consignee stocks through advanced settings." +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:16 +msgid "Enable the consignment setting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:20 -msgid "To use this feature, go to :menuselection:`Inventory --> Configuration --> Settings` in the inventory app. Then, enable the *Consignment* feature in the *Traceability* section. Now, hit save." +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:18 +msgid "To receive, store, and sell consignment stock, the feature needs to be enabled in the settings. To do this, go to :menuselection:`Inventory --> Configuration --> Settings`, and under the :guilabel:`Traceability` section, check the box next to :guilabel:`Consignment`, and then click :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1 +msgid "Enabled Consignment setting in Inventory configuration." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:28 -msgid "Reception of Consignee Stock" +msgid "Receive (and store) consignment stock" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:30 -msgid "When in the *Inventory* app, open the receipts and create a new reception. On the right side, you will see that a new line called *Assign Owner* has appeared. There, you can specify the partner which owns the stock." +msgid "With the feature enabled in Odoo, consignment stock can now be received into a warehouse. From the main :menuselection:`Inventory` dashboard, click into the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:35 +msgid "Consignment stock is not actually purchased from the vendor; it is simply received and stored. Because of this, there are no quotations or purchase orders involved in receiving consignment stock. So, *every* receipt of consignment stock will start by creating manual receipts." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:39 -msgid "If you are the owner, you can leave the field blank." +msgid "Choose a vendor to enter in the :guilabel:`Receive From` field, and then choose the same vendor to enter in the :guilabel:`Assign Owner` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:41 -msgid "Once the receipt is validated, the products enter your stock but still belong to the owner. They don’t impact your inventory valuation." +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:43 +msgid "Since the products received from the vendor will be owned by the same vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields must match." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:46 +msgid "Once the vendor-related fields are set, enter products into the :guilabel:`Product` lines, and set the quantities to be received into the warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be changed, as well. Once all the consignment stock has been received, :guilabel:`Validate` the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1 +msgid "Matching vendor fields in consignment Receipt creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:56 +msgid "Sell and deliver consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:58 +msgid "Once consignment stock has been received into the warehouse, it can be sold the same as any other in-stock product that has the :guilabel:`Can Be Sold` option enabled on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:61 +msgid "To create a sales order, navigate to the :menuselection:`Sales` app, and from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, choose a customer to enter into the :guilabel:`Customer` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:66 +msgid "The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` that supplied the consignment stock received (and stored) in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:69 +msgid "Add the consignment product under the :guilabel:`Product` column in the order lines, set the :guilabel:`Quantity`, and fill out any other pertinent product details on the form. Once the quotation is complete, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1 +msgid "Sales order of consignment stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:77 +msgid "Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will become a sales order. From here, the products can be delivered by clicking on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate` to validate the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:82 +msgid "Traceability and reporting of consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:84 +msgid "Although consignment stock is owned by the vendor who supplied it, and not by the company storing it in their warehouse, consignment products will *still* appear in certain inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:87 +msgid "To find inventory reports, go to :menuselection:`Inventory --> Reporting`, and choose a report to view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:91 +msgid "Since the consignee does not actually own consigment stock, these products are *not* reflected in the :guilabel:`Stock Valuation` report, and have no impact on the consignee's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:96 +msgid "Product moves report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:98 +msgid "To view all information about on-hand stock moves, navigate to the the :guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory --> Reporting --> Product Moves`. For consignment products, the information in this report is the same as any other product: the history of its product moves can be reviewed; the :guilabel:`Quantity Done` and :guilabel:`Reference` document are available; and its :guilabel:`Locations` are available, as well. The consignment stock will originate from :guilabel:`Partner Location/Vendors`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:106 +msgid "To view a consignment product's moves by ownership, select the :guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1 +msgid "Consignment stock moves history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:115 +msgid "To see forecasted units of consignment stock, go to :menuselection:`Inventory --> Reporting --> Forecasted Inventory`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:119 +msgid "Stock on hand report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:121 +msgid "View the :guilabel:`Stock On Hand` dashboard by navigating to :menuselection:`Inventory --> Reporting --> Inventory Report`. From this report, the :guilabel:`Locations` of all stock on-hand are displayed, in addition to the quantities per location. For consigment products, the :guilabel:`Owner` column will be populated with the owner of those products, or the original vendor who supplied the products in the first place." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning.rst:5 @@ -1652,7 +1701,7 @@ msgstr "" msgid "In the *Sales* app, there is an option called *Delivery Date*. It allows seeing an additional field on the sales orders, *Expected Date*. This one is automatically computed based on the different lead times previously configured." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the delivery settings to have the delivery lead time taken into account" msgstr "" @@ -1660,7 +1709,7 @@ msgstr "" msgid "If the set up *Delivery Date* is earlier than the the *Expected Date*, a warning message is displayed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the error that occurs when trying to choose an earlier date than what calculated\n" "by Odoo" msgstr "" @@ -1677,7 +1726,7 @@ msgstr "" msgid "The *Customer Lead Time* is the time needed for your product to go from your warehouse to the customer place. It can be configured on any product by going to :menuselection:`Sales --> Products --> Products`. There, open your product form, go in the inventory tab, and add your *Customer Lead Time*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the customer lead time configuration from the product form" msgstr "" @@ -1703,7 +1752,7 @@ msgstr "" msgid "To set this up, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature *Security Lead Time for Sales*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the security lead time for sales configuration from the sales settings" msgstr "" @@ -1743,7 +1792,7 @@ msgstr "" msgid "The *Supplier Lead Time* is the time needed for a product you purchased to be delivered. To configure it, open a product from :menuselection:`Purchase --> Products --> Products` and add a vendor under the *Purchase* tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the way to add vendors to products" msgstr "" @@ -1751,7 +1800,7 @@ msgstr "" msgid "By clicking on *Add a line*, a new window is displayed. You can specify the *Delivery Lead Time* there. If done so, the delivery day for every purchase of that product is now equal to *Date of the Purchase Order + Delivery Lead Time*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the delivery lead time configuration from a vendor form" msgstr "" @@ -1767,7 +1816,7 @@ msgstr "" msgid "To set up *Security Lead Time* for purchase, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the security lead time for purchase from the inventory settings" msgstr "" @@ -1787,7 +1836,7 @@ msgstr "" msgid "The *Manufacturing Lead Time* is the time needed to manufacture the product. To specify it, open the *Inventory* tab of your product form and add the number of days the manufacturing takes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the manufacturing lead time configuration from the product form" msgstr "" @@ -1803,7 +1852,7 @@ msgstr "" msgid "To enable it, go to :menuselection:`Manufacturing --> Configuration --> Settings` and tick *Security Lead Time*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 msgid "View of the security lead time for manufacturing from the manufacturing app settings" msgstr "" @@ -1868,69 +1917,517 @@ msgstr "" msgid "Products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:3 -msgid "How to select the right replenishment strategy" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:3 +msgid "Replenish on order (MTO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:5 -msgid "Minimum Stock rules and Make to Order have similar consequences but different rules. They should be used depending on your manufacturing and delivery strategies." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:9 +msgid "*Replenish on order*, also known as *MTO* (make to order), is a replenishment strategy that creates a draft order for a product every time a sales order is created for it. For products that are purchased from a vendor, a request for quotation (RFQ) is created, while a sales order for a product manufactured in-house triggers the creation of a manufacturing order. The creation of a |RFQ| or manufacturing order occurs every time a sales order is created, regardless of the current stock level of the product being ordered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:17 +msgid "Unarchive the Replenish on Order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:19 +msgid "By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| is a somewhat niche workflow that is only used by certain companies. However, it is easy to unarchive the route in just a few simple steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:23 +msgid "To do so, begin by navigating to :menuselection:`Inventory --> Configuration --> Routes`. On the :guilabel:`Routes` page, click the :guilabel:`Filters` button and select the :guilabel:`Archived` option. This shows all routes that are currently archived." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +msgid "The archived filter on the Routes page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:31 +msgid "Enable the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click the :guilabel:`Action` button to reveal a drop-down menu. From the drop-down menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +msgid "The unarchive action on the Routes page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:38 +msgid "Finally, remove the :guilabel:`Archived` filter from the :guilabel:`Search...` bar. The :guilabel:`Routes` page will now show all available routes, including :guilabel:`Replenish on Order (MTO)`, which is now selectable on the inventory tab of each product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +msgid "The MTO route appears on the Routes page after unarchiving it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:47 +msgid "Configure a product to use the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:49 +msgid "With the |MTO| route unarchived, products can now be properly configured to use replenish on order. To do so, begin by going to :menuselection:`Inventory --> Products --> Products`, then select an existing product, or click :guilabel:`Create` to configure a new one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:53 +msgid "On the product page, select the :guilabel:`Inventory` tab and enable the :guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` section, along with one other route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:57 +msgid "The :guilabel:`Replenish on Order (MTO)` route **does not** work unless another route is selected as well. This is because Odoo needs to know how to replenish the product when an order is placed for it (buy it, manufacture it, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +msgid "Select the MTO route and a second route on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:65 +msgid "If the product is purchased from a vendor to fulfill sales orders, enable the :guilabel:`Can be Purchased` checkbox under the product name. Doing so makes the :guilabel:`Purchase` tab appear alongside the other settings tabs below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:69 +msgid "Select the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the :guilabel:`Price` they sell the product for." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +msgid "Enable \"Can be Purchased\" and specify a vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:76 +msgid "If the product is manufactured, make sure that it has a bill of materials (BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` smart button at the top of the screen, then click :guilabel:`Create` on the :guilabel:`Bill of Materials` page to configure a new |BOM| for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:81 +msgid "On the blank |BOM| form, add the components used to manufacture the product on the :guilabel:`Components` tab, along with the operations required for the manufacturing workflow on the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:85 +msgid "Finally, click :guilabel:`Save` to save the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:88 +msgid "Fulfill a sales order using the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:90 +msgid "After configuring a product to use the |MTO| route, a replenishment order is created for it every time a sales order including the product is confirmed. The type of order created depends on the second route selected in addition to |MTO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:94 +msgid "For example, if *Buy* was the second route selected, then a purchase order is created upon confirmation of a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:98 +msgid "When the |MTO| route is enabled for a product, a replenishment order is always created upon confirmation of a sales order. This is the case even if there is enough stock of the product on-hand to fulfill the sales order, without buying or manufacturing additional units of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:102 +msgid "While the |MTO| route can be used in unison with a variety of other routes, the *Buy* route is used as the example for this workflow. Begin by navigating to the :menuselection:`Sales` app, then click :guilabel:`Create`, which opens a blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:106 +msgid "On the blank quotation form, add a :guilabel:`Customer`, then click :guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a product that has been configured to use the *MTO* and *Buy* routes. Click :guilabel:`Confirm` and the quotation is turned into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:110 +msgid "A :guilabel:`Purchase` smart button now appears in the top-right corner of the sales order. Clicking it opens the |RFQ| associated with the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:113 +msgid "Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a purchase order. A green :guilabel:`Receive Products` button now appears at the top of the purchase order. Once the products are received, click :guilabel:`Receive Products` to register them into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:117 +msgid "Return to the sales order by clicking the :guilabel:`SO` breadcrumb, or by navigating to :menuselection:`Sales --> Orders --> Orders`, and selecting the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:120 +msgid "Finally, click the :guilabel:`Delivery` smart button in the top-right of the order to be taken to the delivery order. Once the products have been shipped to the customer, click :guilabel:`Validate` to confirm the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:3 +msgid "Reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:5 +msgid "Reordering rules are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:9 +msgid "Reordering rules can be configured for each product based on the route used to replenish it. If a product uses the *Buy* route, then a Request for Quotation (RFQ) is created when the reordering rule is triggered. If a product uses the *Manufacture* route, then a Manufacturing Order (MO) is created instead. This is the case regardless of the selected replenishment route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:15 +msgid "Configure products for reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:17 +msgid "In order to use reordering rules for a product, it must first be correctly configured. Begin by navigating to :guilabel:`Inventory --> Products --> Products`, then select an existing product, or create a new one by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:21 +msgid "First, on the :guilabel:`General Information` tab, make sure that the :guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is necessary because Odoo only tracks stock quantities for storable products, and this number is used to trigger reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +msgid "Set the Product Type as Storable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:29 +msgid "Next, click on the :guilabel:`Inventory` tab and select one or more routes from the :guilabel:`Routes` section. Doing so tells Odoo which route to use to replenish the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +msgid "Select one or more routes on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:36 +msgid "If the product is reordered using the :guilabel:`Buy` route, confirm that the :guilabel:`Can be Purchased` checkbox is enabled under the product name. This makes the :guilabel:`Purchase` tab appear. Click on the :guilabel:`Purchase` tab, and specify at least one vendor, and the price that they sell the product for, so that Odoo knows which company the product should be purchased from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +msgid "Specify a vendor and price on the Purchase tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:45 +msgid "If the product is replenished using the :guilabel:`Manufacture` route, it needs to have at least one Bill of Materials (BoM) associated with it. This is necessary because Odoo only creates manufacturing orders for products with a :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:49 +msgid "If a :abbr:`BoM (Bill of Materials)` does not already exist for the product, select the :guilabel:`Bill of Materials` smart button at the top of the product form, then click :guilabel:`Create` to configure a new :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +msgid "The Bill of Materials smart button on a product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:58 +msgid "Create new reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:60 +msgid "To create a new reordering rule, navigate to :menuselection:`Inventory --> Configuration --> Reordering Rules`, then click :guilabel:`Create`, and fill out the new line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:63 +msgid ":guilabel:`Product`: The product that is replenished by the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:64 +msgid ":guilabel:`Location`: The location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:65 +msgid ":guilabel:`Min Quantity`: The minimum quantity that can be forecasted without the rule being triggered. When forecasted stock falls below this number, a replenishment order for the product is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:68 +msgid ":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:69 +msgid ":guilabel:`Multiple Quantity`: Specify if the product should be replenished in batches of a certain quantity (e.g., a product could be replenished in batches of 20)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:71 +msgid ":guilabel:`UoM`: The unit of measure used for reordering the product. This value can simply be `Units` or a specific unit of measurement for weight, length, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +msgid "The form for creating a new reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:79 +msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory --> Products --> Products`, then select a product. Click on :menuselection:`Reordering Rules --> Create`, then fill out the new line as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:83 +msgid "Once a reordering rule has been created for a product, if its forecasted quantity is below the rule's minimum quantity when the scheduler runs, a replenishment order for the product is automatically generated. By default, the scheduler runs once each day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:88 +msgid "To manually trigger a reordering rule before the scheduler runs, select :menuselection:`Inventory --> Operations --> Run Scheduler`. Then, select the green :guilabel:`Run Scheduler` button on the pop-up that appears. Be aware that this also triggers any other scheduled actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:92 +msgid "If the :guilabel:`Buy` route is selected, then an :abbr:`RFQ (Request for Quotation)` is generated. To view and manage :abbr:`RFQs (Requests for Quotation)`, navigate to :menuselection:`Purchase --> Orders --> Requests for Quotation`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:96 +msgid "If the :guilabel:`Manufacture` route is selected, then an :abbr:`MO (Manufacturing Order)` is generated. To view and manage :abbr:`MOs (Manufacturing Orders)`, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:101 +msgid "Set a preferred route for reordering" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:103 +msgid "Odoo allows for multiple routes to be selected under the :guilabel:`Inventory` tab on each product form. For instance, it is possible to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling the functionality of both routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:107 +msgid "Odoo also enables users to set a preferred route for a product's reordering rule. This is the route that the rule defaults to if multiple are selected. To select a preferred route, begin by navigating to :menuselection:`Inventory --> Configuration --> Reordering Rules`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:111 +msgid "By default, the :guilabel:`Preferred Route` column is hidden on the :guilabel:`Reordering Rules` page. Enable it by selecting the :guilabel:`⋮ (three-dot)` option button on the right side of the page and checking the :guilabel:`Preferred Route` checkbox. Doing so reveals the :guilabel:`Preferred Route` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:116 +msgid "Click inside of the column on the row of a reordering rule and a drop-down menu shows all available routes for that rule. Select one to set it as the preferred route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +msgid "Select a preferred route from the drop-down." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:124 +msgid "If multiple routes are enabled for a product but no preferred route is set for its reordering rule, the product is reordered using the selected route that is listed first on the :guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:3 +msgid "Selecting a replenishment strategy" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:10 +msgid "In Odoo, there are two strategies for automatically replenishing inventory: *reordering rules* and the *make to order (MTO)* route. Although these strategies differ slightly, they both have similar consequences: triggering the automatic creation of a |PO| or |MO|. The choice of which strategy to use depends on the business's manufacturing and delivery processes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:16 msgid "Terminology" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:13 -msgid "Minimum stock rule" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:54 +msgid "Replenishment report and reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:15 -msgid "Minimum Stock rules are used to ensure that you always have the minimum amount of a product in stock in order to manufacture your products and/or answer to your customer needs. When the stock level of a product reaches its minimum the system will automatically generate a procurement order with the quantity needed to reach the maximum stock level." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:21 +msgid "The replenishment report is a list of all products that have a negative forecast quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:22 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:57 -msgid "Make to Order" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:23 +msgid "*Reordering rules* are used to ensure there's always a minimum amount of a product in-stock, in order to manufacture products and/or fulfill sales orders. When the stock level of a product reaches its minimum, Odoo automatically generates a purchase order with the quantity needed to reach the maximum stock level." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:24 -msgid "The Make to Order function will trigger a Purchase Order of the amount of the Sales Order related to the product. The system will **not** check the current stock. This means that a draft purchase order will be generated regardless of the quantity on hand of the product." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:28 +msgid "Reordering rules can be created and managed in the replenishment report, or from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:31 +msgid "Make to order" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:33 -msgid "Minimum stock rules" +msgid "*Make to order (MTO)* is a procurement route that creates a draft purchase order (or manufacturing order) each time a sales order is confirmed, **regardless of the current stock level**." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:35 -msgid "The Minimum Stock Rules configuration is available through your Inventory module. In the Inventory Control menu select \"Reordering Rule\" in the drop down menu. There, click on \"Create\" to set minimum and maximum stock values for a given product." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:36 +msgid "Unlike products replenished using reordering rules, Odoo automatically links the sales order to the |PO| or |MO| generated by the |MTO| route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:44 -msgid "Show tooltips for \"minimum quantity\", \"maximum quantity\" and \"quantity multiple\" fields" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:39 +msgid "Another difference between reordering rules and |MTO| is, with |MTO|, Odoo generates a draft |PO| or |MO| immediately after the |SO| is confirmed. With reordering rules, Odoo generates a draft |PO| or |MO| when the product's forecasted stock falls below the set minimum quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:43 +msgid "In addition, Odoo automatically adds quantities to the |PO| or |MO| as the forecast changes, so long as the |PO| or |MO| is not confirmed." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:46 -msgid "Then, click on your product to access the related product form and, on the \"Inventory submenu\", do not forget to select a supplier." +msgid "The |MTO| route is the best replenishment strategy for products that are customized, and/or for products that have no stock kept on-hand." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:53 -msgid "Don't forget to select the right product type. A consumable can not be stocked and will thus not be accounted for in the stock valuation." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:56 +msgid "To access the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment.`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:59 -msgid "The Make to Order configuration is available on your product form through your :menuselection:`Inventory --> Inventory control --> Products` (or any other module where products are available)." +msgid "By default, the replenishment report dashboard shows every product that needs to be manually reordered. If there is no specific rule for a product, Odoo assumes the :guilabel:`Min Quantity` and :guilabel:`Max Quantity` stock are both `0.00`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:63 -msgid "On the product form, under Inventory, click on \"Make To Order\"." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:64 +msgid "For products that don't have a set reordering rule, Odoo calculates the forecast based on confirmed sales orders, deliveries, and receipts. For products that have a set reordering rule, Odoo calculates the forecast normally, but also takes into account the purchase/manufacturing lead time and security lead time." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:69 -msgid "Choice between the two options" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:70 +msgid "Before creating a new reordering rule, make sure the product has a *vendor* or a *bill of materials* configured on the product form. To check this, go to :menuselection:`Inventory app --> Products --> Products`, and select the product to open its product form. The vendor, if configured, is listed in the :guilabel:`Purchase` tab, and the bill on materials, if configured, is found in the :guilabel:`Bill of Materials` smart button at the top of the form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:71 -msgid "The choice between the two options is thus dependent of your inventory strategy. If you prefer to have a buffer and always have at least a minimum amount, the minimum stock rule should be used. If you want to reorder your stocks only if your sale is confirmed it is better to use the Make to Order." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:76 +msgid "The :guilabel:`Product Type`, located in the :guilabel:`General Information` tab on the product form, **must** be set to :guilabel:`Storable Product`. By definition, a consumable product does not have its inventory levels tracked, so Odoo cannot account for a consumable product in the replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 +msgid "Replenishment report listing all items needing to be purchased to meet current needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:85 +msgid "To create a new reordering rule from the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment`, click :guilabel:`Create`, and select the desired product from the drop-down menu in the :guilabel:`Product` column. If necessary, a :guilabel:`Min Quantity` and a :guilabel:`Max Quantity` can be configured in the corresponding columns on the :guilabel:`Replenishment` report page, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:91 +msgid "To create a new reordering rule from the product form, go to :menuselection:`Inventory app --> Products --> Products`, and select a product to open its product form. Click the :guilabel:`Reordering Rules` smart button, click :guilabel:`Create`, and fill out the fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:96 +msgid "Replenishment report fields" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:98 +msgid "The following fields are on the :guilabel:`Replenishment` report. If any of these fields are not visible, click the :guilabel:`⋮ (additional options)` icon on the far right side of the report, then click the checkbox next to a field to make it visible." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:102 +msgid ":guilabel:`Product`: the product that requires a replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:103 +msgid ":guilabel:`Location`: the specific location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:104 +msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:105 +msgid ":guilabel:`On Hand`: the amount of product currently available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:106 +msgid ":guilabel:`Forecast`: the amount of product available after all current orders (sales, manufacturing, purchase, etc.) are taken into account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:108 +msgid ":guilabel:`Preferred Route`: how the product is procured, either :guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:110 +msgid ":guilabel:`Vendor`: the company from which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:111 +msgid ":guilabel:`Bill of Materials`: the bill of materials for the product (if one is configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:112 +msgid ":guilabel:`Trigger`: how the replenishment is created, either :guilabel:`Auto` (automatically, once the :guilabel:`On Hand` quantity goes below the :guilabel:`Min Quantity`) or :guilabel:`Manual` (only when the replenishment is requested)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:115 +msgid ":guilabel:`Procurement Group`: the reference number for how the product is being acquired, such as a sales order, purchase order, or manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:117 +msgid ":guilabel:`Min Quantity`: the minimum amount of product that should be available. When inventory levels goes below this number, the replenishment is triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:119 +msgid ":guilabel:`Max Quantity`: the amount of product that should be available after replenishing the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:121 +msgid ":guilabel:`Multiple Quantity`: if the product should be ordered in specific quantities, enter the number that should be ordered. For example, if the :guilabel:`Multiple Quantity` is set to `5`, and only 3 are needed, 5 products are replenished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:124 +msgid ":guilabel:`To Order`: the amount of product that is currently needed, and will be ordered, if the :guilabel:`Order Once` or :guilabel:`Automate Orders` button is clicked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:126 +msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:127 +msgid ":guilabel:`Company`: the company for which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:129 +msgid "By default, the quantity in the :guilabel:`To Order` field is the quantity required to reach the set :guilabel:`Max Quantity`. However, the :guilabel:`To Order` quantity can be adjusted by clicking on the field and, changing the value, and clicking :guilabel:`Save`. To replenish a product manually, click :guilabel:`Order Once`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:134 +msgid "To automate a replenishment from the :guilabel:`Replenishment` page, click :guilabel:`Automate Orders` on the right-side of the line, represented by a :guilabel:`🔄 (circular arrow)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:137 +msgid "When this button is clicked, Odoo will automatically generate a draft |PO|/|MO| every time the forecasted stock level falls below the set :guilabel:`Min Quantity` of the reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:140 +msgid "On the :guilabel:`Replenishment` page, a reordering rule or manual replenishment can be temporarily deactivated for a given period, by clicking the :guilabel:`🔕 (snooze)` icon on the far-right of the line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 +msgid "Snooze options to turn off notifications for reordering for a period of time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:148 +msgid "A |PO| or |MO| created by a manual replenishment has a :guilabel:`Replenishment Report` as the source document. A |PO| or |MO| created by an automated reordering rule has the |SO| reference number(s) that triggered the rule as the source document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 +msgid "Quote request list shows which quotes are directly from the replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:157 +msgid "Make to order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:159 +msgid "Since the |MTO| route is recommended for customized products, the route is hidden by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:168 +msgid "To activate the |MTO| route in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:162 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:163 +msgid "Activate the :guilabel:`Multi-Step Routes` setting, located under the :guilabel:`Warehouse` section, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:165 +msgid "Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:166 +msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:167 +msgid "Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click on :menuselection:`Action --> Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:171 +msgid "Activating the :guilabel:`Multi-Step Routes` setting also activates :guilabel:`Storage Locations`. If these features aren't applicable to the warehouse, disable these settings after unarchiving the |MTO| route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:175 +msgid "To set a product's procurement route to |MTO|, go to :menuselection:`Inventory app --> Products --> Products`, click on the desired product to open its product form, and click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:178 +msgid "Then, click the :guilabel:`Inventory` tab, and in the :guilabel:`Routes` section of options, select :guilabel:`Replenish on Order (MTO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:181 +msgid "For products purchased directly from a vendor, make sure the :guilabel:`Buy` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a vendor is configured in the :guilabel:`Purchase` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:185 +msgid "For products manufactured in-house, make sure the :guilabel:`Manufacture` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a bill of materials is configured for the product, which is accessible via the :guilabel:`Bill of Materials` smart button on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:190 +msgid "Finally, when all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:193 +msgid "The |MTO| route cannot be selected alone. |MTO| **only** works if the :guilabel:`Manufacture` or :guilabel:`Buy` route is also selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 +msgid "Replenish on Order selected on the product form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:3 @@ -2057,38 +2554,6 @@ msgstr "" msgid "Another useful use of the packaging is for product reception. By scanning the barcode of the packaging, Odoo adds the number of units contained in the packing on the picking." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies.rst:5 -msgid "Inventory Adjustment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:3 -msgid "Resupply from another Warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:8 -msgid "In order to be able to resupply from another warehouse, you need to activate \\*multi-step routes\\*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:None -msgid "Enable Multi-Step Routes in an Odoo database's settings" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:15 -msgid "You can then access your warehouses via :menuselection:`Inventory --> Configuration --> Warehouses`. Enter the warehouse which should be resupplied by another one. You will have the possibility to directly indicate through which warehouse it gets resupplied." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:24 -msgid "By activating this option, a new route will now be available on your products \\*Supply Product from Second warehouse\\*. It can now be selected, along with either a \\*reordering rule\\* or a \\*make to order\\*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:32 -msgid "For the demonstration, I set a reordering rule with a minimum of 5 units in stock and a maximum of 10 units in stock, having currently 0 units on hand. I will run the scheduler by going to :menuselection:`Inventory --> Operations --> Run scheduler`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:40 -msgid "The system automatically creates two pickings, one \\*delivery order\\* from my Second Warehouse which contains the necessary products, and a receipt in my main warehouse WH/Stock for the same products. The source document is the \\*reordering rule\\* which triggered the route \\*Supply Product from Second warehouse\\*." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/management/reporting.rst:5 msgid "Valuation Methods" msgstr "" @@ -2146,205 +2611,1116 @@ msgid "You are not forced to start from the vendor bill, you can also go in :men msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:3 -msgid "Inventory Valuation Configuration" +msgid "Inventory valuation configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:7 msgid "All of a company's stock on-hand contributes to the valuation of its inventory. That value should be reflected in the company's accounting records to accurately show the value of the company and all of its assets." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:11 msgid "By default, Odoo uses a periodic inventory valuation (also known as manual inventory valuation). This method implies that the accounting team posts journal entries based on the physical inventory of the company, and that warehouse employees take the time to count the stock. In Odoo, this method is reflected inside each product category, where the :guilabel:`Costing Method` field will be set to `Standard Price` by default, and the :guilabel:`Inventory Valuation` field will be set to `Manual`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:-1 msgid "The Inventory Valuation fields are located on the Product Categories form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:22 msgid "Alternatively, automated inventory valuation is an integrated valuation method that updates the inventory value in real-time by creating journal entries whenever there are stock moves initiated between locations in a company's inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:27 msgid "Automated inventory valuation is a method recommended for expert accountants, given the extra steps involved in journal entry configuration. Even after the initial setup, the method will need to be periodically checked to ensure accuracy, and adjustments may be needed on an ongoing basis depending on the needs and priorities of the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:31 -msgid "Types of Accounting" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:33 -msgid "Accounting entries will depend on the accounting mode: Continental or Anglo-Saxon." +msgid "Types of accounting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:35 +msgid "Accounting entries will depend on the accounting mode: *Continental* or *Anglo-Saxon*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:38 msgid "Verify the accounting mode by activating the :ref:`developer-mode` and navigating to :menuselection:`Accounting --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:39 -msgid "In Anglo-Saxon accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. Interim Stock Accounts are used for the input and output accounts, and are both Asset Accounts in the Balance Sheet." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:41 +msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. *Interim Stock Accounts* are used for the input and output accounts, and are both *Asset Accounts* in the balance sheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:44 -msgid "In Continental accounting, the cost of a good is reported as soon as a product is received into stock. Additionally, a *single* Expense account is used for both input and output accounts in the Balance Sheet." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:49 -msgid "Costing Methods" +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:46 +msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Additionally, a single *Expense* account is used for both input and output accounts in the balance sheet." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:51 -msgid "Below are the three costing methods that can be used in Odoo for inventory valuation." +msgid "Costing methods" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:53 -msgid "**Standard Price**: is the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a Purchase Order differs, the valuation will still use the cost defined on the product form." +msgid "Below are the three costing methods that can be used in Odoo for inventory valuation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:55 +msgid "**Standard Price**: is the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:59 msgid "**Average Cost (AVCO)**: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:62 msgid "**First In First Out (FIFO)**: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it's highly sensitive to input data and human error." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:70 msgid "Changing the costing method greatly impacts inventory valuation. It's highly recommended to consult an accountant first before making any adjustments here." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:74 msgid "Configure automated inventory valuation in Odoo" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:76 msgid "Make changes to inventory valuation options by navigating to :menuselection:`Inventory --> Configuration --> Product Categories`, and choose the category/categories where the automated valuation method should apply." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:81 msgid "It is possible to use different valuation settings for different product categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:81 -msgid "Under the :guilabel:`Inventory Valuation` heading are two labels: :guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the desired :guilabel:`Costing Method` using the drop-down menu (e.g. :guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First In First Out (FIFO)` and switch the :guilabel:`Inventory Valuation` to :guilabel:`Automated`." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:83 +msgid "Under the :guilabel:`Inventory Valuation` heading are two labels: :guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the desired :guilabel:`Costing Method` using the drop-down menu (e.g. :guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to :guilabel:`Automated`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:87 -msgid ":doc:`Using the inventory valuation `" +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:89 +msgid ":doc:`Using the inventory valuation `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:90 -msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, the numerical value in the :guilabel:`Cost` field for products in the respective product category will no longer be editable, and will appear grayed out. The :guilabel:`Cost` amount will instead automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:93 +msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the :guilabel:`Cost` field for products in the respective product category creates a new record in the *Inventory Valuation* report to adjust the value of the product. The :guilabel:`Cost` amount will then automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:99 +msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:105 msgid "On the same screen, the :guilabel:`Account Stock Properties` fields will appear, as they are now required fields given the change to automated inventory valuation. These accounts are defined as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:109 msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:111 msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:115 msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:121 msgid "Access reporting data generated by inventory valuation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:123 msgid "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:128 msgid "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:132 msgid "Access more specific information with the :guilabel:`Stock Valuation Account` drop-down menu, by selecting either the :guilabel:`General Ledger` to see an itemized view of all of the journal entries, or by selecting :guilabel:`Journal Items` to review all of the individualized journal entries that were submitted to the account. As well, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:-1 msgid "See the full inventory valuation breakdown in Odoo Accounting app." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:3 -msgid "Using the inventory valuation" +msgid "Using inventory valuation" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:5 -msgid "Inventory valuation refers to how you value your stock. It’s a very important aspect of a business as the inventory can be the biggest asset of a company." +msgid "*Inventory valuation* is a quintessential accounting procedure that calculates the value of on-hand stock. Once determined, the inventory valuation amount is then incorporated into a company's overall value." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:9 -msgid "In this documentation, we will explain how the inventory valuation works in Odoo." +msgid "In Odoo, this process can be conducted manually— by warehouse employees physically counting the products— or automatically through the database." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:13 -msgid "Inventory valuation: the basics" +msgid ":ref:`Inventory valuation configuration `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:16 -msgid "Receive a product" +msgid "Understand the basics of inventory valuation" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:18 -msgid "Each time a product enters or leaves your stock, the value of your inventory is impacted. The way it is impacted depends on the configuration of your product (more info here)." +msgid "In order to understand how moving products in and out of stock affects the company's overall value, consider the following product and stock moves scenario below." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:22 -msgid "Let’s take an example with a product - a table - configured with a *FIFO costing method* and an automated inventory valuation." +msgid "Receive a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:25 -msgid "I purchase 10 tables at a cost of $10." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:24 +msgid "For example, consider an physical product, a simple *table*, which is categorized as `Office Furniture` in the product form's :guilabel:`Product Category` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:30 -msgid "When I’ll confirm the receipt of the products, the value of my inventory will be impacted. If I want to know what this impact is, I can click on the valuation stat button." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:27 +msgid "Navigate to the the product category itself by going to :menuselection:`Inventory app --> Configuration --> Product Categories`, and on the form, set the :guilabel:`Costing Method` as `First In First Out (FIFO)` and the :guilabel:`Inventory Valuation` field as `Automated`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:35 -msgid "The consignment feature allows you to set owners on your stock (discover more about the consignment feature). When you receive products that are owned by another company, they are not taken into account in your inventory valuation." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:32 +msgid "Alternatively access the :guilabel:`Product Categories` dashboard by clicking on the :guilabel:`internal link` arrow on the individual product's form, by hovering over the :guilabel:`Product Category` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:44 -msgid "You need access rights on the accounting module to see that button." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:36 +msgid "Next, assume 10 tables are purchased at a price of $10.00, each. The :abbr:`PO (Purchase Order)` for those tables will show the subtotal of the purchase as $100, plus any additional costs or taxes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:46 -msgid "In this case, I can see that the 10 tables entered the stock for a total value of $100." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 +msgid "Purchase order with 10 tables products valued at $10 each." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:52 -msgid "I can also easily access the accounting entry that has been generated (in case of automated inventory valuation)." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:43 +msgid "After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, use the :guilabel:`Valuation` smart button to view how the value of inventory was impacted." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 +msgid "Valuation smart button on a receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:51 +msgid ":ref:`Developer mode ` must be turned on to see the *Valuation* smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:54 +msgid "The :doc:`consignment ` feature allows ownership to items in stock. Thus, products owned by other companies are not accounted for in the host company's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:58 +msgid "The :guilabel:`Stock Valuation` dashboard then displays valuation of all products in the shipment, along with their quantities and valuation. In the example of 10 tables being purchased, the :guilabel:`Total Value` column of the dashboard would display a calculated valuation of $100." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 +msgid "Stock valuation page depicting the products within a shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:66 +msgid "In Odoo, automatic inventory valuation records are also recorded in the *Accounting* app. To access these accounting entries, navigate to :menuselection:`Accounting --> Journal Entries`, and look for inventory valuation entries with the `STJ` prefix in the :guilabel:`Journal` and :guilabel:`Number` columns, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 +msgid "Accounting entry for the inventory valuation of 10 tables." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:76 msgid "Deliver a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:61 -msgid "In the same logic, when a table will be delivered, the stock valuation will be impacted and you will have access to a similar information." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:78 +msgid "In the same logic, when a table is shipped to a customer and leaves the warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock valuation record as it does on a :abbr:`PO (Purchase Order)`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 +msgid "Decreased stock valuation after a product is shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:87 msgid "The inventory valuation report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:70 -msgid "The summary of this is accessible via the inventory valuation report (accessible from :menuselection:`Inventory --> Reporting --> Inventory Valuation`). It gives you, product per product, the value of your stock. By clicking on the button *Inventory At Date*, you can have the same information for a past date." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:89 +msgid "To view the current value of all products in the warehouse, go to :menuselection:`Inventory app --> Reporting --> Inventory Valuation`. The records in the table are organized by product, and selecting a product's drop-down menu displays detailed records with the :guilabel:`Date`, :guilabel:`Quantity`, and :guilabel:`Total Value` of the inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 +msgid "Inventory valuation report showing multiple products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:99 +msgid "The :guilabel:`Inventory At Date` button, located in the top-left corner of the :guilabel:`Stock Valuation` dashboard, shows the inventory valuation of products available during a prior specified date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:104 +msgid "Update product unit price" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:106 +msgid "For any company: lead times, supply chain failures, and other risk factors can contribute to invisible costs. Although Odoo attempts to accurately represent the stock value, *manual valuation* serves as an additional tool to update the unit price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:111 +msgid "Manual valuation is intended for products that can be purchased and received for a cost greater than 0, or have product categories set with :guilabel:`Costing Method` set as either `Average Cost (AVCO)` or `First In First Out (FIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 +msgid "Add manual valuation of stock value to a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:119 +msgid "Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard by first navigating to :menuselection:`Inventory app --> Reporting --> Inventory Valuation`, and then click the little gray drop-down icon to the left of a product's name, to then reveal stock valuation line items below as well as a teal :guilabel:`+ (plus)` button on the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:124 +msgid "Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product Revaluation` form, where updates to the calculation of inventory valuation can be made, by increasing or decreasing the unit price of each product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 +msgid "Product revaluation form adding a value of $1.00 with the reason being inflation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:6 +msgid "Incoming shipments and delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:8 +msgid "There are several ways to handle how a warehouse receives products (receipts) and ships products (deliveries). Depending on several factors, such as the type of products stocked and sold, warehouse size, and the amount of daily confirmed receipts and delivery orders, the way products are handled when coming in and out of the warehouse can vary a lot. Different settings can be configured for receipts and deliveries; they do not have to be configured to have the same number of steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:15 +msgid "`Using Routes (eLearning Tutorial) `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:16 +msgid "`Push & Pull Rules (eLearning Tutorial) `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:20 +msgid "Choosing the right inventory flow to handle receipts and deliveries" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:22 +msgid "By default, Odoo handles shipping and receiving in three different ways: in one, two, or three steps. The simplest configuration is one step, which is the default. Each additional step required for a warehouse for either the receiving or shipping process will add an additional layer of operations to perform before a product is either received or shipped. These configurations depend entirely on the requirements for the products stored, such as performing quality checks on received products, or using special packaging on shipped products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:30 +msgid "One-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:32 +msgid "The receiving and shipping rules for a one-step configuration are as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:34 +msgid "**Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock occur, such as a transfer to a quality control location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:36 +msgid "**Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping occur, such as a transfer to a packing location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:38 +msgid "Can only be used if not using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:40 +msgid "Receipts and/or deliveries are handled quickly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:41 +msgid "Recommended for small warehouses with low stock levels, and for non-perishable items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:42 +msgid "Items are received or shipped directly into/from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:45 +msgid ":ref:`Process receipts and deliveries in one step `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:48 +msgid "Two-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:50 +msgid "The receiving and shipping rules for a two-step configuration are as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:52 +msgid "**Input + stock**: Bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:55 +msgid "**Pick + ship**: Bring products to an output location before shipping. Packages can be organized by different carriers or shipping docks before being shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:57 +msgid "Minimum requirement to use lot numbers or serial numbers to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)` or :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:60 +msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (such as mattresses, large furniture, heavy machinery, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:83 +msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:66 +msgid ":ref:`Process receipts and deliveries in two steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:69 +msgid "Three-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:71 +msgid "The receiving and shipping rules for a three-step configuration are as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:73 +msgid "**Input + quality + stock**: Receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:75 +msgid "**Pick + pack + ship**: Pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:77 +msgid "Can be used when tracking products by lot or serial numbers when using a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:80 +msgid "Recommended for very large warehouses with very high stock levels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:81 +msgid "Required for any warehouse needing to perform quality control inspections before receiving items into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:87 +msgid ":ref:`Process receipts in three steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:88 +msgid ":ref:`Process deliveries in three steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:91 +msgid "Inventory flow table of contents" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:3 +msgid "Process deliveries in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:7 +msgid "Some companies process large amounts of deliveries every day, many of which include multiple products or require special packaging. To make this efficient, a packing step is needed before shipping out products. For this, Odoo has a three step process for delivering goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:11 +msgid "In the default three-step delivery process, products that are part of a delivery order are picked in the warehouse according to their removal strategy, and brought to a packing zone. After the items have been packed into the different shipments in the packing zone, they are brought to an output location before being shipped. These steps can be modified if they do not fit the needs of the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:20 +msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize three step deliveries. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "Activate multi-step routes and storage locations in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:30 +msgid "Next, the warehouse needs to be configured for three step deliveries. To do this, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the :guilabel:`Warehouse`. Then, select :guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for :guilabel:`Outgoing Shipments`. Then :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +msgid "Set outgoing shipment option to deliver in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:39 +msgid "Activating three-step receipts and deliveries will create two new internal locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:45 +msgid "Process a delivery order in three steps (pick + pack + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:35 +msgid "Create a sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:50 +msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Customer`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:53 +msgid "A :guilabel:`Delivery` smart button will appear in the top right. Clicking on it will show the picking order, packing order, and the delivery order, which are all associated with the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +msgid "After confirming the sales order, the Delivery smart button appears showing three items\n" +"associated with it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:62 +msgid "Process a picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:64 +msgid "The picking, packing, and delivery orders will be created once the sales order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +msgid "Ready status for the pick operation while the packing and delivery operations are waiting\n" +"another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:72 +msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be packed. The status of the packing order and delivery order will both be :guilabel:`Waiting Another Operation`, since the packing and delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` when the packing has been marked :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:78 +msgid "The receipt can also be found in the *Inventory* application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Pick` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +msgid "The pick order can be seen in the Inventory Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:85 +msgid "Click on the picking to process. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as done, and complete the transfer to the :guilabel:`Packing Zone`. Then the packing order will be ready. Since the documents are linked, the products which have been previously picked are automatically reserved on the packing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "Validate the picking by clicking Validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:95 +msgid "Process a packing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:97 +msgid "The packing order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Pack` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +msgid "The packing order can be seen in the Inventory kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:105 +msgid "Click on the packing order associated with the sales order, then click on :guilabel:`Validate` to complete the packing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +msgid "Click Validate on the packing order to transfer the product from the packing zone to the\n" +"output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:113 +msgid "Once the packing order is validated, the product leaves the :guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` location. Then, the status of the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:118 +msgid "Process a delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:120 +msgid "The delivery order will be ready to be processed once the packing is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +msgid "The delivery order can be seen in the Delivery Orders Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:128 +msgid "Click on the delivery order associated with the sales order, then click on :guilabel:`Validate` to complete the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "Click Validate on the delivery order to transfer the product from the output location to\n" +"the customer location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:136 +msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:3 +msgid "Process receipts and deliveries in one step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:7 +msgid "By default, incoming shipments are configured to be received directly into stock, and outgoing shipments are configured to be delivered directly from stock to the customer; the default setting for warehouses in Odoo is one step receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:12 +msgid "Incoming and outgoing shipments do not need to be configured with the same steps. For example, products can be received in one step, but shipped in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:15 +msgid "In the following example, one step will be used for both receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:18 +msgid "Configure the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:20 +msgid "If another receiving or shipping configuration is set on the warehouse, they can easily be set back to the one step setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:23 +msgid "Begin by navigating to :menuselection:`Inventory --> Configuration --> Warehouses`, click on the desired warehouse, and click :guilabel:`Edit`. Next, on the :guilabel:`Warehouse Configuration` tab, under the :guilabel:`Shipments` section, select :guilabel:`Receive goods directly (1 step)` for :guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods directly (1 step)` for :guilabel:`Outgoing Shipments`, and :guilabel:`Save` the changes to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +msgid "Set incoming and outgoing shipment options to receive and deliver in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:35 +msgid "Receive goods directly (1 step)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:46 +msgid "Create a purchase order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:72 +msgid "On the main :menuselection:`Purchase` application dashboard, start by making a new quote by clicking :guilabel:`Create`. Then, select (or create) a :guilabel:`Vendor` from the drop-down field, add a storable :guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` to finalize the quote as a new purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:97 +msgid "A :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (purchase order)` form — click it to reveal the associated receipt for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +msgid "Receipt smart button appears on the confirmed purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:93 +msgid "Purchase order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Receipts` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +msgid "Receipt kanban card's 1 to Process smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:97 +msgid "Process the receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:64 +msgid "When viewing the receipt (associated with the purchase order above), click :guilabel:`Validate` to then complete the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +msgid "Validate the purchase order via the Validate smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:72 +msgid "If :guilabel:`Storage Locations` are activated, clicking the :guilabel:`≣ (bullet list)` details icon next to the :guilabel:`🗑️ (trash)` delete icon enables the :guilabel:`Detailed Operations` screen to pop-up. This allows the location(s) to be specified for the received product(s)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +msgid "Select the Storage Location for the products being received in the Detailed Operations\n" +"pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:81 +msgid "Once the receipt is validated, the product leaves the :guilabel:`Supplier Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives here, it will be available for manufacturing, sales, etc. Then, the status of the document will change to :guilabel:`Done`, thus completing the reception process in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:87 +msgid "Deliver goods directly (1 step)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:92 +msgid "Start my navigating to the main :menuselection:`Sales` app dashboard, and make a new quote by clicking :guilabel:`Create`. Then select (or create) a :guilabel:`Customer` from the drop-down field, add a storable :guilabel:`Product` that is in stock to the order lines, and click :guilabel:`Confirm` to finalize the quotation as a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:100 +msgid "A :guilabel:`Delivery` smart button will appear in the top-right corner of the :abbr:`SO (Sales Order)` form — click it to reveal the associated delivery order for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +msgid "The Delivery smart button appears after the sales order is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:108 +msgid "Delivery orders can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +msgid "Delivery Orders kanban card's 1 to Process smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:196 +msgid "Process the delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:119 +msgid "When viewing the delivery order (associated with the sales order above), click :guilabel:`Validate` to then complete the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +msgid "Validate the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:126 +msgid "Once the picking order is validated, the product leaves the :guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers location`. Then, the status of the document will change to :guilabel:`Done`, thus completing delivery in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:3 +msgid "Process receipts and deliveries in two steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:7 +msgid "Depending on a company's business processes, multiple steps may be needed before receiving or shipping products. In the two-step receipt process, products are received in an input area, then transferred to stock. Two-step receipts work best when various storage locations are being used, such as locked or secured areas, freezers and refrigerators, or various shelves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:12 +msgid "Products can be sorted according to where they are going to be stored, and employees can stock all the products going to a specific location. The products are not available for further processing until they are transferred into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:16 +msgid "In the two-step delivery process, products that are part of a delivery order are picked from the warehouse according to their removal strategy, and brought to an output location before being shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:20 +msgid "One situation where this would be useful is when using either a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy, where the products that are being picked need to be selected based on their receipt date or expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:25 +msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize two-step receipts and deliveries. Incoming and outgoing shipments do not need to be set to have the same steps. For example, products can be received in two steps, but shipped in one step. In the following example, two steps will be used for both receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:32 +msgid "Configure multi-step routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:34 +msgid "First, make sure the :guilabel:`Multi-Step Routes` option is enabled in :menuselection:`Inventory --> Configuration --> Settings`, under the :guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:39 +msgid "Activating the :guilabel:`Multi-Step Routes` setting will also activate the :guilabel:`Storage Locations` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:46 +msgid "Next, the warehouse needs to be configured for two-step receipts and deliveries. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to change the warehouse settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:50 +msgid "Then, select :guilabel:`Receive goods in input and then stock (2 steps)` for :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and then deliver (2 steps)` for :guilabel:`Outgoing Shipments`. :guilabel:`Save` the changes to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "Set incoming and outgoing shipment options to receive and deliver in two steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:59 +msgid "Activating two-step receipts and deliveries will create new *input* and *output* locations, which by default, are labeled :guilabel:`WH/Input` and :guilabel:`WH/Output`, respectively, on the :guilabel:`Locations` dashboard. To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, and then click :guilabel:`Edit`. On the location form, update the :guilabel:`Location Name`, make any other changes (if necessary) and :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:67 +msgid "Process a receipt in two steps (input + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:78 +msgid "For businesses with multiple warehouses that have different step configurations, the :guilabel:`Deliver To` field on the :abbr:`PO (Purchase Order)` form may need to be specified as the correct *input location* connected to the two-step warehouse, which can be done by selecting the warehouse from the drop-down selection that includes the `Receipts` label at the end of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:84 +msgid "After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (Purchase Order)` form — click it to reveal the associated receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +msgid "After confirming a purchase order, a Receipt smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:0 +msgid "One receipt ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:104 +msgid "The receipt and internal transfer will be created once the purchase order is confirmed. The status of the receipt will be :guilabel:`Ready`, since the receipt must be processed first. The status of the internal transfer will be :guilabel:`Waiting Another Operation`, since the transfer cannot happen until the receipt is completed. The status of the internal transfer will only change to :guilabel:`Ready` once the receipt has been marked as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:110 +msgid "Click on the :guilabel:`Receipt` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "Validate the receipt by clicking Validate, then the product will be transferred to the\n" +"WH/Input location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:119 +msgid "Process the internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:121 +msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product into stock. Navigate to the :menuselection:`Inventory` app, and on the :guilabel:`Inventory Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Internal Transfers` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +msgid "One Internal Transfer ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:130 +msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "Validate the internal transfer to move the item to stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:140 +msgid "Process a delivery order in two steps (pick + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:145 +msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`Create`. Select or create a :guilabel:`Customer`, add a storable :guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:149 +msgid "After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart button will appear in the top-right corner of the :abbr:`SO (Sales Order)` form. Click it to reveal the associated delivery forms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "After confirming the sales order, the Delivery smart button appears showing two items\n" +"associated with it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:159 +msgid "Sales order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Pick` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:0 +msgid "The pick order can be seen in the Inventory kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:168 +msgid "Process the picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:170 +msgid "The picking and delivery order will be created once the sales order is confirmed. When the :guilabel:`Delivery` smart button appears, click it to reveal the :guilabel:`Transfers` dashboard, which lists both the picking and the delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:174 +msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be shipped. The status of the delivery order will be :guilabel:`Waiting Another Operation`, since the delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` once the picking has been marked as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "Ready status for the pick operation while the delivery operation is Waiting Another\n" +"Operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:185 +msgid "Click on the picking delivery order to begin processing it. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as :guilabel:`Done`, then the delivery order will be ready for processing. Since the documents are linked, the products which have been previously picked are automatically reserved on the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:198 +msgid "The delivery order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application, on the :guilabel:`Inventory Overview` dashboard. Click the :guilabel:`# To Process` smart button in the :guilabel:`Delivery Orders` kanban card to begin." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:203 +msgid "The delivery order associated with the :abbr:`SO (Sales Order)` can also be quickly accessed by clicking on the :guilabel:`Delivery` smart button again, and choosing the delivery order on the :guilabel:`Transfers` page (which should now be marked as :guilabel:`Ready`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +msgid "The delivery order can be seen in the Inventory Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:211 +msgid "Click on the delivery order associated with the :abbr:`SO (Sales Order)`, then click on :guilabel:`Validate` to complete the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:219 +msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location on the :guilabel:`Transfers` dashboard and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:3 +msgid "Process receipts in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:7 +msgid "Some companies require a quality control process before receiving goods from suppliers. To accomplish this, Odoo has a three-step process for receiving goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:10 +msgid "In the three-step receipt process, products are received in an input area, then transferred to a quality area for inspection. Products that pass the quality inspection are then transferred into stock. The products are not available for further processing until they are transferred out of the quality area and into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:18 +msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize three-step receipts. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +msgid "Activate multi-step routes and storage locations in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:28 +msgid "Next, the warehouse needs to be configured for three-step receipts. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the warehouse. Then, select :guilabel:`Receive goods in input, then quality and then stock (3 steps)` for :guilabel:`Incoming Shipments`. Then, :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +msgid "Set incoming shipment option to receive in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:37 +msgid "Activating three-step receipts and deliveries will create two new internal locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:43 +msgid "Process a receipt in three steps (input + quality + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:48 +msgid "In the :menuselection:`Purchase` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:52 +msgid "A :guilabel:`Receipt` smart button will appear in the top right, and the receipt will be associated with the purchase order. Clicking on the :guilabel:`Receipt` smart button will show the receipt order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:61 +msgid "Process a receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:63 +msgid "One receipt and two internal transfers (one transfer to quality, and a subsequent transfer to stock) will be created once the purchase order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +msgid "The status of the three receipt transfers will show which operation is ready and which ones\n" +"are waiting another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:72 +msgid "The status of the receipt transferring the product to the input location will be :guilabel:`Ready`, since the receipt must be processed before any other operation can occur. The status of the two internal transfers will be :guilabel:`Waiting Another Operation`, since the transfers cannot be processed until the linked step before each transfer is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:77 +msgid "The status of the first internal transfer to *quality* will only change to :guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The status for the second internal transfer to *stock* will be marked :guilabel:`Ready` only after the transfer to quality has been marked :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:82 +msgid "The receipt can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Receipts` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +msgid "One Receipt ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:90 +msgid "Click on the receipt associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +msgid "Validate the receipt by clicking Validate, and the product will be transferred to the\n" +"WH/Quality location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:99 +msgid "Process a transfer to Quality Control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:101 +msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product to :guilabel:`Quality Control`. In the :menuselection:`Inventory` :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:110 +msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to the :guilabel:`Quality Control` location. Once the transfer is validated, the product is ready for the quality inspection, but is not available for manufacturing or delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +msgid "Validate the internal transfer to move the item to the Quality Control location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:120 +msgid "Process a transfer to stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:122 +msgid "Once the product is in the :guilabel:`Quality Control` location, the final internal transfer is ready to move the product to :guilabel:`Stock`. In the :guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` Kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:126 +msgid "Click on the final :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/warehouses.rst:5 msgid "Warehouses" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:3 +msgid "Create a second warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:5 +msgid "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." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:8 +msgid "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:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:12 +msgid ":guilabel:`Warehouse`: the full name of the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:13 +msgid ":guilabel:`Short Name`: the abbreviated code by which the warehouse is referred to; the short name for the default warehouse in Odoo is **WH**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:15 +msgid ":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" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:17 +msgid ":guilabel:`Address`: the address where the warehouse is located" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:20 +msgid "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 `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:25 +msgid ":guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and outgoing shipments should follow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:27 +msgid ":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied from this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:28 +msgid ":guilabel:`Manufacture to Resupply`: allow for items to be manufactured in this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:29 +msgid ":guilabel:`Manufacture`: select the route that should be followed when manufacturing goods inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:31 +msgid ":guilabel:`Buy to Resupply`: check the box to allow for purchased products to be delivered to the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:33 +msgid ":guilabel:`Resupply From`: select warehouses that can be used to resupply the warehouse being created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:-1 +msgid "A filled out form for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:41 +msgid "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." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:46 +msgid "After filling out the form, click :guilabel:`Save` and the new warehouse will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:49 +msgid "Add inventory to a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:51 +msgid "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:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:57 +msgid ":guilabel:`Inventory Reference`: the name or code that the inventory adjustment can be referred to by" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:59 +msgid ":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" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:61 +msgid ":guilabel:`Products`: include all products that will be added to inventory or leave blank to select any product during the next step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:63 +msgid ":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" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:65 +msgid ":guilabel:`Accounting Date`: the date used by accounting teams for bookkeeping related to the inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:67 +msgid ":guilabel:`Company`: the company that owns the inventory; can be set as the user's company or as a customer or vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:69 +msgid ":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" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:-1 +msgid "A filled out form for an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:77 +msgid "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:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:81 +msgid ":guilabel:`Product`: the product being added to inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:82 +msgid ":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" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:84 +msgid ":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the serial number used to identify it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:86 +msgid ":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" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:88 +msgid ":guilabel:`Counted`: the amount of the product that is being added to inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:89 +msgid ":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" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:91 +msgid ":guilabel:`UoM`: the unit of measure used for counting the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:-1 +msgid "Include a line for each product being added to inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:97 +msgid "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." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:3 msgid "What is the difference between warehouses and locations?" msgstr "" @@ -2353,30 +3729,186 @@ msgstr "" msgid "In Odoo, a **Warehouse** is the actual building/place in which your items are stocked. You can setup multiple warehouses and create moves between warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:11 msgid "A **Location**, is a specific space within your warehouse. It can be considered as a sublocation of your warehouse, as a shelf, a floor, an aisle, etc. Therefore, a location is part of one warehouse only and it is not possible to link one location to multiple warehouses. You can configure as many locations as you need under one warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:17 msgid "There are 3 types of locations:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:19 msgid "The **Physical Locations** are internal locations that are part of the warehouses for which you are the owner. They can be the loading and unloading area of your warehouse, a shelf or a department, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:23 msgid "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 you are not the owner of the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:27 msgid "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 you want to place lost products out of your stock (in the **Inventory loss**), or when you want to take into account products that are on their way to your warehouse (**Procurements**)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:31 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:33 msgid "In Odoo, locations are structured hierarchically. You can structure your locations as a tree, dependent on a parent-child relationship. This gives you more detailed levels of analysis of your stock operations and the organization of your warehouses." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:3 +msgid "Transfer products between warehouses using replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:5 +msgid "For companies that use multiple warehouses, it is often necessary to transfer items between them. This is referred to as an *inter-warehouse transfer*. Odoo *Inventory* handles the administrative process of inter-warehouse transfers to ensure that inventory counts remain accurate during and after the transfer. This document will detail the method for conducting an inter-warehouse transfer using replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:12 +msgid "Configure warehouses for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:14 +msgid "First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by navigating to :menuselection:`Inventory --> Configuration --> Settings`, and then check the box under the :guilabel:`Warehouse` tab. This will provide additional configuration options when creating a second warehouse that are needed for inter-warehouse replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:19 +msgid "By default, Odoo comes with a main warehouse already configured. If an additional warehouse has not already been created, do so now from the :guilabel:`Inventory` module by selecting :menuselection:`Configuration --> Warehouses --> Create`. Otherwise, select the warehouse that products will be transferred to from the :guilabel:`Warehouses` page and then click :guilabel:`Edit` to change its settings. Configure the warehouse as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:25 +msgid ":guilabel:`Warehouse`: choose a name that is not already being used for another warehouse (e.g. `Alternative Warehouse`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:27 +msgid ":guilabel:`Short Name`: choose a short name by which the warehouse will be identified (e.g. `ALT_WH`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:30 +msgid "Click :guilabel:`Save` and the new warehouse will be created. In addition, a new :guilabel:`Resupply From` field will appear on the warehouse's form. Click :guilabel:`Edit` and then check the box next to the warehouse that will be used to resupply the warehouse that is currently being configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 +msgid "A warehouse settings form configured to allow resupplying between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:39 +msgid "For the purposes of this demonstration, the warehouse that products are transferred from (outgoing) will be titled \"San Francisco\", and the warehouse that products are transferred to (incoming) will be titled \"San Francisco 2\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:44 +msgid "Configure products for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:46 +msgid "Products must also be configured properly in order for them to be transferred between warehouses. Navigate to :menuselection:`Inventory --> Products --> Products` and select an existing product or :guilabel:`Create` a new one, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:50 +msgid "Then, on the product form, go to the :guilabel:`Inventory` tab and enable the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the warehouse receiving the transferred products and *Y* being the warehouse that products are transferred from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 +msgid "Enable the checkbox to resupply one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:59 +msgid "Replenish one warehouse from another" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:61 +msgid "Starting in the :menuselection:`Inventory` module, select :menuselection:`Products --> Products` and then choose the product that will be replenished. Click the :guilabel:`Replenish` button on the top left of the product page and fill out the pop-up form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:65 +msgid ":guilabel:`Quantity`: the number of units that will be sent to the warehouse being replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:66 +msgid ":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to take place" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:67 +msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:68 +msgid ":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* being the warehouse to be replenished and *Y* being the warehouse that the product will be transferred from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 +msgid "The form for replenishing a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:75 +msgid "Click :guilabel:`Confirm` and a delivery order will be created for the outgoing warehouse along with a receipt for the warehouse that will receive the product. Depending on the configuration settings for the outgoing and incoming warehouses, processing delivery orders and receipts will require between one and three steps. This document will detail how to process one-step deliveries and receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:82 +msgid "Process the delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:84 +msgid "The first stage of a replenishment order is processing the delivery from the warehouse that the product is being transferred from. On the :menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, then the delivery order created for the replenishment. On the delivery order page, click the :guilabel:`Check Availability` button in the top left to reserve the quantity of the product to be transferred. Once the delivery has been dispatched, click the :guilabel:`Validate` button to register the quantities shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 +msgid "The delivery orders card for the outgoing warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:99 +msgid "Once the goods arrive at the incoming warehouse, the receipt created for that warehouse must be processed as well. Return to the :menuselection:`Inventory` dashboard and select the :guilabel:`X to Process` button on the :guilabel:`Receipts` card for the incoming warehouse, then the receipt created for the replenishment. On the receipt page, click the :guilabel:`Validate` button in the top left of the page to register the quantities received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:109 +msgid "After processing the receipt, the products transferred will now appear in the inventory of the incoming warehouse. The stock numbers for both warehouses can be viewed by returning to the product page and selecting the :guilabel:`X Units On Hand` button at the top of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:114 +msgid "Automate inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:116 +msgid "Using reordering rules, it is possible to automate the process of replenishing one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:119 +msgid "To get started, navigate to :menuselection:`Inventory --> Products --> Products`, and then choose the product that will be replenished. From the product page, select the :guilabel:`Reordering Rules` smart button at the top of the form, and then on the next page, click :guilabel:`Create` to configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:124 +msgid ":guilabel:`Location`: the location that the reordering rule will replenish when triggered, in this case, the incoming warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:126 +msgid ":guilabel:`Min Quantity`: when the quantity on hand at the incoming warehouse falls below this number, the reordering rule will be triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:128 +msgid ":guilabel:`Max Quantity`: when the reordering rule is triggered, the product will be replenished at the incoming warehouse up to this quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:130 +msgid ":guilabel:`Multiple Quantity`: specify if the product should be replenished in batches of a certain quantity; for example, a product could be replenished in batches of 20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:132 +msgid ":guilabel:`UoM`: the unit of measure used for reordering the product; this value can simply be `Units`, or a specific unit of measurement for weight, length, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 +msgid "A fully configured reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:139 +msgid "Finish by clicking :guilabel:`Save` and the reordering rule will be created. Now, when the scheduler runs automatically each day, a transfer will be created for each reordering rule that has been triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:144 +msgid "To manually trigger reordering rules, start from the :menuselection:`Inventory` module and select :menuselection:`Operation --> Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the pop-up that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:148 +msgid "After the scheduler runs, a delivery order and receipt will be created for the outgoing and incoming warehouses, respectively. Both the delivery order and receipt should be processed using the same method as detailed above." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/routes.rst:5 msgid "Advanced Routes" msgstr "" @@ -2437,568 +3969,596 @@ msgstr "" msgid "The delivery order is now ready to be processed and can be validated too." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:3 -msgid "Inter-warehouse transfers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:5 -msgid "When owning several warehouses, you might need to transfer goods from one warehouse to another. Proceeding to such behavior is called *inter-warehouse transfers*. If this action is physically easy to perform, the administrative part can be arduous. Fortunately, Odoo comes with an intuitive flow that helps save time when registering those transfers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:13 -msgid "First of all, go to :menuselection:`Configuration --> Settings` and enable **Storage Locations**. Then, hit save." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "Enabling the storage location feature in Odoo Inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:21 -msgid "If you want to manage several routes within your warehouses, then enable **Multi-Step Routes** and check :doc:`use-routes`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:25 -msgid "Creating a new warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:27 -msgid "The next step is to create your new warehouse. To do so, go to :menuselection:`Configuration --> Warehouse Management --> Warehouses` and click on **Create**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:30 -msgid "Fill out a **Warehouse Name** and a **Short Name**. The short name is five characters maximum." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "Short name field of a warehouse on Odoo Inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:37 -msgid "The **Short Name** appears on your transfer orders and other warehouse documents. We recommend using an understandable one (e.g.: WH/[first letters of location])." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:40 -msgid "Now, go back to your dashboard. There, new operations related to your warehouse have been automatically generated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "Inventory app dashboard displaying new transfer type for the recently created warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:48 -msgid "Creating a new inventory" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:50 -msgid "If you create a new warehouse, you might already have an existing inventory in it. In that case, you should create an inventory in Odoo. If this is not the case, you can skip this step." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:53 -msgid "Into the inventory application, select :menuselection:`Operations --> Inventory Adjustment`. Then, create a new inventory by clicking on **Create**. Fill in the **Inventory Reference**, **Date** and make sure to select the right warehouse and location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "View of the inventory adjustment form before hitting the start button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:61 -msgid "Next, click on **Start Inventory**. You will be able to input your existing products in the new window. Select add an item and indicate the **Real Quantity** available in the warehouse. The theoretical quantity can not be changed as it represents a computed one from purchase and sales orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "View of the actual physical inventory of the new warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:71 -msgid "Don't forget to validate your inventory once you have recorded the state of all your products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:74 -msgid "Create an internal transfer" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:76 -msgid "The final step is to create your internal transfer. If you want to transfer eight units of a product from your first warehouse to another one, proceed as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:79 -msgid "From your dashboard, select an internal movement of one of the two warehouses. To do so, click on :menuselection:`Manage --> Planned Transfer`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "View of the choice between planned transfer and immediate transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:86 -msgid "On the new window, select the source location zone (in this case, your \"old\" warehouse) and the destination location zone (in this case, your \"new\" warehouse)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:89 -msgid "Add the products you want to transfer by clicking on **Add an Item**, then click on **Save** and **Mark as TODO** once you are done." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "View of the internal transfer form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:96 -msgid "If you selected **Immediate Transfer**, Odoo processes the transfer automatically after you clicked on **Validate**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:99 -msgid "If you select **Mark as TODO**, Odoo puts the transfer in **Waiting Availability** status. Click on **Reserve** to reserve the number of products in your source warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:102 -msgid "It is also possible to manually transfer each product:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:104 -msgid "Via your dashboard, select the transfer order in the source location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "View of the dashboard with a zoom of the pending internal transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:110 -msgid "Select the right transfer order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "View of the pending internal transfers list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:116 -msgid "Click on the little pencil logo in the lower right corner to open the operation details window. In this new window you can manually indicate how many products you process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:None -msgid "View of a backorder pop-up window because all products are not moved at the same time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:124 -msgid "If you decide to process the transfer order partially (e.g., a part of the products can't be shipped yet due to an unexpected event), Odoo automatically asks if you wish to create a **backorder**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:128 -msgid "Create a backorder if you expect to process the remaining products later." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:129 -msgid "Do not create a backorder if you will not supply/receive the remaining products." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:3 -msgid "Taking stock from different warehouses" +msgid "Sell stock from multiple warehouses using virtual locations" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:5 -msgid "When you plan to deliver a customer, you don’t know in advance if the products will come from Warehouse A or Warehouse B. You may, in some cases, need to take stock from different warehouses. With *Odoo*, you can configure this by using the concept of virtual warehouses. Let us show you how to set those virtual warehouses." +msgid "While keeping stock and selling inventory from one warehouse might work for smaller companies, bigger companies might need to keep stock in, or sell from, multiple warehouses in multiple locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:11 -msgid "Set up virtual warehouses" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:9 +msgid "In Odoo, sometimes products included in a single sales order might take stock from two (or more) warehouses. In Odoo, pulling products from multiple warehouses to satisfy sales demands can be done by using *virtual locations*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:13 -msgid "Let’s say you have two warehouses: Warehouse A and Warehouse B. Create a new warehouse, that will be a virtual one. It will allow you to take the stock from A or B. To do so, go to your inventory app settings and enable the multi-warehouses feature. Then, go to the warehouses menu and click on create." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:14 +msgid "In order to create virtual locations in warehouses and proceed to the following steps, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features will need to be enabled in the :menuselection:`Settings` app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:22 -msgid "The *Storage Location* feature will be automatically enabled. Good news, because you will need it later in the process." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:18 +msgid "To do so, go to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the :guilabel:`Warehouse` section, and click the checkboxes next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`. Then, :guilabel:`Save` the changes to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:23 +msgid "Create and configure a virtual parent location" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:25 -msgid "Now, you have to make sure that the main stock locations of warehouse A and warehouse B are children locations of the main stock location of warehouse A + B. Go to the locations menu, and edit the main location of your two warehouses. Then, change their parent location to main location of warehouse A+B." +msgid "Before creating any virtual stock locations, a new warehouse will need to be created. This new warehouse will act as a *virtual* warehouse, and will be the *parent* location of other physical warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:34 -msgid "Sell a product from the virtual warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:31 +msgid "Virtual warehouses are great for companies with multiple physical warehouses. This is because a situation might arise when one warehouse runs out of stock of a particular product, but another warehouse still has stock on-hand. In this case, stock from these two (or more) warehouses could be used to fulfill a single sales order." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:36 -msgid "Let’s say you have two products, one stored in warehouse A and one stored in warehouse B. Now, you can create a new quotation for one of each product. Go to other information and choose Warehouse A+B in the shipping information." +msgid "The \"virtual\" warehouse acts as a single aggregator of all the inventory stored in a company's physical warehouses, and is used (for traceability purposes) to create a hierarchy of locations in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:41 +msgid "Create a new warehouse" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:43 -msgid "Once you have done it, you can convert it to a sales order. Then, a delivery order will be automatically generated, with a product reserved in warehouse A and one in warehouse B." +msgid "To create a new warehouse, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Create`. From here, the warehouse :guilabel:`Name` and :guilabel:`Short Name` can be changed, and other warehouse details can be changed under the :guilabel:`Warehouse Configuration` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:3 -msgid "Using Routes and Pull/Push Rules" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:48 +msgid "Under the :guilabel:`Shipments` heading, set the number of steps used to process :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` by selecting between the :guilabel:`1 step`, :guilabel:`2 steps`, and :guilabel:`3 steps` radio buttons. The desired option for :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` will depend on the warehouse's procurement process, and might differ for individual products or product categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:55 +msgid ":doc:`How to choose the right flow to handle receipts and deliveries? `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:58 +msgid "Under the :guilabel:`Resupply` heading, configure the method(s) for how the warehouse resupplies its inventory:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:61 +msgid ":guilabel:`Resupply Subcontractors`: resupply subcontractors with components from this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:62 +msgid ":guilabel:`Manufacture to Resupply`: when products are manufactured, they can be manufactured in this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:64 +msgid ":guilabel:`Manufacture`: to produce right away, move the components to the production location directly and start the manufacturing process; to pick first and then produce, unload the components from the stock to input location first, and then transfer it to the production location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:68 +msgid ":guilabel:`Buy to Resupply`: when products are bought, they can be delivered to this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:69 +msgid ":guilabel:`Resupply From`: automatically create routes to resupply this warehouse from another chosen warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:73 +msgid "*Routes* can be set and configured directly from the :guilabel:`Warehouse` form, by clicking on the :guilabel:`Routes` smart button. Once the warehouse is configured, virtual *Locations* can be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:-1 +msgid "The edit screen for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:81 +msgid "In order to apply this virtual warehouse as the *parent* location of two *child* location warehouses, there need to be two warehouses configured with physical stock locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid "**Parent Warehouse**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouse`: `Virtual Warehouse`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid ":guilabel:`Location`: `VWH`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid "**Child Warehouses**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouses`: `Warehouse A` and `Warehouse B`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid ":guilabel:`Locations`: `WHA/Stock` and `WHB/Stock`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:95 +msgid "Create a virtual parent location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:98 +msgid "In order to take stock from multiple warehouses to fulfill a sales order, there need to be at least **two** warehouses acting as *child locations* of the *virtual parent location* warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:101 +msgid "To create and edit *Locations*, go to :menuselection:`Inventory --> Configuration --> Locations`. All :guilabel:`Locations` are listed here, including the *Stock* :guilabel:`Location` of the virtual warehouse that was created. Click into the *Stock* :guilabel:`Location` for the virtual warehouse that was previously created (:dfn:`Warehouse Name/Stock`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:106 +msgid "Then, under the :guilabel:`Additional Information` section, change the :guilabel:`Location Type` from :guilabel:`Internal Location` to :guilabel:`View`. :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:109 +msgid "This identifies this :guilabel:`Location` as a *virtual location*, which is used to create a hierarchical structure for a warehouse and aggregate its *child locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:113 +msgid "Products can *not* be stored in a :guilabel:`View` :guilabel:`Location Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:-1 +msgid "Warehouse location types in location creation screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:120 +msgid "Configure physical warehouse locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:122 +msgid "Navigate back to the :guilabel:`Locations` overview (via the breadcrumbs), and remove any filters in the :guilabel:`Search Bar`. Then, click into the first physical warehouse :guilabel:`Location` that was previously created to be a *child location*, and click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:126 +msgid "Under :guilabel:`Parent Location`, select the virtual warehouse from the drop-down menu, and :guilabel:`Save` changes. Then, navigate back to the :guilabel:`Locations` overview, and repeat this step for the second physical warehouse stock location. Be sure to :guilabel:`Save` changes again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:130 +msgid "Both locations are now *child locations* of the virtual warehouse *parent location*. This allows stock to be taken from multiple locations to fulfill a single sales order, if there is not enough stock in any one location (provided they are both tied to the same virtual warehouse *parent location*)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:136 +msgid "Example flow: Sell a product from a virtual warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:139 +msgid "To sell products from multiple warehouses using a virtual *parent* location in this flow, there must be at least **two** products and at least **two** warehouses configured - with at least **one** product with quantity on-hand in each warehouse, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:143 +msgid "To create a new request for quotation, or RFQ, navigate to the :menuselection:`Sales` app, and click :guilabel:`Create` from the :guilabel:`Quotations` overview. Fill out the information on the new quotation by adding a :guilabel:`Customer`, and click :guilabel:`Add a product` to add the two products stored in the two warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:148 +msgid "Then, click the :guilabel:`Other Info` tab on the sales order form. Under the :guilabel:`Delivery` section, change the :guilabel:`Warehouse` field value listed to the virtual warehouse that was previously created. Once the warehouse has been changed, click :guilabel:`Confirm` to convert the quotation into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:153 +msgid "Now that the quotation has been confirmed as a sales order, click the :guilabel:`Delivery` smart button. From the warehouse delivery form, confirm that the :guilabel:`Source Location` value matches the :guilabel:`Warehouse` field value from the sales order. Both should list the virtual warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:159 +msgid "The :guilabel:`Source Location` on the warehouse delivery form and the :guilabel:`Warehouse` under the :guilabel:`Other Info` tab on the sales order form *must* match in order for the products included in the sales order to be pulled from different warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:163 +msgid "If the virtual warehouse is not the value in the :guilabel:`Source Location` field on the warehouse delivery form, then click :guilabel:`Edit`, make the change, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:166 +msgid "If the virtual warehouse is not the value in the :guilabel:`Warehouse` field on the sales order, then a new quotation may need to be generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:168 +msgid "If whe :guilabel:`Warehouse` field is missing on the sales order form, then the virtual warehouse (and its children warehouses) may not have been set up correctly, in which case, review the documentation above again to make sure all settings/configuration were done properly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:-1 +msgid "Delivery order with matching source and child locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:176 +msgid "Finally, on the warehouse delivery form, under the :guilabel:`Detailed Operations` tab, confirm that the *Locations* values under the :guilabel:`From` column for each product matches to the *child locations* that are tied to the virtual *parent location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:181 +msgid "To view which *Locations* the products are coming from on the drop-down menus, click the :guilabel:`internal link (arrow)` icon to expand the *Location* information. If needed, it can be changed from here (granted there is quantity on hand for the product in that location)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:185 +msgid "Once everything has been properly set, click :guilabel:`Validate` and then :guilabel:`Apply` to validate the delivery. Then, navigate back to the sales order form (via the breadcrumbs), and click :guilabel:`Create Invoice` to invoice for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:190 +msgid "To use a virtual *parent* location as the default warehouse for sales orders, each salesperson can have the virtual warehouse assigned to them from the drop-down menu next to :guilabel:`Default Warehouse` on their employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:-1 +msgid "Default warehouse location on employee form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:5 +msgid "Using Routes and Pull/Push Rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:7 msgid "In inventory management, the supply chain strategy determines when products should be fabricated, delivered to distribution centers, and made available in the retail channel." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:11 msgid "This kind of strategic process can be configured using *Routes*, featuring *Pull and Push Rules*. Once everything is properly configured, the inventory app can automatically generate transfers following the instructions given by the rules. Yes, Odoo simplifies your life." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:18 msgid "Inside the warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:20 msgid "Let’s imagine a generic warehouse plan, where you can find receiving docks, a quality control area, storage locations, picking and packing areas, and shipping docks. All products go through all these locations, which also trigger all the route's rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of a generic warehouse with stock and quality control area" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:29 msgid "In this example, vendor trucks unload pallets of ordered goods at receiving docks. Operators then scan the products in the receiving area. Some of these products are sent to a quality control area (those devoted to being used during the manufacturing process, for example), while others are directly stored in their respective locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of a generic push to rule when receiving products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:38 msgid "Here is an example of a fulfillment route. In the morning, items are picked for all the orders that need to be prepared during the day. These items are picked from storage locations and moved to the picking area, close to where the orders are packed. Then, the orders are packed in their respective boxes and conveyors bring them close to the shipping docks, ready to be delivered to customers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of a generic pull from rule when preparing deliveries" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:50 #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:45 msgid "How does it work?" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:53 msgid "Pull Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:55 msgid "With *Pull Rules*, a demand for some products triggers procurements, while *Push Rules* are triggered by products arriving in a specific location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:59 msgid "We can say that *Pull Rules* are used to fulfill a customer order, a sale order. So, Odoo generates a need at the *Customer Location* for each product in the order. Because *Pull Rules* are triggered by a need, Odoo looks for a *Pull Rule* defined on the *Customer Location*. In our case, a delivery order pull rule that transfers products from the *Shipping Area* to the *Customer Location* is found, and a transfer between the two locations is created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:67 msgid "Then, Odoo finds another pull rule that tries to fulfill the need for the *Shipping Area*: the *Packing Rule* that transfers products from the *Packing Area* to the *Shipping Area*. And, finally, other rules are triggered until a transfer between the *Stock* and the *Picking Area* is created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:74 msgid "All these transfers are pre-generated by Odoo, starting from the end and going backwards. While working, the operator process these transfers in the opposite order: first the picking, then the packing, then the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:81 msgid "Push Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:83 msgid "On the other hand, *Push Rules* are much easier to understand. Instead of pre-generating documents based on needs, they are live-triggered when products arrive in a specific location. *Push Rules* basically say: \"when a product arrives at a specific location, move it to another location.\"" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:88 msgid "A simple example would be: when a product arrives in the *Receipt Area*, move them to the *Storage Location*. As different rules can be applied to different products, you can assign different storage locations for different products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:93 msgid "Another rule could be: when products arrive at a location, move them to the *Quality Control Area*. Then, once the quality check is done, move them to their *Storage Location*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:98 msgid "*Push Rules* can be triggered only if no *Pull Rule* pre-generated the upstream transfers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:102 msgid "Sets of rules like those are called routes. The grouping on the rule defines how products are grouped in the same transfer or not. For example, during the picking operation, all orders are grouped in one transfer, whereas the packing operation respects the grouping per customer order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:109 msgid "Use Routes and Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:111 msgid "Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you manage advanced routes configuration such as:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:114 msgid "Manage product manufacturing chains;" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:115 msgid "Manage default locations per product;" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:116 msgid "Define routes within your warehouse according to business needs, such as quality control, after-sales services, or supplier returns;" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:118 msgid "Help rental management by generating automated return moves for rented products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:121 msgid "To configure a route such as one of those above, open the **Inventory Application** and go to :menuselection:`Configuration --> Settings`. Then, enable the *Multi-Step Routes* feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "activation of the multi-steps feature in Odoo Inventory" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:130 msgid "The *Storage Locations* feature is automatically activated with the *Multi-Step Routes*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:133 msgid "Once this first step is completed, you have the choice between pre-configured routes or custom ones. Both are explained below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:137 msgid "Pre-configured Routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:139 msgid "Odoo’s pre-configured routes are available in the warehouses’ menu. To find it, go to :menuselection:`Inventory --> Configuration --> Warehouses`. There, open your warehouse and edit it to see the pre-configured routes for incoming and outgoing shipments." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "preconfigured warehouse in Odoo Inventory" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:148 msgid "Some more advanced routes, such as pick-pack-ship, are already configured to make your life easier. Those are based on your choice for shipments. Once you made your choice, head to :menuselection:`Inventory --> Configuration --> Routes` to see the routes Odoo generated for you." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of all the preconfigured routes Odoo offers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:153 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:157 msgid "Opening one of those routes allows you to see on what you can apply the route. Here, all the selected product categories in the *YourCompany* warehouse are set up to follow the 3-steps route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of a route example applicable on category and warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:161 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:165 msgid "Easier for many businesses, this process might not fit yours. Thus, you can configure custom routes in which you can define your own rules, but also the source and destination location of each action. As an example, here are the rules for the pre-configured route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "rules example with push & pull actions in Odoo Inventory" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:171 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:175 msgid "Custom Routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:177 msgid "To create a custom route, go to :menuselection:`Inventory --> Configuration --> Routes`, click on create, and choose the places where this route can be selected. Of course, combinations are available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of a pick - pack - ship route as an example" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:182 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:186 msgid "Each place has a different behavior, so it is important to tick only the useful ones and adapt each route accordingly." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:189 msgid "When applying the route on a product category (:menuselection:`Inventory --> Configuration --> Product Categories`), all the rules configured in the route are applied to **every** product of the category. For example, this can be useful if you use the dropshipping process for all the products from the same category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of a route applied to the \"all\" product category" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:195 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:199 msgid "The same behavior applies to the warehouses. If you tick *Warehouses*, all the transfers occurring inside the chosen warehouse, and meeting the conditions of the linked rules, then follow that route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the route menu when selecting applicable on warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:203 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:207 msgid "For the *Sales Order Lines*, it is more or less the opposite. You have to choose the route yourself when creating a quotation. This is pretty useful if some products go through different routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the route menu when selecting applicable on sales order lines" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:215 msgid "If you work with this kind of route, it is important to keep in mind that it must be selected on the sales order, such as below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the menu allowing to add new lines to sales orders" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:218 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:222 msgid "Then, the route can be chosen on each line of the document." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the routes added to the sales orders" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:224 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:228 msgid "Finally, there are routes that can be applied to products. Those work more or less like the product categories: once selected, you have to manually set on which product it must be applied." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the menu when selecting applicable on products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:232 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:236 msgid "To do so, go to :menuselection:`Inventory --> Master Data --> Products` and open the one on which you want to apply the route. Then go to the *Inventory tab* and select the route you’ve created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of a product form, where the route must be selected" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:240 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:244 msgid "If, prima facie, the routes’ configuration can appear quite easy, don’t forget that we haven’t set up any rule yet. If not harder to set up, those are vital to have working routings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:245 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:249 msgid "Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:247 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:251 msgid "The rules are to be defined on the routes. To do so, go to :menuselection:`Inventory --> Configuration --> Routes`, then to the *Rules* section, and click on *Add a line* button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the rules menu, where it is possible to add new rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:255 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:259 msgid "The available rules trigger various actions. If Odoo offers *Push* and *Pull* rules, others are also available. Here are some explanations for all of them:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:259 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:263 msgid "**Pull From**: this rule is triggered by a need for the product in a specific location. The need can come from a sale order which has been validated or from a manufacturing order which requires a specific component. When the need appears in the destination location, Odoo generates a picking to fulfill this need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:264 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:268 msgid "**Push To**: this rule is triggered by the arrival of some products in the defined source location. In the case you move products to the source location, Odoo generates a picking to move those products to the destination location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:268 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:272 msgid "**Pull & Push**: this rule allows generating pickings in the two situations explained above. This means that when products are required at a specific location, a transfer is created from the previous location to fulfill that need. This creates a need in the previous location and a rule is triggered to fulfill it. Once the second need is fulfilled, the products are pushed to the destination location and all the needs are fulfilled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:274 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:278 msgid "**Buy**: when products are needed at the destination location, a request for quotation is created to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:276 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:280 msgid "**Manufacture**: when products are needed in the source location, a manufacturing order is created to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "overview of a transfer requested between the stock and the packing zone" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:283 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:287 msgid "You must also define the *Operation Type*. This operation allows defining which kind of picking is created from the rule. With our above screenshot, the created picking is, for example, an internal transfer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:288 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:292 msgid "On the other hand, the *Supply Method*, allows defining what happens at the source location:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:291 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:295 msgid "**Take From Stock**: the products are taken from the available stock of the source location;" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:293 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:297 msgid "**Trigger Another Rule**: the system tries to find a stock rule to bring the products to the source location. The available stock is ignored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:296 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:300 msgid "**Take From Stock, if Unavailable, Trigger Another Rule**: the products are taken from the available stock of the source location. If there is no stock available, the system tries to find a rule to bring the products to the source location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:301 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:305 msgid "In the *Scheduling* section, you can determine how Odoo behaves when one of the chain's pickings is rescheduled. In case you decide to **Propagate Rescheduling**, the next move is also to be rescheduled. If you prefer having the choice to reschedule the next move, you can decide to receive an alert in the form of a *next activity*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:309 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:313 msgid "What about a full flow?" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:311 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:315 msgid "Do you remember our Pick - Pack - Ship custom route? Let’s use it to try a full flow with an advanced custom route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:314 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:318 msgid "First, a quick look at our rules and their supply methods: we have three rules, all **Pull From** rules. The supply methods are the following:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:318 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:322 msgid "**Take From Stock**: When products are needed in WH/Packing Zone, *Picks* (internal transfers from WH/Stock to WH/Packing Zone) are created from WH/Stock to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:321 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:325 msgid "**Trigger Another Rule**: When products are needed in WH/Output, *Packs* (internal transfers from WH/Packing Zone to WH/Output) are created from WH/Packing Zone to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:324 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:328 msgid "**Trigger Another Rule**: When products are needed in Partner Locations/Customers, Delivery Orders are created from WH/Output to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "overview of all the transfers created by the pick - pack - ship route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:332 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:336 msgid "This means that, when a customer orders products, a delivery order is created to fulfill the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the operations created by a pull from transfer" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:340 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:344 msgid "If the source document is the same sale order, the status is not the same. In fact, the status is **Waiting Another Operation** if the previous transfer in the list is not done yet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the transfers various status at the beginning of the process" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:348 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:352 msgid "To prepare the order, conveyors need products packed at the output area, so an internal transfer is requested from the packing zone." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the detailed operations for a transfer between the packing and output zones" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:355 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:359 msgid "Obviously, the packing zone needs products ready to be packed. So, an internal transfer is requested to the stock and employees can gather the required products from the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the detailed operations for a transfer between the stock and packing zones" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:363 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:367 msgid "As explained in this documentation introduction, the last step in the process (here the delivery order) is the first to be triggered, which then triggers other rules until we reach the first step in the process (here, the internal transfer from to stock to the packing area). Now, everything is ready to be processed so the customer can get the ordered items." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:370 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:374 msgid "In our case, the product is delivered to the customer when all the rules have been triggered and the transfers done." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:-1 msgid "view of the transfers' status when all the process is done" msgstr "" @@ -3007,43 +4567,221 @@ msgid "Putaway & Removal Strategies" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:3 -msgid "What is a Putaway Rule?" +msgid "Putaway rules" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:5 -msgid "A good warehouse implementation takes care that products automatically move to their appropriate destination location. To make that process easier, Odoo uses *Putaway rules*. But what is a putaway rule? Putaway is the process of taking products off the receiving shipments and directly putting them into the most appropriate location." +msgid "Putaway is the process of routing products to appropriate storage locations upon shipment arrival. Odoo can accomplish this seamlessly using *putaway rules*, which dictate how products move through specified warehouse locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:10 -msgid "If, for example, a warehouse contains volatile substances, it is important to make sure that certain products are not stored close to each other because of a potential chemical reaction. That’s where putaway rules intervene, to avoid storing products wrongly." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:9 +msgid "Upon shipment arrival, operations are generated based on putaway rules to efficiently move products to specified locations and ensure easy retrieval. Putaway rules can also prevent volatile substances from being stored in close proximity by directing them to different locations determined by the warehouse manager." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:17 -msgid "In the *Inventory* app, go to :menuselection:`Configuration --> Settings` and activate the *Multi-Step Routes*. By doing so, the *Storage Locations* will be automatically activated." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:15 +msgid ":ref:`How push rules work `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:24 -msgid "Setting up a Putaway Rule" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:16 +msgid ":ref:`Warehouse locations `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:26 -msgid "In some cases, like for a retail shop storing vegetables and fruits, we have to store products in different locations to maintain product quality." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:19 +msgid "Enable putaway rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:29 -msgid "Let’s suppose there are one warehouse location *WH/Stock* and two sub-locations *WH/Stock/Vegetables* and *WH/Stock/Fruits*." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:21 +msgid "Begin by navigating to :menuselection:`Inventory app --> Configuration --> Settings`, then activate the :guilabel:`Multi-Step Routes` checkbox under the :guilabel:`Warehouse` heading. By doing so, the :guilabel:`Storage Locations` setting is automatically enabled as well. Finally, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:32 -msgid "To manage those locations, we will create putaway rules. To do so, open the *Inventory* app and go to :menuselection:`Configuration --> Putaway Rules`. Then, click on create and configure your first rule indicating the main location the product will enter before being redirected to the right location." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 +msgid "In configs, for the Inventory app, check multi-step routes box to enable Putaway rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:38 -msgid "The putaway rules can be defined either per product or per product category." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:31 +msgid "Put away products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:43 -msgid "Now, if I purchase apples and carrots to my supplier, they will be grouped in the same receipt but redirected to the right location automatically, thanks to putaway rules. This information is available from *Inventory Report*, under the reporting menu." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:33 +msgid "Putaway rules are commonly used to move products to specific locations for easy retrieval. Thus, products are grouped in the same *product category* when a single putaway rule captures the group's storage needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:37 +msgid "To manage where specific products are routed for storage, navigate to :menuselection:`Inventory app --> Configuration --> Putaway Rules`. Use the :guilabel:`Create` button to configure a new putaway rule on a :guilabel:`Product` or :guilabel:`Product Category` that the rule affects." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:41 +msgid "In the same line, the :guilabel:`When product arrives in` location is where the putaway rule is triggered to create an operation to move the product to the :guilabel:`Store to` location. The :guilabel:`Store to` location must be a sublocation of the first (e.g. `WH/Stock/Fruits` is a specific, named location inside `WH/Stock` to make the products stored here easier to find)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:47 +msgid "Ensure all apples are stored in the fruits section by filling the field :guilabel:`Store to` with the location `WH/Stock/Fruits` when the :guilabel:`Product`, `Apple` arrives in `WH/Stock`. Repeat this for all products and hit :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Create putaway rules for apples and carrots." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:56 +msgid "It is also possible to create and manage putaway rules for a single product by going to the product page and clicking the :guilabel:`Putaway Rules` smart button at the top of the page. If the button is not visible at first glance, select the :guilabel:`More` button at the top right to view additional smart buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:64 +msgid "Check whether putaway rules work as intended using the summary of internal product movements. In the :menuselection:`Inventory` app, select :menuselection:`Reporting --> Product Moves` and enable the :guilabel:`Internal` search filter on the :guilabel:`Filters` drop-down menu under the search bar at the top of the page. In this view, confirm that products are moved to the :guilabel:`Store to` location detailed in the putaway rule. More details in :ref:`this section `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:72 +msgid "Use putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:74 +msgid "Once a putaway rule is configured, the product it specifies is automatically routed to the :guilabel:`Store to` location upon arriving in the :guilabel:`When product arrives in` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:77 +msgid "For example, on a putaway rule with the :guilabel:`When product arrives in` location set to `WH/Stock`, internal stock moves are automatically created when products first enter the warehouse. To trigger this putaway rule, begin by creating a :ref:`purchase order ` (PO) to bring products into the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:82 +msgid "To create a :guilabel:`Request for Quotation` (RFQ), go to the :menuselection:`Purchase` app, and click :guilabel:`Create`. Then, add products to the :abbr:`RFQ (Request for Quotation)` by clicking :guilabel:`Add a line`, and selecting the desired product(s) from the drop-down menu in the :guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:87 +msgid "Once ready, click :guilabel:`Confirm`. Doing so turns the :abbr:`RFQ (Request for Quotation)` into a :abbr:`PO (Purchase Order)`. Next, click :guilabel:`Send by Email` to send the :abbr:`PO (Purchase Order)` to the vendor, if needed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 +msgid "View purchase order for apples and carrots." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:95 +msgid "Begin receiving the incoming shipment by selecting the :guilabel:`Receipt` smart button on the :abbr:`PO (Purchase Order)`. Click :guilabel:`Receive products` and then :guilabel:`Validate` to move products into the warehouse. Since the putaway rule is set to trigger when products arrive in stock, internal transfers are automatically created when products arrive in the :guilabel:`Destination Location`, `WH/Stock`. This ensures products entering the warehouse are stored in specific locations suitable for their storage needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 +msgid "In the WH reception operation, receive package of apples and carrots." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:107 +msgid "Verify stock moves" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:109 +msgid "Confirm whether the putaway rule worked as intended and that the products have been moved to the correct location using the :guilabel:`Stock On Hand` dashboard. View all products in stock in :menuselection:`Inventory app --> Reporting --> Inventory Report`. By default, the products are grouped by location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:114 +msgid "Select a product's collapsable drop-down menu, which displays the current location(s) of the product. Then, select a :guilabel:`Location` drop-down menu to view a list of all stock movements in and out of each location. Each of these lines are records of a stock move, called a *stock move line*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 +msgid "Verify stock moves triggered by putaway rule in the Inventory Report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:126 +msgid "Trace products in wrong locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:128 +msgid "To trace products and associated documents for warehouse operations, use the :guilabel:`Product Moves` report in :menuselection:`Inventory app --> Reporting --> Product Moves`. View a product's warehouse operation history by selecting a product's drop-down menu. Each stock move line contains details about any movement of stock, such as manufacturing orders, inventory adjustments, or internal transfers. Click on a stock move line to view all the information in a comprehensive report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:135 +msgid "The stock move line is useful because the :guilabel:`Reference` displays the warehouse operation associated to the :guilabel:`Product`. Use the :guilabel:`From` and :guilabel:`To` location and associated :guilabel:`Source` documents to trace the product path and identify the type of operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:141 +msgid "It is also possible to view the stock moves of a product directly from the product page. Open the desired product page by navigating to :menuselection:`Inventory --> Products --> Products` and select the product. From there, click on the :guilabel:`Product Moves` smart button, then click the product's collapsable drop-down menu from the list. This displays the stock moves history of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:150 +msgid "A putaway rule was purposely set up incorrectly on `Apple`, so the product was moved from `WH/Stock` to `WH/Stock/Shelf 1` instead of the expected location, `WH/Stock/Fruits`. To trace the path the apple moved and identify the cause of the wrong stock move, open the :guilabel:`Product Moves` report in :menuselection:`Inventory app --> Reporting --> Product Moves`. The apple's drop-down menu, when opened, displays a list of stock moves of the apple. line to open a report that is useful to trace the path the product moved and identify the cause of the wrong stock move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:158 +msgid "The :guilabel:`To` field displays where the product currently is, `WH/Stock/Shelf 1`, which is the wrong location. The :guilabel:`From` location is the vendor's location, which is expected since the :guilabel:`Source` of the stock move is a :abbr:`PO (Purchase Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:162 +msgid "The :guilabel:`Reference` operation, `WH/IN/00015`, which is a warehouse reception of products from the vendor, would further explain why the apples were moved to the wrong location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Open stock move report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:169 +msgid "To follow an operation identified from the :guilabel:`Product Moves` report, navigate to :menuselection:`Inventory --> Operations --> Transfers`. This is the page that displays all warehouse transfers— internal or external. Search for and click on the corresponding :guilabel:`Reference` operation to view the document explaining why the product was moved to the wrong location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:176 +msgid "When there are too many records, use either the :guilabel:`Filters` or :guilabel:`Group by` features to sort and :ref:`find desired records `. It is useful to search exclusively for the receipt operation type because putaway rules store products *into* a specific stock location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:183 +msgid "Continuing to diagnose why the product, `Apple`, was placed in `WH/Stock/Shelf 1`, navigate to the list of all transfers in :menuselection:`Inventory --> Operations --> Transfers`. Click on the list item where the :guilabel:`Reference` field matches the `WH/IN/00015` operation identified in the :ref:`previous example ` to open the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "In the Transfers page in the Inventory app, select the desired transfer to view the\n" +"record." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:194 +msgid "This receipt describes which products were received from the supplier, with the affiliated :abbr:`PO (Purchase Order)` linked in the :guilabel:`Source Document` field. On the warehouse reception document, the field :guilabel:`Destination Location` shows where the product is received upon entering the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:199 +msgid "Clicking on the :guilabel:`≣ (Detailed Operations)` icon to the right of the product line opens a window that shows the product was moved to the wrong location. Based on this information it can be gathered that the putaway rule was triggered but the location was set incorrectly. Rectify this in :menuselection:`Inventory --> Configuration --> Putaway Rules`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Click Detailed Operations button on the right of warehouse transfers page to the right\n" +"of the WH reception document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Show putaway rule in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:216 +msgid "Advanced filter search" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:218 +msgid "Keep track of and trace products on the :guilabel:`Product Moves` report by navigating to :menuselection:`Inventory app --> Reporting --> Product Moves` and use the :guilabel:`Filters` and :guilabel:`Group by` features to stay updated on warehouse operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:222 +msgid "Transfers based on putaway rules can be found by toggling on the :guilabel:`Internal` filter as mentioned in this :ref:`tip ` previously. Other useful filters and groupbys intended for reporting on the company's internal operations include:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:227 +msgid "Filter by :guilabel:`Incoming` and :guilabel:`To Do` to display shipments from vendors yet to be processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Filter warehouse transfer records by Incoming shipments and processes ToDo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:234 +msgid "Use custom filters to search for a specific product by its name, :ref:`lot/serial number ` or barcode. Create a custom filter by clicking on :guilabel:`Filters`. Click :guilabel:`Add Custom Filter`, fill in the identifying information, and click :guilabel:`Apply`. Now that the custom filter is active, click on the :guilabel:`Filters` button again to create any additional filters." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:239 +msgid "Group by :guilabel:`Date`: View all product moves on a specific date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:240 +msgid "Group by :guilabel:`From`: Create a custom filter that displays all locations that currently store at least 1 product. This is useful to view all the locations and sublocations to optimize storage space." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:243 +msgid ":guilabel:`Favorite` the current search with filters applied. This feature is useful to apply the filters promptly, especially if this search is often used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Use the star button under the search bar to save current search as a favorite view." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:3 @@ -3066,7 +4804,7 @@ msgstr "" msgid "Imagine a generic warehouse plan, with receiving docks and area, storage locations, picking and packing areas, and shipping docks. All products go through all these locations, but some rules, such as removal strategies, can have an effect on which products are taken for the pickings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "empty stock waiting for deliveries at the docks." msgstr "" @@ -3074,7 +4812,7 @@ msgstr "" msgid "Here, vendor trucks unload pallets of goods at the docks. Then, operators scan the products in the receiving area, with the receiving date and, if the product has an expiration date, the expiration date. After that, products are stored in their respective locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "products entering stock via the receiving area." msgstr "" @@ -3082,7 +4820,7 @@ msgstr "" msgid "Next, several orders for the same product are made, but you didn’t receive the goods the same day and they don’t have the same expiration date. In that situation, you logically prefer sending those with the closest date first. Depending on the removal strategy you chose, Odoo generates a transfer with the products fitting your settings the best." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "products being packed at packing area for delivery, taking expiration dates into account." msgstr "" @@ -3150,7 +4888,7 @@ msgstr "" msgid "To identify some units from other ones, you need to track them, either by *lot* or by *serial number*. To do so, go to :menuselection:`Configuration --> Settings`. Then, activate *Storage Location*, *Multi-Steps Routes*, and *Lots & Serial Numbers*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "features to enable in order to properly use removal strategies." msgstr "" @@ -3162,7 +4900,7 @@ msgstr "" msgid "Next, you need to define your removal strategy, on *Product Categories* via :menuselection:`Inventory --> Configuration --> Product Categories`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "force removal strategy set up as first in first out." msgstr "" @@ -3178,7 +4916,7 @@ msgstr "" msgid "For this example, we created three lots of white shirts. Those are from the All/Clothes category, where we put *FIFO* as the removal strategy. In our stock location (WH/Stock), we now find the three lots available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "view of the white shirt lots inventory valuation." msgstr "" @@ -3190,7 +4928,7 @@ msgstr "" msgid "On the delivery order linked to the picking, you can see that the oldest lot numbers have been reserved thanks to the *FIFO* strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "two lots being reserved for sell with the FIFO strategy." msgstr "" @@ -3206,7 +4944,7 @@ msgstr "" msgid "Even if our white shirts are clothes, we can say that they are timeless. So, let’s use them to test our *LIFO* strategy. Once again, open the product category via :menuselection:`Inventory --> Configuration --> Product Categories` and change the removal strategy to *LIFO*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "last in first out strategy set up as forced removal strategy." msgstr "" @@ -3214,7 +4952,7 @@ msgstr "" msgid "Now, create a sale order for 4 white shirts and check that the reserved products are from lots 000003 and 000002." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "two lots being reserved for sell with the LIFO strategy." msgstr "" @@ -3238,7 +4976,7 @@ msgstr "" msgid "By activating *Expiration Dates*, it becomes possible to define different dates on the serial/lot numbers to be used in *FEFO*. These dates can be set by going to :menuselection:`Inventory --> Master Data --> Lots/Serial Numbers`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "view of the removal date for 0000001." msgstr "" @@ -3254,7 +4992,7 @@ msgstr "" msgid "To use the *FEFO* strategy, once again go to :menuselection:`Inventory --> Configuration --> Product Categories` and choose *FEFO* as the *Force Removal Strategy*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "view of the FEFO strategy being set up as forced removal strategy." msgstr "" @@ -3308,7 +5046,7 @@ msgstr "" msgid "When we realize a sale for 25 units of Hand Cream, we can see that the lot numbers which have been automatically reserved by Odoo are the ones with the closest expiration date, meaning 0000001 and 0000003." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "two hand cream lots reserved for sell with the FEFO strategy." msgstr "" @@ -3375,6 +5113,86 @@ msgstr "" msgid ":doc:`multipack`" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:3 +msgid "Use dropshipping to ship directly from suppliers to customers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:5 +msgid "Dropshipping is an order fulfillment strategy that allows sellers to have items shipped directly from suppliers to customers. Normally, a seller purchases a product from a supplier, stores it in their inventory, and ships it to the end customer once an order is placed. With dropshipping, the supplier is responsible for storing and shipping the item. This benefits the seller by reducing inventory costs, including the price of operating warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:12 +msgid "Configure products to be dropshipped" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:14 +msgid "To use dropshipping as a fulfillment strategy, navigate to the :menuselection:`Purchase` app and select :menuselection:`Configuration --> Settings`. Under the :guilabel:`Logistics` heading, click the :guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:18 +msgid "Next, go to the :menuselection:`Sales` app, click :menuselection:`Products --> Products` and choose an existing product or select :guilabel:`Create` to configure a new one. On the :guilabel:`Product` page, make sure that the :guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 +msgid "Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:27 +msgid "Click on the :guilabel:`Purchase` tab and specify a vendor and the price that they sell the product for. Multiple vendors can be added, but the vendor at the top of the list will be the one automatically selected for purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 +msgid "The product form with a vendor specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:35 +msgid "Finally, select the :guilabel:`Inventory` tab and enable the :guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 +msgid "Enable the Dropship option in the product inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:43 +msgid "Fulfill orders using dropshipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:45 +msgid "When a customer completes an online purchase for a dropshipped product, a sales order will be automatically created with an associated request for quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. Sales orders can be viewed in the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart button at the top right of a sales order to view the associated :abbr:`RFQ (Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:52 +msgid "Dropship sales orders can also be created manually through the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders --> Create` and adding a product configured for dropshipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 +msgid "A dropship sales order with the Purchase smart button in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:60 +msgid "Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a purchase order and a dropship receipt is created and linked to it. The receipt can be viewed by clicking the :guilabel:`Receipt` smart button in the top right corner of the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 +msgid "A dropship purchase order with the Receipt smart button in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:68 +msgid "The dropship receipt will list the supplier in the :guilabel:`Receive From` section and the customer in the :guilabel:`Destination Location` section. Upon delivery of the product to the customer, click on the :guilabel:`Validate` button at the top left of the dropship receipt to confirm the delivered quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 +msgid "Validate the dropship receipt after delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:77 +msgid "To view all dropship orders, simply navigate to the :menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 +msgid "Click the green button on the Dropship card to view all dropship orders." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:3 msgid "How to invoice the shipping cost to the customer?" msgstr "" @@ -3462,6 +5280,78 @@ msgstr "" msgid ":doc:`labels`" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:3 +msgid "Change shipping label size" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:8 +msgid "In Odoo, there are a variety of different types of shipping labels that can be selected for delivery orders. Depending on the types of shipping packages used, different label sizes may be more appropriate, and can be configured to fit the package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:15 +msgid "In the :menuselection:`Inventory` module, go to :menuselection:`Configuration --> Delivery --> Shipping Methods.` Choose a delivery method and click :guilabel:`Edit`. For the following example, *FedEx International* will be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 +msgid "Different shipping methods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:23 +msgid "In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose one of the label types available. The availability will vary depending on the carrier. :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 +msgid "Select a label type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:30 +msgid "When a sales order with the corresponding shipping company is confirmed and a delivery order is validated, the shipping label will be automatically created as a PDF and appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:37 +msgid "In the :menuselection:`Sales` application, click :guilabel:`Create` and select an international customer. Click :guilabel:`Add A Product` and select an item. Click :guilabel:`Add Shipping`, select a shipping method, then click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 +msgid "Add a shipping method and rate to a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:45 +msgid "Once the quotation is confirmed by clicking :guilabel:`Confirm`, a :guilabel:`Delivery` smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 +msgid "Delivery order smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:52 +msgid "Once the delivery order is validated by clicking :guilabel:`Validate` in the delivery order, the shipping documents appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 +msgid "Shipping PDF documents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:60 +msgid "Example labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:62 +msgid "The default :guilabel:`Label Type` is :guilabel:`Paper Letter`. An example of a FedEx letter sized label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 +msgid "Full page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:69 +msgid "For comparison, an example of a FedEx bottom-half label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 +msgid "Half page letter size FedEx shipping label." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:3 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:85 msgid "How to print shipping labels?" @@ -3538,6 +5428,11 @@ msgstr "" msgid "To check your information, go to the **Settings** application and click on **General Settings**. Click on the first link **Configure your company data**." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:90 +msgid "Product configuration" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:70 #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:92 msgid "The shipper companies need the weight of your product, otherwise the price computation cannot be done." @@ -3975,140 +5870,284 @@ msgstr "" msgid ":doc:`IoT Boxes (MES) `" msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance.rst:5 +msgid "Maintenance" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:3 +msgid "Add new equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:5 +msgid "In Odoo, **equipment** refers to any item that is used in everyday operations, including the manufacturing of products. This can mean a piece of machinery on a production line, a tool that is used in different locations, or a computer in an office space. Equipment registered in Odoo can be owned by the company that uses the Odoo database, or by a third party, such as a vendor in the case of equipment rentals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:11 +msgid "Using Odoo **Maintenance**, it is possible to track individual pieces of equipment, along with information about their maintenance requirements. To add a new piece of equipment, navigate to the :guilabel:`Maintenance` module, select :menuselection:`Equipments --> Machines & Tools --> Create`, and configure the equipment as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:16 +msgid ":guilabel:`Equipment Name`: the product name of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:17 +msgid ":guilabel:`Equipment Category`: the category that the equipment belongs to; for example, computers, machinery, tools, etc.; new categories can be created by navigating to :menuselection:`Configuration --> Equipment Categories` and clicking :guilabel:`Create`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:20 +msgid ":guilabel:`Company`: the company that owns the equipment; again, this can be the company that uses the Odoo database, or a third-party company" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:22 +msgid ":guilabel:`Used By`: specify if the equipment is used by a specific employee, department, or both; select :guilabel:`Other` to specify both an employee and a department" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:24 +msgid ":guilabel:`Maintenance Team`: the team responsible for servicing the equipment; new teams can be created by navigating to :menuselection:`Configuration --> Maintenance Teams` and selecting :guilabel:`Create`; the members of each team can also be assigned from this page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:27 +msgid ":guilabel:`Technician`: the person responsible for servicing the equipment; this can be used to assign a specific individual in the event that no maintenance team is assigned or when a specific member of the assigned team should always be responsible for the equipment; any person added to Odoo as a user can be assigned as a technician" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:31 +msgid ":guilabel:`Used in location`: the location where the equipment is used; this is a simple text field that can be used to specify locations that are not work centers, like an office, for example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:34 +msgid ":guilabel:`Work Center`: if the equipment is used at a work center, specify it here; equipment can also be assigned to a work center by navigating to :menuselection:`Maintenance --> Equipments --> Work Centers`, selecting a work center or creating a new one using the :guilabel:`Create` button, and clicking the :guilabel:`Equipment` tab on the work center form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:-1 +msgid "An example of a fully configured new equipment form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:44 +msgid "Include additional product information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:46 +msgid "The :guilabel:`Product Information` tab at the bottom of the form can be used to provide further details about the piece of equipment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:49 +msgid ":guilabel:`Vendor`: the vendor that the equipment was purchased from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:50 +msgid ":guilabel:`Vendor Reference`: the reference code assigned to the vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:51 +msgid ":guilabel:`Model`: the specific model of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:52 +msgid ":guilabel:`Serial Number`: the unique serial number of the equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:53 +msgid ":guilabel:`Effective Date`: the date that the equipment became available for use; this is used to calculate the :abbr:`MTBF (Mean Time Between Failures)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:55 +msgid ":guilabel:`Cost`: the amount the equipment was purchased for" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:56 +msgid ":guilabel:`Warranty Expiration Date`: the date on which the equipment's warranty will expire" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:-1 +msgid "The product information tab for the new piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:63 +msgid "Add maintenance details" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:65 +msgid "The :guilabel:`Maintenance` tab includes information that can be useful to maintenance teams:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:67 +msgid ":guilabel:`Preventive Maintenance Frequency`: specifies how often maintenance should be performed to prevent equipment failure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:69 +msgid ":guilabel:`Maintenance Duration`: the amount of time required to fix the equipment when it fails" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:70 +msgid ":guilabel:`Expected Mean Time Between Failure`: the average amount of time that the equipment is expected to operate before failing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:-1 +msgid "The maintenance tab for the new piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:78 +msgid "The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean Time Between Failure`, :guilabel:`Estimated Next Failure`, :guilabel:`Latest Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated automatically based on maintenance requests if any exist." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:84 +msgid "To see the maintenance requests for a piece of equipment, go to the page for the equipment and select :guilabel:`Maintenance` in the top right corner of the form." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/management.rst:5 msgid "Manufacturing management" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:3 -msgid "Using an alternative Work Center" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:5 -msgid "For many manufacturing companies, a common issue is to have to manufacture, at the same time, several products usually produced at the same work center. If in practice, employees can manufacture the goods at another work center, it is not that simple." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:10 -msgid "You need to keep track of the job: which work center has been used and when, so you can schedule maintenance efficiently. With Odoo, you can configure it so you can keep tracking manufacturing orders and your employees have an alternative work center to use." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:15 -msgid "This way, your process becomes more efficient, and less non-productive time will be noticed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:20 -msgid "Configure your Work Centers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:22 -msgid "The first thing to do is to go to the *Manufacturing* app settings. Then, enable the *Work Orders* feature and hit save." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:30 -msgid "Now, go to the *Work Centers* menu under *Master Data* and create two new work centers. Add the second work centers as an alternative to the first and vice versa." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:39 -msgid "The next step is to create your *routing*. Add your work center and an operation to it before saving." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:47 -msgid "Then, you can create your *Bill of Materials* and add components and routing to it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:56 -msgid "Create your Work Orders" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:58 -msgid "Now that everything is configured, you can create your *Work Orders*. Go to the *Manufacturing Orders* menu and hit *Create*. There, add your product and plan it. In the *Work Orders* list, you can find it ready to be assembled." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:68 -msgid "Each new *Work Order*, which will be created before the end of the first one, will be scheduled at the alternative work center you configured." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:78 -msgid "Keep in mind that, if you add time after production to your work center, you may have work orders scheduled for your alternative work center even if the usual one is free." -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:3 -msgid "Create Bills of Materials" +msgid "Create a bill of materials (BoM)" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:5 -msgid "A *Bill of Materials* is a document defining the quantity of each component required to manufacture a finished product. It also includes the routing and individual steps of the manufacturing process." +msgid "A *bill of materials* (or *BoM*) is a document that defines the quantity of each component required to manufacture (or deliver) a finished product. It can also include various operations types, steps, and instructions for the individual guidelines needed to complete a production process." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:9 -msgid "With Odoo, you can link multiple BoMs to each product and use it to describe multiple variants of them. Each BoM will, yet, be associated with one product only." +msgid "In Odoo *Manufacturing*, multiple :abbr:`BoMs (Bills of Materials)` can be linked to a product, so even product variants can have their own specific :abbr:`BoMs (Bills of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:13 -msgid "This feature will help optimize your manufacturing process while saving you time." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:12 +msgid "Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the manufacturing process, and saves time." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:17 -msgid "Setting up a BoM" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:16 +msgid "Set up a BoM" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:19 -msgid "You can use BoMs without routings. You will use this if you choose to manage your manufacturing operations using manufacturing orders only. In other words, you choose to realize your manufacturing process in one step and do not track the steps the product goes through." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 +msgid ":abbr:`BoMs (Bills of Materials)` can be set up with or without operations steps or instructions, and can include as many or as few components as needed. The simplest setup is one without operations or instructions. In that case, the production is solely managed with *manufacturing orders* (MOs)." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:24 -msgid "Before creating your *BoM*, you have to create the product using the *BoM* and, at least, one of the components. Go to the :menuselection:`Master Data menu --> Products` and create both the finished product and the component." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:22 +msgid "To create a :abbr:`BoM (Bill of Materials)`, navigate to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and click :guilabel:`Create`. Then, in the :guilabel:`Product` field, choose the product that will be associated with the :abbr:`BoM (Bill of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:28 -msgid "Once done, go to the *Bills of Materials* menu under *Master Data*. Now, create it. Choose the product from the dropdown menu and add your components and the quantity. In this case, keep the default *BoM* type, which is *Manufacture this Product*." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:-1 +msgid "Bill of materials creation screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:37 -msgid "The destination location should **not** be a scrap location. A scrap location is where you put products that you don't need." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:30 +msgid "There are three :guilabel:`BoM Types` that can be chosen for any bill of materials:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:32 +msgid ":guilabel:`Manufacture this product` indicates that this product is manufactured in-house, from start to finish using the components listed on the :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:34 +msgid ":guilabel:`Kits` are sets of unassembled components that may be sold as products, and are useful for managing more complex :abbr:`BoMs (Bills of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:36 +msgid ":guilabel:`Subcontracting` outsources the production of some (or all) components or products to outside manufacturers. This feature needs to be enabled in :menuselection:`Manufacturing app --> Configuration --> Settings`, under the :guilabel:`Operations` section." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:41 -msgid "Using the same BoM to describe Variants" +msgid "A :abbr:`BoM (Bill of Materials)` can also be created directly from the :abbr:`BoM (Bill of Materials)` smart button on the product template, in which case the :guilabel:`Product` field is pre-filled." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 -msgid "As said above, you can use *BoM* for *Product Variants*. It is basically the same as for the standard product." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:45 +msgid "The most common :guilabel:`BoM Type` is :guilabel:`Manufacture this product`. Once the :guilabel:`BoM Type` is chosen, click :guilabel:`Add a Line` to add all the :guilabel:`Components` that go into the production of the final product, as well as the :guilabel:`Quantity` of each component. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM (Bill of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:46 -msgid "If your *BoM* is for one variant only, then specify which one in the *Product Variant* field. If not, specify the variant it is consumed for on each component line. You can add several variants for each component." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:55 -msgid "Adding a routing" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:51 +msgid "New components can be added, even during production, directly from the :abbr:`BoM (Bill of Materials)`. After selecting :guilabel:`Add a line`, create the new component and select :guilabel:`Create` or :guilabel:`Create and Edit`. Components can also be created by going to :menuselection:`Manufacturing app --> Products --> Products`, and clicking :guilabel:`Create`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:57 -msgid "You can add routing to your *BoM*. You will do this if you need to define a series of operations required by your manufacturing process. To use it, enable the *Work Orders* feature in the *Manufacturing* app settings." +msgid "Specify a BoM for a product variant" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:66 -msgid "Each *BoM* can have only one routing while each routing can be used multiple times." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:60 +msgid "To assign *product variants* to :abbr:`BoMs (Bills of Materials)`, the feature must be enabled in :menuselection:`Inventory --> Configuration --> Settings`, under the :guilabel:`Products` section by selecting :guilabel:`Variants` and clicking :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:69 -msgid "Now that you have created your routing, add it to your *BoM*. You can select when, in the work operations, your components are consumed with the dropdown menu." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:64 +msgid ":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *product variants*, with two setup options available to choose from." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:77 -msgid "Adding By-Products" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:-1 +msgid "Bill of materials product variants and apply on variants options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:71 +msgid "The first method is to create one :abbr:`BoM (Bill of Materials)` per product variant, by specifying the :guilabel:`Product Variant` every time a new :abbr:`BoM (Bill of Materials)` is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:74 +msgid "The second method is to create **one** master :abbr:`BoM (Bill of Materials)` that contains all components, and specify which variant each component applies to in the :guilabel:`Apply on Variants` column." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:79 -msgid "In Odoo, a *by-product* is any product produced by a *BoM* in addition to the primary product." +msgid "`Managing with Product Variants `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:82 -msgid "To add *by-products* to a *BoM*, you will first need to enable them from the *Manufacturing* app settings." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:83 +msgid "The :guilabel:`Apply on Variants` column is hidden by default and can be accessed by clicking on the :guilabel:`Additional Options` menu icon at the right of the :guilabel:`Components` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:88 -msgid "Once the feature is enabled, you can add your *By-Products* to your *BoMs*. You can add as many *By-Products* as you want. Just keep in mind that you need to register during which operation your by-product is produced." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87 +msgid "Set up operations steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:89 +msgid "Some :abbr:`BoMs (Bills of Materials)` require multiple operations and steps during the manufacturing process. To create :guilabel:`Operations` on a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`Work Orders` feature in :menuselection:`Manufacturing app --> Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:-1 +msgid "An example of a Bill of Materials operation and the steps creation tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:98 +msgid "When creating a new :abbr:`BoM (Bill of Materials)`, click the :guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:101 +msgid "In the :guilabel:`Create Operations` box, give the operation a name, and specify the :guilabel:`Work Center` and the :guilabel:`Default Duration` settings. Under the :guilabel:`Work Sheet` tab, the type of :guilabel:`Work Sheet` can also be chosen, if assembly instructions need to be attached." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:105 +msgid "The :guilabel:`Work Sheet` types that can be added are: :guilabel:`Text` (with a :guilabel:`Description`); :guilabel:`PDF` files; and :guilabel:`Google Slide` presentations. When all the information has been filled out, select :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:-1 +msgid "Bill of materials create operations popup on operations tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:114 +msgid "Add by-products to a BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:116 +msgid "A *by-product* is a residual product that is created during production of a :abbr:`BoM (bill of materials)`. Unlike the finished product, there can be more than one by-product on a :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:120 +msgid "To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`By-Products` feature in :menuselection:`Manufacturing app --> Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:123 +msgid "Once the feature is enabled, by-products can be added to a :abbr:`BoM (Bill of Materials)` from the :guilabel:`By-products` tab by clicking :guilabel:`Add a line`. The by-product can be named, its :guilabel:`Quantity` specified, and a :guilabel:`Unit of Measure` chosen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:127 +msgid "If the :abbr:`BoM (Bill of Materials)` has :guilabel:`Operations` steps, specify exactly which operation the by-product is produced from in the :guilabel:`Produced in Operation` field. Finally, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:132 +msgid ":doc:`/applications/inventory_and_mrp/manufacturing/management/kit_shipping`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:133 +msgid ":doc:`/applications/inventory_and_mrp/manufacturing/management/product_variants`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:134 +msgid ":doc:`/applications/inventory_and_mrp/manufacturing/management/routing_kit_bom`" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3 @@ -4659,7 +6698,7 @@ msgstr "" msgid ":guilabel:`Company`: select the company that the work center belongs to" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:None +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 msgid "An example of a fully configured work center form." msgstr "" @@ -4699,7 +6738,7 @@ msgstr "" msgid ":guilabel:`Analytic Account`: the account where the cost of the work center should be recorded" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:None +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 msgid "The general information tab of the work center form." msgstr "" @@ -4735,7 +6774,7 @@ msgstr "" msgid ":guilabel:`Est. Next Failure`: an estimate of when the next equipment failure will occur" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:None +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 msgid "The equipment tab of the work center form." msgstr "" @@ -4743,86 +6782,327 @@ msgstr "" msgid ":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are all calculated automatically based on past failure data, if any exists." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:79 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:81 msgid "Integrate IoT devices" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:81 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 msgid "The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT (Internet of Things)` devices with a work center:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:84 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:86 msgid ":guilabel:`Device`: specifies the IoT device to be triggered" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:87 msgid ":guilabel:`Key`: the security key for the device" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 msgid ":guilabel:`Action`: the IoT device action triggered" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:None +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 msgid "The IoT Triggers tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:93 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:95 msgid "Use case: configure an alternative work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:95 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 msgid "When a work center is at capacity, it cannot accept any new work orders. Instead of waiting for the work center to become available, it is possible to specify an alternative work center where surplus work orders should be carried out." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:99 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:101 msgid "Begin by creating a new work center. Configure the :guilabel:`Equipment` tab so that it has all of the same equipment as the main work center. This will ensure that the same tasks can be carried out at both work centers. Navigate to the main work center and include the new work center in the :guilabel:`Alternative Workcenters` selection field." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:104 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:106 msgid "Now, create a new manufacturing order that uses the main work center for one of its operations. The main work center will automatically be selected for the operation in the :guilabel:`Work Orders` tab. After confirming the manufacturing order, click the :guilabel:`Plan` button that appears at the top left of the form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:None +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 msgid "Click the plan button to automatically select an available work center." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:113 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:115 msgid "If the main work center is at capacity, the work center selected for the operation will be automatically changed to the alternative work center." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:None +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 msgid "The alternative work center is automatically selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:121 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:123 msgid "Monitor work center performance" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 msgid "Performance for an individual work center can be viewed by selecting :menuselection:`Configuration --> Work Centers`, and clicking on a work center. A variety of metrics showing work center performance can be viewed at the top right of the form:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:127 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:129 msgid ":guilabel:`OEE`: overall effective efficiency, the percentage of time that the work center has been fully productive" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:129 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:130 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:132 msgid ":guilabel:`Load`: the amount of time it will take to complete the current workload" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 msgid ":guilabel:`Performance`: the real duration of work time, shown as a percentage of the expected duration" msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:3 +msgid "Make work centers unavailable using Time Off" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:5 +msgid "In Odoo, *work centers* are used to carry out manufacturing operations at specific locations. However, if a work center cannot be used for some reason, work orders begin to pile up at the work center until it is operational again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:9 +msgid "As a result, it is necessary to make the work center unavailable in Odoo so that the platform routes new work orders to alternative work centers that are operational. Using Odoo *Time Off*, it is possible to designate a work center as being unavailable for a set period of time. Doing so ensures that manufacturing operations can continue until the impacted work center is available again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:17 +msgid "Before a work center can be designated as unavailable, the Odoo platform must be properly configured. First, it is necessary to enable :ref:`developer mode `. This allows the :guilabel:`Time Off` smart button to appear on each work center's :guilabel:`Working Hours` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:22 +msgid "Enable developer mode by going to :menuselection:`Settings`, scrolling to the bottom of the page, and clicking :guilabel:`Activate the developer mode` under the :guilabel:`Developer Tools` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "The \"Activate the developer mode\" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:29 +msgid "Next, install the *Time Off* app. This is the app used for assigning time off to all resources within Odoo, including employees and work centers. Navigate to :menuselection:`Apps`, then type `Time Off` in the :guilabel:`Search...` bar. The card for the :guilabel:`Time Off` module should be the only one that appears on the page. Click the green :guilabel:`Install` button on the card to install the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "The Time Off module installation card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:39 +msgid "The last step is to properly configure work centers. For this workflow, it is necessary to have at least two work centers: one that is made unavailable and a second that receives the work orders that the other cannot accept. If no second work center is configured, Odoo cannot route work orders away from the unavailable work center and they will pile up in its queue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:44 +msgid "To create a work center, navigate to :menuselection:`Manufacturing --> Configuration --> Work Centers --> Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:47 +msgid "Make sure that both work centers have the same equipment listed under the :guilabel:`Equipment` tab. This ensures that operations carried out at one work center can also be performed at the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "The equipment tab on a work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:54 +msgid "For the work center that will be made unavailable, select the second work center on the :guilabel:`Alternative Workcenters` drop-down menu. Now, Odoo knows to send work orders to the second work center when the first is unavailable for any reason." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "A work center form configured with an alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:63 +msgid "Add time off for a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:65 +msgid "With configuration completed, time off can now be assigned to the work center that will be made unavailable. Begin by navigating to :menuselection:`Manufacturing --> Configuration --> Work Centers` and selecting the affected work center. Click :guilabel:`Edit`, and then the :guilabel:`↗ (external link)` button next to the :guilabel:`Working Hours` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "The Working Hours \"External link\" button on the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:74 +msgid "A pop-up appears, titled :guilabel:`Open: Working Hours`. The standard working hours for the work center are listed here, along with various other details about it. Since developer mode was enabled, there is a :guilabel:`Time Off` button in the top right of the pop-up. Click it to be taken to the :guilabel:`Resource Time Off` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "The Time Off button on the Working Hours pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:83 +msgid "On this page, click :guilabel:`Create` to configure a new time-off entry. On the time-off form, note the :guilabel:`Reason` for the work center closure (broken, maintenance, etc.), select the affected work center as the :guilabel:`Resource`, and choose a :guilabel:`Start Date` and :guilabel:`End Date` to specify the period during which the work center will be unavailable. Click :guilabel:`Save` and the time off for the work center is logged in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "The \"Resource Time Off\" form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:94 +msgid "Route orders to an alternative work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:96 +msgid "Once a work center is within its specified time-off period, work orders sent to it can be automatically routed to an alternative work center using the :guilabel:`Plan` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:99 +msgid "Begin by creating a new manufacturing order by selecting :menuselection:`Operations --> Manufacturing Orders --> Create`. On the manufacturing order form, specify a :guilabel:`Product` that uses the unavailable work center for one of its operations. Click :guilabel:`Confirm` to confirm the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:104 +msgid "On the confirmed work order, select the :guilabel:`Work Orders` tab. By default, the unavailable work center is specified in the :guilabel:`Work Center` column. There is also a green :guilabel:`Plan` button on the top left of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "The Plan button on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:112 +msgid "Click :guilabel:`Plan` and the work center listed under the :guilabel:`Work Orders` tab is automatically changed to the alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 +msgid "The selected work center updates automatically after clicking the Plan button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:119 +msgid "Once the time-off period for the unavailable work center ends, Odoo recognizes that the work center is available again. At this point, clicking the :guilabel:`Plan` button does not route work orders to an alternative work center unless the first one is at capacity." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/quality_control.rst:5 msgid "Quality control" msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:3 +msgid "Create quality alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:5 +msgid "Configuring quality control points is a great way to ensure that quality checks are performed at routine stages during specific operations. However, quality issues can often appear outside of these scheduled checks. Using Odoo *Quality*, users can create quality alerts for issues that are not detected by automated processes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:11 +msgid ":doc:`Add quality control points `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:14 +msgid "Find and fill out the quality alerts form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:16 +msgid "In some situations, it is necessary to manually create quality alerts within the *Quality* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:19 +msgid "A helpdesk user who is notified of a product defect by a customer ticket can create an alert that brings the issue to the attention of the relevant quality team." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:22 +msgid "To create a new quality alert, start from the :menuselection:`Quality` module and select :menuselection:`Quality Control --> Quality Alerts --> Create`. The quality alert form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:26 +msgid ":guilabel:`Title`: choose a concise, yet descriptive title for the quality alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:27 +msgid ":guilabel:`Product`: the product about which the quality alert is being created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:28 +msgid ":guilabel:`Product Variant`: the specific variant of the product that has the quality issue, if applicable" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:30 +msgid ":guilabel:`Lot`: the lot number assigned to the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:31 +msgid ":guilabel:`Work Center`: the work center where the quality issue originated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:32 +msgid ":guilabel:`Picking`: the picking operation during which the quality issue originated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:33 +msgid ":guilabel:`Team`: the quality team that will be notified by the quality alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:34 +msgid ":guilabel:`Responsible`: the individual responsible for managing the quality alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:35 +msgid ":guilabel:`Tags`: classify the quality alert based on user-created tags" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:36 +msgid ":guilabel:`Root Cause`: the cause of the quality issue, if known" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:37 +msgid ":guilabel:`Priority`: assign a priority between one and three stars to ensure more urgent issues are prioritized" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:40 +msgid "The tabs at the bottom of the form can be used to provide additional information to quality teams:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:42 +msgid ":guilabel:`Description`: provide additional details about the quality issue" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:43 +msgid ":guilabel:`Corrective Actions`: the method for fixing affected products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:44 +msgid ":guilabel:`Preventive Actions`: procedures for preventing the issue from occurring in the future" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:46 +msgid ":guilabel:`Miscellaneous`: the product vendor (if applicable), the company that produces the product, and the date assigned" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:-1 +msgid "An example of a completed quality alert form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:54 +msgid "Add quality alerts during the manufacturing process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:56 +msgid "Odoo enables manufacturing employees to create quality alerts within a work order without accessing the *Quality* module. From the work order tablet view, click the :guilabel:` ☰ ` hamburger menu icon in the top left corner and select :guilabel:`Quality Alert`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:-1 +msgid "Access the work order menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:64 +msgid "The quality alert form can then be filled out as detailed in the previous section. After saving the form, a new alert will appear on the :guilabel:`Quality Alerts` dashboard that can be found through the :menuselection:`Quality --> Quality Control` menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:69 +msgid "Manage existing quality alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:71 +msgid "By default, quality alerts are organized in a kanban board view. The stages of the kanban board are fully configurable and alerts can be moved from one stage to the next by dragging and dropping or from within each alert. Additional options are available for viewing alerts, including graph, calendar, and pivot table views." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:77 +msgid "Filter alerts based on diverse criteria like date assigned or date closed. Alerts can also be grouped by quality team, root cause, or other parameters found under the :guilabel:`Filters` button menu." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:3 msgid "Add quality controls" msgstr "" @@ -4875,10 +7155,6 @@ msgstr "" msgid ":guilabel:`Responsible`: add a point person to manage the status and evolution of the quality control point over time" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:40 -msgid "The tabs at the bottom of the form can be used to provide additional information to quality teams:" -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:42 msgid ":guilabel:`Instructions`: describe the quality check to be performed" msgstr "" @@ -4891,7 +7167,7 @@ msgstr "" msgid ":guilabel:`Notes`: use to include any additional information" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:None +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:-1 msgid "An example of a completed quality control point form for a Pass-Fail test." msgstr "" @@ -4923,7 +7199,7 @@ msgstr "" msgid ":guilabel:`Tolerance`: select the range that a measurement can be within while still passing the check (e.g., :guilabel:`from` 59.5 mm :guilabel:`to` 60.5 mm)" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:None +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:-1 msgid "An example of a quality control point form configured for a measure quality check." msgstr "" @@ -4967,7 +7243,7 @@ msgstr "" msgid "Go to *Reporting* to access the purchase analysis. Simply by accessing the reporting dashboard, you can get a quick overview of your actual performance. By default, the reporting dashboard displays a line chart presenting the untaxed amount of your purchase orders per day, and below it, key metrics and a pivot table." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 msgid "Reporting dashboard in Odoo Purchase" msgstr "" @@ -5011,7 +7287,7 @@ msgstr "" msgid "If you use the *Order Date* or *Confirmation Date* filters, the *Comparison* feature appears next to *Filters*. It enables you to compare the period you filtered with the previous one." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 msgid "Reporting filters in Odoo Purchase" msgstr "" @@ -5023,7 +7299,7 @@ msgstr "" msgid "Thanks to the 31 filtering options to choose from, the possibilities of your customizing your dataset are almost limitless. Go to :menuselection:`Filters --> Add Custom Filter`, specify the condition the filtering option should meet (e.g. *is equal to*, *contains*, etc.), and click on *Apply*. If you want to select orders matching several conditions simultaneously (*and* operator), repeat the process to add another custom filter. If you want to use the *or* operator, don't click on *Apply*, and click on *Add a condition* instead. Once you have added all the desired filtering options, click on *Apply*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 msgid "Custom reporting filter in Odoo Purchase" msgstr "" @@ -5039,7 +7315,7 @@ msgstr "" msgid "Before selecting what you want to measure, you need to decide whether you prefer using the graph view or the pivot view. By default, the dashboard presents both views. However, the measures you select won't be applied to both views. You can access each view separately by clicking on the icons at the top right of the dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 msgid "Switch reporting view in Odoo Purchase" msgstr "" @@ -5051,7 +7327,7 @@ msgstr "" msgid "You can transform the main graph in just a click by selecting one of the three charts: bar, line or pie. Fourteen different measures are available, but you can only use one at a time. However, you can group the measure using one or several of the 19 *Groups*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 msgid "Reporting graph view in Odoo Purchase" msgstr "" @@ -5067,7 +7343,7 @@ msgstr "" msgid "The pivot table view enables you to explore your data in great detail. Unlike the graph view, the pivot table enables you to add several measures at the same time. By clicking on *Measures* or on the **+** sign in the *Total* column, you can add as many as you want, each assigned to a new column. By clicking on the **+** sign in the *Total* row, you can add *Groups*. If you click on a group's **+** sign, you can add a sub-group, and so on." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 msgid "Pivot table view in Odoo Purchase" msgstr "" @@ -5103,7 +7379,7 @@ msgstr "" msgid "From the Purchase app, go to :menuselection:`Configuration --> Settings` and activate *Purchase Agreements*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Enable purchase agreements in Odoo Purchase" msgstr "" @@ -5131,7 +7407,7 @@ msgstr "" msgid "Quantities: if you use lines of agreements, you can also specify independently if the products' quantities should be used to pre-fill new requests for quotations. The default option for blanket orders is *Set quantities manually*, while for calls for tenders are set to *Use quantities of agreement*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Configure purchase agreements types in Odoo Purchase" msgstr "" @@ -5147,7 +7423,7 @@ msgstr "" msgid "Next, add the products you want to order and their price. Note that you can also add a *Quantity* for each product, for example, if you have agreed with your vendor to order a specific minimum quantity each time or in total. If you have configured your blanket order to *Set quantities manually*, this is only used for informational purposes." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Set up a blanket order in Odoo Purchase" msgstr "" @@ -5167,7 +7443,7 @@ msgstr "" msgid "From here, you can quickly view all the requests for quotations made under that blanket order by clicking on *RFQs/Orders*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Create new quotations for an ongoing blanket order in Odoo Purchase" msgstr "" @@ -5183,7 +7459,7 @@ msgstr "" msgid "Blanket orders can be used for :doc:`automated replenishment <../../purchase/products/reordering>`, as once a blanket order is confirmed, a new vendor line is added to your product. Make sure the related vendor is in the first position if you have several vendors linked to your product." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Blanket order added to product configuration in Odoo Purchase" msgstr "" @@ -5203,7 +7479,7 @@ msgstr "" msgid "You can also write any *Terms and Conditions* at the bottom of the agreement. Once you are ready, click on *Confirm*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Set up a call for tenders in Odoo Purchase" msgstr "" @@ -5215,7 +7491,7 @@ msgstr "" msgid "You can now request new quotations from the call for tenders. Click on *New Quotation* and select one of your vendors you want to invite to the call for tenders. Product lines should also be pre-filled in, depending on how you configured the *Purchase Agreement Type*. Click on *Send by email* to send it to the vendor. Go back to the call for tenders and repeat this process for each vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Request a quotation from a call for tenders in Odoo Purchase" msgstr "" @@ -5223,7 +7499,7 @@ msgstr "" msgid "Once you have sent a request for quotation to every vendor and receiving their quotes, click on *Validate* to proceed to the bid selection. Next, click on the RFQs/Orders smart button to view all your vendors' quotations." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Validate a call for tenders and view all quotations in Odoo Purchase" msgstr "" @@ -5231,7 +7507,7 @@ msgstr "" msgid "Click on each request for quotation to add the price communicated by your vendors manually. When that's done, select the most advantageous offer and click on *Confirm Order*. This automatically closes the call for tenders. You can now proceed with the purchase order as you would for a regular one." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:-1 msgid "Confirm an order in Odoo Purchase" msgstr "" @@ -5255,8 +7531,7 @@ msgstr "" msgid "As a first step, open your Purchase app and go to :menuselection:`Configuration --> Settings` to set the default bill control policy for all the products created onwards." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:None -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 msgid "Vendor bills default control setting for new products in Odoo Purchase" msgstr "" @@ -5268,7 +7543,7 @@ msgstr "" msgid "If you choose *On received quantities* instead, you can only create one once you have at least received some of the products you have ordered. The quantities you have received are used to generate the draft bill. If you try to create one without having received any product, you get an error message." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 msgid "No invoiceable line error message in Odoo Purchase" msgstr "" @@ -5288,7 +7563,7 @@ msgstr "" msgid "Once you confirm an order, you can view its *Billing Status* by going to the *Other Information* tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 msgid "Purchase order billing status in Odoo Purchase" msgstr "" @@ -5356,7 +7631,7 @@ msgstr "" msgid "First, go to :menuselection:`Configuration --> Settings` and activate *3-way matching*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 msgid "3-way-matching setting in Odoo Purchase" msgstr "" @@ -5372,7 +7647,7 @@ msgstr "" msgid "With the feature activated, your vendor bills now display the *Should Be Paid* field under the *Other info* tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 msgid "Should Be Paid field under a vendor bill in Odoo Purchase" msgstr "" @@ -5388,7 +7663,7 @@ msgstr "" msgid "Once the payment has been registered and mentions *Paid*, the *Should Be Paid* status is set to *No*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 msgid "Paid bill in Odoo Purchase" msgstr "" @@ -5400,308 +7675,355 @@ msgstr "" msgid "Manage vendor bills" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:5 -msgid "The **Purchase** application allows you to manage your purchase orders, incoming products, and vendor bills all seamlessly in one place." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:7 +msgid "A *vendor bill* is an invoice received for products and/or services that a company purchases from a vendor. Vendor bills record payables as they arrive from vendors, and can include amounts owed for the goods and/or services purchased, sales taxes, freight and delivery charges, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:8 -msgid "If you want to set up a vendor bill control process, the first thing you need to do is to have purchase data in Odoo. Knowing what has been purchased and received is the first step towards understanding your purchase management processes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:13 -msgid "Here is the standard work flow in Odoo:" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:11 +msgid "In Odoo, a vendor bill can be created at different points in the purchasing process, depending on the *bill control* policy chosen in the *Purchase* app settings." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:15 -msgid "You begin with a **Request for Quotation (RFQ)** to send out to your vendor(s)." +msgid "Bill control policies" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:18 -msgid "Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase Order (PO)**." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:17 +msgid "To view and edit the default bill control policy and make changes to it, go to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:21 -msgid "Confirming the PO generates an **Incoming Shipment** if you purchased any stockable products." +msgid "Here, there are two :guilabel:`Bill Control` policy options: :guilabel:`Ordered quantities` and :guilabel:`Received quantities`. After a policy is selected, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:24 -msgid "Upon receiving a **Vendor Bill** from your Vendor, validate the bill with products received in the previous step to ensure accuracy." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 +msgid "Bill control policies in purchase app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:27 -msgid "This process may be done by three different people within the company, or only one." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28 +msgid "The policy selected will be the default for any new product created. The definition of each policy is as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:34 -msgid "Installing the Purchase and Inventory applications" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31 +msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase order is confirmed. The products and quantities in the purchase order are used to generate a draft bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:36 -msgid "From the **Apps** application, search for the **Purchase** module and install it. Due to certain dependencies, installing Purchase will automatically install the **Inventory** and **Accounting** applications." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:33 +msgid ":guilabel:`Received quantities`: a bill is only created **after** part of the total order has been received. The products and quantities **received** are used to generate a draft bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:41 -msgid "Creating products" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:37 +msgid "If a product needs a different control policy, the default bill control policy can be overridden by going to the :guilabel:`Purchase` tab in a product's template, and modifying its :guilabel:`Control Policy` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:43 -msgid "Creating products in Odoo is essential for quick and efficient purchasing within Odoo. Simply navigate to the Products submenu under Purchase and click create." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 +msgid "Control policy field on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:50 -msgid "When creating the product, pay attention to the **Product Type** field, since it is important:" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:46 +msgid "3-way matching" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:53 -msgid "Products that are set as **Stockable or Consumable** will allow you to keep track of their inventory levels. These options imply stock management and will allow for receiving these kinds of products." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:48 +msgid "*3-way matching* ensures vendor bills are only paid once some (or all) of the products included in the purchase order have actually been received." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:58 -msgid "Conversely, products that are set as a **Service or Digital Product** will not imply stock management, simply due to the fact that there is no inventory to manage. You will not be able to receive products under either of these designations." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:51 +msgid "To activate it, go to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, check the box next to :guilabel:`3-way matching: purchases, receptions, and bills`, and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:56 +msgid ":guilabel:`3-way matching` is **only** intended to work with the :guilabel:`Bill Control` policy set to :guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 +msgid "Activated three-way matching feature in purchase settings." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:64 -msgid "It is recommended that you create a **Miscellaneous** product for all purchases that occur infrequently and do not require inventory valuation or management. If you create such a product, it is recommended to set the product type to **Service**." +msgid "Create and manage vendor bills on receipts" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:69 -msgid "Managing your Vendor Bills" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:66 +msgid "When products are received into a company's warehouse, receipts are created. Once the company processes the received quantities, they can choose to create a vendor bill directly from the warehouse receipt form. Depending on the bill control policy chosen in the settings, vendor bill creation is completed at different steps of the procurement process." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:72 -msgid "Purchasing products or services" +msgid "With the bill control policy set to ordered quantities" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:74 -msgid "From the purchase application, you can create a purchase order with as many products as you need. If the vendor sends you a confirmation or quotation for an order, you may record the order reference number in the **Vendor Reference** field. This will enable you to easily match the PO with the the vendor bill later (as the vendor bill will probably include the Vendor Reference)" +msgid "To create and manage vendor bills on receipts using the *ordered quantities* bill control policy, first go to :menuselection:`Purchase app --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Ordered quantities` under :guilabel:`Bill Control`. Then, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:84 -msgid "Validate the purchase order and receive the products from the Inventory application." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:79 +msgid "Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` to create a new request for quotation (RFQ). Doing so reveals a blank :abbr:`RFQ (request for quotation)` detail form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:88 -msgid "Receiving Products" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:82 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:144 +msgid "On the blank detail form, add a vendor to the :abbr:`RFQ (request for quotation)` in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:86 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 +msgid "Then, confirm the :abbr:`RFQ (request for quotation)` by clicking the :guilabel:`Confirm Order` button above the detail form. Doing so turns the :abbr:`RFQ (request for quotation)` into a purchase order." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:90 -msgid "If you purchased any stockable products that you manage the inventory of, you will need to receive the products from the Inventory application after you confirm a purchase order. From the **Inventory dashboard**, you should see a button linking you directly to the transfer of products. This button is outlined in red below:" +msgid "Then, click the :guilabel:`Create Bill` button to create a vendor bill for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:92 +msgid "Clicking the :guilabel:`Create Bill` button reveals the :guilabel:`Draft Bill` page for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:95 +msgid "On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button to modify the bill, and add a bill date in the :guilabel:`Bill Date` field. If needed, add additional products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line` in the :guilabel:`Invoice Lines` tab." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:99 -msgid "Navigating this route will take you to a list of all orders waiting to be received." +msgid "Next, confirm the bill by clicking the :guilabel:`Confirm` button on the :guilabel:`Draft Bill` page." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:105 -msgid "If you have a lot of awaiting orders, apply a filter using the search bar in the upper right. With this search bar, you may filter based on the vendor (partner), the product, or the source document (also known as the reference of your purchase order). You can also group the orders by different criteria under **Group By**. Selecting an item from this list will open the following screen where you then will receive the products." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:103 +msgid "Since the bill control policy is set to *ordered quantities*, the draft bill can be confirmed as soon as it is created, before any products have been received." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:116 -msgid "Purchasing service products does not trigger a delivery order." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:106 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:179 +msgid "On the new :guilabel:`Vendor Bill`, add a :guilabel:`Bill Reference` number, which can be used to match the bill with additional documents (such as the :abbr:`PO (purchase order)`). Then, click :menuselection:`Confirm --> Register Payment`. Doing so causes a pop-up to appear, wherein a payment :guilabel:`Journal` can be chosen; a :guilabel:`Payment Method` selected; and a :guilabel:`Recipient Bank Account` can be selected from a drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:119 -msgid "Managing Vendor Bills" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:112 +msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. Once ready, click :guilabel:`Create Payment` to finish creating the :guilabel:`Vendor Bill`. Doing so causes a green :guilabel:`In Payment` banner to display on the :abbr:`RFQ (request for quotation)` form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:121 -msgid "When you receive a vendor bill for a previous purchase, be sure to record it in the Purchases application under the **Control Menu**. You need to create a new vendor bill even if you already registered a purchase order." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 +msgid "Vendor bill form for ordered quantities control policy." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:129 -msgid "The first thing you will need to do upon creating a vendor bill is to select the appropriate vendor, since doing so will also pull up any associated accounting or pricelist information. From there, you can choose to specify one or multiple Purchase Orders to populate the Vendor Bill with. When you select a Purchase Order from the list, Odoo will pull any uninvoiced products associated to that Purchase Order and automatically populate that information below. If you are having a hard time finding the appropriate vendor bill, you may search through the list by inputting the vendor reference number or your internal purchase order number." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:122 +msgid "Each vendor bill provides the option to either :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note`. A *credit note* is typically issued when a vendor or supplier of goods get some quantity of products back from the customer to whom they were sold, while *debit notes* are reserved for goods returned from the customer/buyer to the vendor or supplier." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:143 -msgid "While the invoice is in a draft state, you can make any modifications you need (i.e. remove or add product lines, modify quantities, and change prices)." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:128 +msgid "With the bill control policy set to received quantities" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 -msgid "Your vendor may send you several bills for the same Purchase Order if:" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:131 +msgid "If the creation of a vendor bill is attempted without receiving any quantities of a product (while using the *received quantities* bill control policy), an error message appears, and settings must be changed before proceeding." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:150 -msgid "Your vendor is in back-order and is sending you invoices as they ship the products." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:135 +msgid "To create and manage vendor bills on receipts using the *received quantities* bill control policy, first go to :menuselection:`Purchase app --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Received quantities` under :guilabel:`Bill Control`. Then, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:151 -msgid "Your vendor is sending you a partial bill or asking for a deposit." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:140 +msgid "Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` to create a new :abbr:`RFQ (request for quotation)`. Doing so reveals a blank :abbr:`RFQ (request for quotation)` detail form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:153 -msgid "Every time you record a new vendor bill, Odoo will automatically populate the product quantities based on what has been received from the vendor. If this value is showing a zero, this means that you have not yet received this product and simply serves as a reminder that the product is not in hand and you may need to inquire further into this. At any point in time, before you validate the Vendor Bill, you may override this zero quantity." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:152 +msgid "Finally, click the :guilabel:`Create Bill` button to create a bill for the purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:162 -msgid "Vendor Bill Matching" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:155 +msgid "Clicking :guilabel:`Create Bill` before any products have been received will cause a :guilabel:`User Error` pop-up to appear. The :guilabel:`Purchase Order` requires the receipt of at least partial quantity of the items included on the order to create a vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 +msgid "User error pop-up for received quantities control policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:163 +msgid "Next, click the :guilabel:`Receipt` smart button to view the warehouse receipt form." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:165 -msgid "What to do if your vendor bill does not match what you received" +msgid "On the warehouse receipt form, click :menuselection:`Validate --> Apply` to mark the :guilabel:`Done` quantities. Then, navigate back to the :menuselection:`Purchase Order` (via the breadcrumbs), and click the :guilabel:`Create Bill` button on the purchase order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:167 -msgid "If the bill you receive from the vendor has quantities that do not match the quantities automatically populated by Odoo, this could be due to several reasons:" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:169 +msgid "Doing so reveals the :guilabel:`Draft Bill` for the purchase order. On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button, and add a :guilabel:`Bill Date`. If needed, add additional products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:171 -msgid "The vendor is incorrectly charging you for products and/or services that you have not ordered." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:173 +msgid "Next, click the :guilabel:`Confirm` button to confirm the :guilabel:`Draft Bill`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:174 -msgid "The vendor is billing you for products that you might not have received yet, as the invoicing control may be based on ordered or received quantities." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:176 +msgid "Since the bill control policy is set to *received quantities*, the draft bill can **only** be confirmed when at least some of the quantities are received." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:178 -msgid "The vendor did not bill you for previously purchased products." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:185 +msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. Once ready, click :guilabel:`Create Payment` to finish creating the vendor bill. Doing so causes a green **In Payment** banner to display on the :abbr:`RFQ (request for quotation)` form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:180 -msgid "In these instances it is recommended that you verify that the bill, and any associated purchase order to the vendor, are accurate and that you understand what you have ordered and what you have already received." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:184 -msgid "If you are unable to find a purchase order related to a vendor bill, this could be due to one of a few reasons:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:187 -msgid "The vendor has already invoiced you for this purchase order; therefore it is not going to appear anywhere in the selection." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:190 -msgid "Someone in the company forgot to record a purchase order for this vendor." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:191 +msgid "Create and manage vendor bills in Accounting" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:193 -msgid "The vendor is charging you for something you did not order." +msgid "Vendor bills can also be created directly from the *Accounting* app, **without** having to create a purchase order first. To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`, and click :guilabel:`Create`. Doing so reveals a blank vendor bill detail form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:198 -msgid "How product quantities are managed" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:197 +msgid "On this blank vendor bill detail form, add a vendor in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines (under the :guilabel:`Invoice Lines` tab), by clicking :guilabel:`Add a line`. Then, add a bill date in the :guilabel:`Bill Date` field, and any other necessary information. Finally, click :guilabel:`Confirm` to confirm the bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:200 -msgid "By default, services are managed based on ordered quantities, while stockables and consumables are managed based on received quantities." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:202 +msgid "From here, click the :guilabel:`Journal Items` tab to view (or change) the :guilabel:`Account` journals that were populated based on the configuration on the corresponding :guilabel:`Vendor` and :guilabel:`Product` forms." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:203 -msgid "If you need to manage products based on ordered quantities over received quantities, you will need to belong to the group **Purchase Manager**. Ask your system administrator to enable these access on :menuselection:`Settings --> Users --> Users --> Access Rights`. Once you belong to the correct group, select the product(s) you wish to modify, and you should see a new field appear, labeled **Control Purchase Bills**." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:206 +msgid "Then, click :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note` to add credit or debit notes to the bill. Or, add a :guilabel:`Bill Reference` number (while in :guilabel:`Edit` mode)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:209 +msgid "Then, when ready, click :menuselection:`Register Payment --> Create Payment` to complete the :guilabel:`Vendor Bill`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:213 -msgid "You can then change the default management method for the selected product to be based on either:" +msgid "To tie the draft bill to an existing purchase order, click the drop-down menu next to :guilabel:`Auto-Complete`, and select a :abbr:`PO (purchase order)` from the menu. The bill will auto-populate with the information from the :abbr:`PO (purchase order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:216 -msgid "Ordered quantities" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 +msgid "Auto-complete drop-down list on draft vendor bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:218 -msgid "or Received quantities" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:222 +msgid "Batch billing" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:221 -msgid "Batch Billing" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:224 +msgid "Vendor bills can be processed and managed in batches in the *Accounting* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:223 -msgid "When creating a vendor bill and selecting the appropriate purchase order, you may continue to select additional purchase orders. Odoo will add the additional line items from the purchase orders you select. If you have not deleted the previous line items from the first purchase order, the bill will be linked to all the appropriate purchase orders." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:226 +msgid "To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`. Then, click the :guilabel:`checkbox` at the top left of the page, beside the :guilabel:`Number` column, under the :guilabel:`Create` button. This selects all existing vendor bills with a :guilabel:`Posted` or :guilabel:`Draft` :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:231 +msgid "From here, click the :guilabel:`Action` gear icon to export, delete, or send & print the bills; click the :guilabel:`Print` icon to print the invoices or bills; or click :guilabel:`Register Payment` to create and process payments for multiple vendor bills at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:235 +msgid "When :guilabel:`Register Payment` is selected, a pop-up appears. In this pop-up window, select the appropriate journal in the :guilabel:`Journal` field, choose a payment date in the :guilabel:`Payment Date` field, and choose a :guilabel:`Payment Method`. There is also the option to :guilabel:`Group Payments` on this pop-up, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:240 +msgid "When ready, click the :guilabel:`Create Payment` button, which creates a list of journal entries on a separate page. This list of journal entries are all tied to their appropriate vendor bills." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 +msgid "Batch billing register payment pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:248 +msgid "The :guilabel:`Register Payment` option for vendor bills in batches will only work for journal entries whose :guilabel:`Status` is set to :guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:252 +msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/control_bills`" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:3 -msgid "Don’t run out of stock with reordering rules" +msgid "Configure reordering rules" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:5 -msgid "To make sure you never run out of stock, you can define *Reordering Rules* on products. Thanks to them, Odoo can help you replenish your stock automatically when it reaches set quantities or whenever a sales order is created." +msgid "For certain products, it is necessary to ensure that there is always a minimum amount available on hand at any given time. By adding a reordering rule to a product, it is possible to automate the reordering process so that a purchase order is automatically created whenever the amount on hand falls below a set threshold." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:9 -msgid "You need to install the *Inventory app* to use reordering rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:12 -msgid "Configure your storable product" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:11 +msgid "The *Inventory* module must be installed to use reordering rules." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:14 -msgid "Open or create a product with its *Product Type* set to *Storable Product*." +msgid "Configure products for reordering" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None -msgid "Set the product type in Odoo" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:16 +msgid "Products must be configured in a specific way before a reordering rule can be added to them." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:20 -msgid "As you are purchasing this product from a vendor, go to the product's *Purchase tab* and add a vendor by clicking on *Add a line*. You can add multiple vendors, but make sure to order them correctly, since reordering rules always use the first vendor in a list. You can add a price, but it isn't necessary for the reordering rule to work. In addition, you can add a minimum quantity you must order to benefit from that price." +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:18 +msgid "Starting from the :menuselection:`Inventory`, :menuselection:`Manufacturing`, :menuselection:`Purchase`, or :menuselection:`Sales` module, navigate to :menuselection:`Products --> Products` and then click :guilabel:`Create` to make a new product. Alternatively, find a product that already exists in the database and click into it's product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:27 -msgid "If the quantity Odoo has to reorder doesn't match the minimum quantity specified, Odoo selects the next vendor on your list. If you don't have another vendor on your list, the reordering rule won't work. For that purpose, you can add the same vendor multiple times with different prices for different quantities." +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:23 +msgid "Next, on the product form, enable reordering by checking the :guilabel:`Can be Purchased` option underneathe the :guilabel:`Product Name` field. Finally, set the :guilabel:`Product Type` to `Storable Product` under the :guilabel:`General Information` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None -msgid "Add vendor to a product in Odoo" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:-1 +msgid "Configure a product for reordering in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:37 -msgid "By default, a draft purchase order is created. However, if you have enabled *Purchase Agreements*, you can *Propose a call for tenders* instead as shown in the image above. For more information, see :doc:`../manage_deals/agreements`" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:32 +msgid "Add a reordering rule to a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:41 -msgid "Next, make sure the correct route is selected under the Inventory tab of your product. If you created your product within the Purchase app, the *Buy* route is selected by default. If you are looking to dropship your product, select *Dropship*." +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:34 +msgid "After properly configuring a product, a reordering rule can be added to it by selecting the now visible :guilabel:`Reordering Rules` tab at the top of that product's form, and then clicking :guilabel:`Create` on the :guilabel:`Reordering Rules` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None -msgid "Choose product routes in Odoo" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:-1 +msgid "Access reordering rules for a product from the product page in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:50 -msgid "Set up your reordering rule" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:42 +msgid "Once created, the reordering rule can be configured to generate purchase orders automatically by defining the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:45 +msgid ":guilabel:`Location` specifies where the ordered quantities should be stored once they are received and entered into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:47 +msgid ":guilabel:`Min Quantity` sets the lower threshold for the reordering rule while :guilabel:`Max Quantity` sets the upper threshold. If the stock on hand falls below the minimum quantity, a new purchase order will be created to replenish it up to the maximum quantity." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:52 -msgid "Open your product and click on the *Reordering Rules* button." +msgid "If :guilabel:`Min Quantity` is set to `5` and :guilabel:`Max Quantity` is set to `25` and the stock on hand falls to four, a purchase order will be created for 21 units of the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None -msgid "Reordering rules button on a product in Odoo" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:58 -msgid "Once you are on the product's reordering rules page, click on *Create*." +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:55 +msgid ":guilabel:`Multiple Quantity` can be configured so that products are only ordered in batches of a certain quantity. Depending on the number entered, this can result in the creation of a purchase order that would put the resulting stock on hand above what is specified in the :guilabel:`Max Quantity` field." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:61 -msgid "You can access and create reordering rules from :menuselection:`Inventory --> Configuration --> Reordering Rules` and from :menuselection:`Inventory --> Operations --> Replenishment`. By default, the replenishment view presents a summary of all the products that you might need to purchase to fulfill your sales orders. From there, you can ask Odoo with a single click to order a product once or automate all orders for that product, future orders included." +msgid "If :guilabel:`Max Quantity` is set to `100` but :guilabel:`Multiple Quantity` is set to order the product in batches of `200`, a purchase order will be created for 200 units of the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:68 -msgid "Define quantities" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:65 +msgid ":guilabel:`UoM` specifies the unit of measurement by which the quantity will be ordered. For discrete products, this should be set to `Units`. However, it can also be set to units of measurement like `Volume` or `Weight` for non-discrete products like water or bricks." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:70 -msgid "You can set a **minimum quantity** your stock should always have. Once set, if your stock goes below the minimum quantity, and if you selected the Buy route, a request for quotation is automatically generated to reach that minimum quantity, plus any additional quantity needed to fill in a sales order for example." +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:-1 +msgid "Configure the reordering rule in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:75 -msgid "If you set a **maximum quantity**, every time the product has to be replenished, enough products are reordered to reach the maximum quantity." +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:74 +msgid "Manually trigger reordering rules using the scheduler" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:78 -msgid "If you want to order only the exact quantity needed to fill in a sales order for example, set both both the minimum and maximum quantity to **zero**. The quantity mentioned in the sales order is then used by the reordering rule." +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:76 +msgid "Reordering rules will be automatically triggered by the scheduler, which runs once a day by default. To trigger reordering rules manually, navigate to :menuselection:`Inventory --> Operations --> Run Scheduler`. On the pop-up window, confirm the manual action by clicking :guilabel:`Run Scheduler`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:82 -msgid "You can also add a **quantity multiple** to only order products in batches of a certain quantity. Click on the optional columns drop-down menu, and select *Multiple Quantity* to show the column. Bear in mind that you might go over the maximum quantity you set if your rule includes a quantity multiple, as Odoo orders enough products to reach the maximum quantity and respect the set quantity multiple." +msgid "Manually triggering reordering rules will also trigger any other scheduled actions." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None -msgid "Create a reordering rule in Odoo" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:85 +msgid "Manage reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:92 -msgid "If you selected multiple routes for the same product under its Inventory tab, make sure to select your *Preferred Route* on your reordering rule by clicking on the optional columns drop-down menu, adding the *Preferred Route* column, and selecting the right route." +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:87 +msgid "To manage the reordering rules for a single product, navigate to that product page's form and select the :guilabel:`Reordering Rules` tab at the top of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:90 +msgid "To manage all reordering rules for every product, go to :menuselection:`Inventory --> Configuration --> Reordering Rules`. From this dashboard, typical bulk actions in Odoo can be performed such as exporting data or archiving rules that are no longer needed. As well, the :guilabel:`Filters`, :guilabel:`Group By` or triple-dotted menu on the form are available to search for and/or organize the reordering rules as desired." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:3 @@ -5732,7 +8054,7 @@ msgstr "" msgid "Open your Sales app and go to :menuselection:`Configuration --> Settings`. Under Product Catalog, enable *Units of Measure*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:-1 msgid "Enable the units of measure option in Odoo Sales" msgstr "" @@ -5760,7 +8082,7 @@ msgstr "" msgid "Back to the first example, if you purchase orange juice from your vendor in **gallons** and sell it to your customers in **liters**, first select *L* (liters) as the *Unit of Measure*, and *gal (US)* (gallons) as the *Purchase Unit of Measure*, then click on *Save*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:-1 msgid "Configure a product's units of measure in Odoo" msgstr "" @@ -5780,7 +8102,7 @@ msgstr "" msgid "To do so, go to :menuselection:`Configuration --> Units of Measure Categories`. Click on *Create* and name the category." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:-1 msgid "Create a new units of measure category in Odoo Purchase" msgstr "" @@ -5796,7 +8118,7 @@ msgstr "" msgid "In the example, as you cannot purchase less than 1 roll and won't use fractions of a roll as a unit of measure, you can enter 1." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:-1 msgid "Create a new reference unit of measure in Odoo Purchase" msgstr "" @@ -5820,7 +8142,7 @@ msgstr "" msgid "For your curtain roll, the ratio should be set to 100." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:-1 msgid "Create a second unit of measure in Odoo Purchase" msgstr "" @@ -5828,6 +8150,6 @@ msgstr "" msgid "You can now configure your product just as you would using Odoo's standard units of measure." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:None +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:-1 msgid "Set a product's units of measure using your own units in Odoo Purchase" msgstr "" diff --git a/locale/sources/legal.pot b/locale/sources/legal.pot index f236d44fe..8d03a9b86 100644 --- a/locale/sources/legal.pot +++ b/locale/sources/legal.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-09-01 15:09+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,97 +20,6 @@ msgstr "" msgid "Legal" msgstr "" -#: ../../content/legal.rst:18 -#: ../../content/legal/licenses.rst:6 -msgid "Licenses" -msgstr "" - -#: ../../content/legal.rst:20 -msgid ":ref:`licenses`" -msgstr "" - -#: ../../content/legal.rst:23 -#: ../../content/legal/terms.rst:5 -msgid "Terms and Conditions" -msgstr "" - -#: ../../content/legal.rst:29 -msgid "English" -msgstr "" - -#: ../../content/legal.rst:30 -msgid "Français" -msgstr "" - -#: ../../content/legal.rst:31 -msgid "Nederlands" -msgstr "" - -#: ../../content/legal.rst:32 -msgid "Deutsch" -msgstr "" - -#: ../../content/legal.rst:33 -msgid "Español" -msgstr "" - -#: ../../content/legal.rst:34 -msgid "Odoo Enterprise Agreement [#]_" -msgstr "" - -#: ../../content/legal.rst:47 -#: ../../content/legal.rst:48 -#: ../../content/legal.rst:68 -#: ../../content/legal.rst:69 -#: ../../content/legal.rst:70 -msgid "|missing_txt| |missing_pdf|" -msgstr "" - -#: ../../content/legal.rst:55 -#: ../../content/legal/terms/partnership.rst:5 -msgid "Odoo Partnership Agreement" -msgstr "" - -#: ../../content/legal.rst:71 -msgid "Terms of Sale" -msgstr "" - -#: ../../content/legal.rst:88 -msgid "Applies to self-hosting, Odoo.SH and Odoo Cloud." -msgstr "" - -#: ../../content/legal.rst:99 -msgid "`Archive of older agreements `_" -msgstr "" - -#: ../../content/legal.rst:102 -msgid "Other legal references" -msgstr "" - -#: ../../content/legal.rst:104 -msgid "`Odoo Cloud Service Level Agreement (SLA) `_" -msgstr "" - -#: ../../content/legal.rst:105 -msgid "`Odoo Cloud Acceptable Use Policy `_" -msgstr "" - -#: ../../content/legal.rst:106 -msgid "`Odoo SA's Privacy Policy `_" -msgstr "" - -#: ../../content/legal.rst:107 -msgid "`Odoo SA's GDPR Compliance Guide `_" -msgstr "" - -#: ../../content/legal.rst:108 -msgid ":ref:`cla`" -msgstr "" - -#: ../../content/legal.rst:109 -msgid ":ref:`germany/gobd`" -msgstr "" - #: ../../content/legal/cla.rst:5 msgid "Contributor License Agreement" msgstr "" @@ -251,6 +160,10 @@ msgstr "" msgid "https://www.ietf.org/rfc/rfc1855.txt" msgstr "" +#: ../../content/legal/licenses.rst:6 +msgid "Licenses" +msgstr "" + #: ../../content/legal/licenses.rst:11 msgid "Odoo 14 Community Edition" msgstr "" @@ -267,53 +180,37 @@ msgstr "" msgid "Odoo 14 Enterprise Edition is licensed under the Odoo Enterprise Edition License v1.0, defined as follows:" msgstr "" -#: ../../content/legal/licenses/enterprise_license.txt:1 -#: ../../content/legal/terms/i18n/enterprise_fr.rst:651 -#: ../../content/legal/licenses/enterprise_license.txt:1 -#: ../../content/legal/terms/i18n/partnership_fr.rst:405 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:658 +#: ../../content/legal/terms/i18n/partnership_fr.rst:423 #: ../../content/legal/licenses/enterprise_license.txt:1 msgid "Odoo Enterprise Edition License v1.0" msgstr "" -#: ../../content/legal/licenses/enterprise_license.txt:3 -#: ../../content/legal/licenses/enterprise_license.txt:3 #: ../../content/legal/licenses/enterprise_license.txt:3 msgid "This software and associated files (the \"Software\") can only be used (executed, modified, executed after modifications) with a valid Odoo Enterprise Subscription for the correct number of users." msgstr "" -#: ../../content/legal/licenses/enterprise_license.txt:7 -#: ../../content/legal/licenses/enterprise_license.txt:7 #: ../../content/legal/licenses/enterprise_license.txt:7 msgid "With a valid Partnership Agreement with Odoo S.A., the above permissions are also granted, as long as the usage is limited to a testing or development environment." msgstr "" -#: ../../content/legal/licenses/enterprise_license.txt:11 -#: ../../content/legal/licenses/enterprise_license.txt:11 #: ../../content/legal/licenses/enterprise_license.txt:11 msgid "You may develop Odoo modules based on the Software and distribute them under the license of your choice, provided that it is compatible with the terms of the Odoo Enterprise Edition License (For example: LGPL, MIT, or proprietary licenses similar to this one)." msgstr "" -#: ../../content/legal/licenses/enterprise_license.txt:16 -#: ../../content/legal/licenses/enterprise_license.txt:16 #: ../../content/legal/licenses/enterprise_license.txt:16 msgid "You may use Odoo modules published under any license along with the Software, provided that their license is compatible with the terms of the Odoo Enterprise License (Including, but not limited to, any module published on the Odoo Apps Store on odoo.com/apps)" msgstr "" -#: ../../content/legal/licenses/enterprise_license.txt:21 #: ../../content/legal/licenses.rst:69 #: ../../content/legal/licenses/enterprise_license.txt:21 -#: ../../content/legal/licenses/enterprise_license.txt:21 msgid "It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software." msgstr "" -#: ../../content/legal/licenses/enterprise_license.txt:24 -#: ../../content/legal/licenses/enterprise_license.txt:24 #: ../../content/legal/licenses/enterprise_license.txt:24 msgid "The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software." msgstr "" -#: ../../content/legal/licenses/enterprise_license.txt:27 -#: ../../content/legal/licenses/enterprise_license.txt:27 #: ../../content/legal/licenses/enterprise_license.txt:27 msgid "THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE." msgstr "" @@ -362,1016 +259,1223 @@ msgstr "" msgid "Odoo 8 is licensed under `AGPL version 3 `_ (also known as AGPLv3). See also the `GPL FAQ `_ and the `compatibility matrix `_." msgstr "" +#: ../../content/legal/terms.rst:5 +msgid "Terms and Conditions" +msgstr "" + #: ../../content/legal/terms/enterprise.rst:5 msgid "Odoo Enterprise Subscription Agreement" msgstr "" -#: ../../content/legal/terms/enterprise.rst:7 -#: ../../content/legal/terms/i18n/enterprise_es.rst:16 -#: ../../content/legal/terms/i18n/enterprise_fr.rst:14 -msgid "Version 9c - 2020-06-15" +#: ../../content/legal/terms/enterprise.rst:10 +msgid "`Download PDF `_" msgstr "" -#: ../../content/legal/terms/enterprise.rst:20 +#: ../../content/legal/terms/enterprise.rst:12 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:17 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:31 +msgid "Version 10a - 2022-10-27" +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:27 msgid "By subscribing to the Odoo Enterprise services (the \"Services\") provided by Odoo SA and its affiliates (collectively, \"Odoo SA\") in relation with Odoo Enterprise Edition or Odoo Community Edition (the \"Software\"), hosted on Odoo SA's Cloud platforms (the \"Cloud Platform\") or on-premises (\"Self-Hosting\"), you (the \"Customer\") are agreeing to be bound by the following terms and conditions (the \"Agreement\")." msgstr "" -#: ../../content/legal/terms/enterprise.rst:29 +#: ../../content/legal/terms/enterprise.rst:36 msgid "1 Term of the Agreement" msgstr "" -#: ../../content/legal/terms/enterprise.rst:31 +#: ../../content/legal/terms/enterprise.rst:38 msgid "The duration of this Agreement (the “Term”) shall be specified in writing on conclusion of this Agreement, beginning on the date of conclusion. It is automatically renewed for an equal Term, unless either party provides a written notice of termination minimum 30 days before the end of the Term to the other party." msgstr "" -#: ../../content/legal/terms/enterprise.rst:39 +#: ../../content/legal/terms/enterprise.rst:46 msgid "2 Definitions" msgstr "" -#: ../../content/legal/terms/enterprise.rst:45 +#: ../../content/legal/terms/enterprise.rst:52 msgid "User" msgstr "" -#: ../../content/legal/terms/enterprise.rst:42 +#: ../../content/legal/terms/enterprise.rst:49 msgid "Any user account indicated as active in the Software, with access to creation and/or edition mode. Deactivated user accounts and accounts used by external people (or systems) who only have limited access to the Software through the portal facilities (known as \"portal Users\") are not counted as Users." msgstr "" -#: ../../content/legal/terms/enterprise.rst:49 -#: ../../content/legal/terms/i18n/enterprise_de.rst:54 -#: ../../content/legal/terms/i18n/enterprise_fr.rst:58 -#: ../../content/legal/terms/i18n/enterprise_nl.rst:60 +#: ../../content/legal/terms/enterprise.rst:55 +#: ../../content/legal/terms/i18n/enterprise_de.rst:64 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:62 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:65 +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:61 msgid "App" msgstr "" -#: ../../content/legal/terms/enterprise.rst:48 -msgid "An \"App\" is a specialized group of features available for installation in the Software, and listed in the public Pricing section of `Odoo SA's website `_." -msgstr "" - -#: ../../content/legal/terms/enterprise.rst:54 -msgid "Odoo Partner" -msgstr "" - -#: ../../content/legal/terms/enterprise.rst:52 -msgid "An Odoo Partner is a third-party company or individual, chosen by the Customer, and working with the Customer for their Odoo related services. The Customer can decide at any time to work with a different Odoo Partner, or to work with Odoo SA directly (subject to prior notice)." +#: ../../content/legal/terms/enterprise.rst:55 +msgid "An \"App\" is a specialized group of features available for installation in the Software." msgstr "" #: ../../content/legal/terms/enterprise.rst:60 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:71 +msgid "Odoo Partner" +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:58 +msgid "An Odoo Partner is a third-party company or individual, chosen by the Customer, and working with the Customer for their Odoo related services. The Customer can decide at any time to work with a different Odoo Partner, or to work with Odoo SA directly (subject to prior notice)." +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:66 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:78 msgid "Extra Module" msgstr "" -#: ../../content/legal/terms/enterprise.rst:57 +#: ../../content/legal/terms/enterprise.rst:63 msgid "An extra module is a directory of source code files, or a set of Python-based customizations created in a database (e.g. with Odoo Studio), that adds features or changes the standard behavior of the Software. It may have been developed by the Customer, by Odoo SA, by an Odoo Partner on behalf of the Customer, or by third parties." msgstr "" -#: ../../content/legal/terms/enterprise.rst:64 +#: ../../content/legal/terms/enterprise.rst:70 msgid "Covered Extra Module" msgstr "" -#: ../../content/legal/terms/enterprise.rst:63 +#: ../../content/legal/terms/enterprise.rst:69 msgid "A Covered Extra Module is an Extra Module for which the Customer chooses to pay a maintenance fee in order to get support, upgrade and bug fixing services." msgstr "" -#: ../../content/legal/terms/enterprise.rst:73 -#: ../../content/legal/terms/i18n/enterprise_fr.rst:84 -#: ../../content/legal/terms/i18n/enterprise_nl.rst:71 +#: ../../content/legal/terms/enterprise.rst:79 +#: ../../content/legal/terms/i18n/enterprise_de.rst:89 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:88 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:93 +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:86 msgid "Bug" msgstr "" -#: ../../content/legal/terms/enterprise.rst:67 +#: ../../content/legal/terms/enterprise.rst:73 msgid "Is considered a Bug any failure of the Software or of a Covered Extra Module that results in a complete stop, error traceback or security breach, and is not directly caused by a defective installation or configuration. Non-compliance with specifications or requirements will be considered as Bugs at the discretion of Odoo SA (typically, when the Software does not produce the results or performance it was designed to produce, or when a country-specific feature does not meet legal accounting requirements anymore)." msgstr "" -#: ../../content/legal/terms/enterprise.rst:79 +#: ../../content/legal/terms/enterprise.rst:84 msgid "Covered Versions" msgstr "" -#: ../../content/legal/terms/enterprise.rst:76 +#: ../../content/legal/terms/enterprise.rst:82 msgid "Unless specified otherwise, the Services provided under this Agreement are applicable only to the Covered Versions of the Software, which include the 3 most recently released major versions." msgstr "" -#: ../../content/legal/terms/enterprise.rst:84 +#: ../../content/legal/terms/enterprise.rst:89 +msgid "Subscription Plan" +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:87 +msgid "A Subscription Plan defines a set of Apps, features and hosting solutions covered by this Agreement, and is defined in writing at the conclusion of this Agreement." +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:94 msgid "3 Access to the Software" msgstr "" -#: ../../content/legal/terms/enterprise.rst:86 +#: ../../content/legal/terms/enterprise.rst:96 msgid "The Customer can use the Software hosted on the Cloud Platform, or choose the Self-Hosting option. The Cloud Platform is hosted and fully managed by Odoo SA, and accessed remotely by the Customer. With the Self-Hosting option, the Customer instead hosts the Software on computer systems of their choice, that are not under the control of Odoo SA." msgstr "" -#: ../../content/legal/terms/enterprise.rst:91 +#: ../../content/legal/terms/enterprise.rst:101 msgid "For the duration of this Agreement, Odoo SA gives the Customer a non-exclusive, non-transferable license to use (execute, modify, execute after modification) the Odoo Enterprise Edition software, under the terms set forth in :ref:`appendix_a`." msgstr "" -#: ../../content/legal/terms/enterprise.rst:95 +#: ../../content/legal/terms/enterprise.rst:105 msgid "The Customer agrees to take all necessary measures to guarantee the unmodified execution of the part of the Software that verifies the validity of the Odoo Enterprise Edition usage and collects statistics for that purpose, including but not limited to the running of an instance, the number of Users, the installed Apps, and the number of lines of code of Covered Extra Modules." msgstr "" -#: ../../content/legal/terms/enterprise.rst:100 +#: ../../content/legal/terms/enterprise.rst:110 msgid "Odoo SA commits not to disclose individual or named figures to third parties without the consent of the Customer, and to deal with all collected data in compliance with its official Privacy Policy, published at https://www.odoo.com/privacy." msgstr "" -#: ../../content/legal/terms/enterprise.rst:104 +#: ../../content/legal/terms/enterprise.rst:114 msgid "Upon expiration or termination of this Agreement, this license is revoked immediately and the Customer agrees to stop using the Odoo Enterprise Edition software and the Cloud Platform." msgstr "" -#: ../../content/legal/terms/enterprise.rst:107 -msgid "Should the Customer breach the terms of this section, the Customer agrees to pay Odoo SA an extra fee equal to 300% of the applicable list price for the actual number of Users and installed Apps." +#: ../../content/legal/terms/enterprise.rst:117 +msgid "Should the Customer breach the terms of this section, the Customer agrees to pay Odoo SA an extra fee equal to 300% of the applicable list price for the actual number of Users." msgstr "" -#: ../../content/legal/terms/enterprise.rst:114 +#: ../../content/legal/terms/enterprise.rst:124 msgid "4 Services" msgstr "" -#: ../../content/legal/terms/enterprise.rst:119 +#: ../../content/legal/terms/enterprise.rst:129 msgid "4.1 Bug Fixing Service" msgstr "" -#: ../../content/legal/terms/enterprise.rst:121 +#: ../../content/legal/terms/enterprise.rst:131 msgid "For the duration of this Agreement, Odoo SA commits to making all reasonable efforts to remedy any Bug of the Software and Covered Extra Modules submitted by the Customer through the appropriate channel (typically, the web form or phone numbers listed on `odoo.com/help `_, or when working with an Odoo Partner, the channel provided by the partner), and to start handling such Customer submissions within 2 business days." msgstr "" -#: ../../content/legal/terms/enterprise.rst:127 +#: ../../content/legal/terms/enterprise.rst:137 msgid "As soon as the Bug is fixed an appropriate remedy will be communicated to the Customer. If the Customer is using a Covered Version, they will not be asked to upgrade to a more recent Covered Version of the Software as a remedy to a Bug." msgstr "" -#: ../../content/legal/terms/enterprise.rst:131 +#: ../../content/legal/terms/enterprise.rst:141 msgid "When a Bug is fixed in any Covered Version, Odoo SA commits to fixing the Bug in all more recent Covered Versions of the Software." msgstr "" -#: ../../content/legal/terms/enterprise.rst:134 +#: ../../content/legal/terms/enterprise.rst:144 msgid "Both parties acknowledge that as specified in the license of the Software and in the :ref:`liability` section of this Agreement, Odoo SA cannot be held liable for Bugs in the Software or in Covered Extra Modules." msgstr "" -#: ../../content/legal/terms/enterprise.rst:140 +#: ../../content/legal/terms/enterprise.rst:150 msgid "4.2 Security Updates Service" msgstr "" -#: ../../content/legal/terms/enterprise.rst:145 +#: ../../content/legal/terms/enterprise.rst:155 +#: ../../content/legal/terms/i18n/enterprise_de.rst:162 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:177 msgid "Self-Hosting" msgstr "" -#: ../../content/legal/terms/enterprise.rst:147 +#: ../../content/legal/terms/enterprise.rst:157 msgid "For the duration of this Agreement, Odoo SA commits to sending a \"Security Advisory\" to the Customer for any security Bug that is discovered in the Covered Versions of the Software (this excludes Extra Modules), at least 2 weeks before making the Security Advisory public, unless the Bug has already been disclosed publicly by a third party. Security Advisories include a complete description of the Bug, its cause, its possible impacts on the Customer's systems, and the corresponding remedy for each Covered Version." msgstr "" -#: ../../content/legal/terms/enterprise.rst:154 +#: ../../content/legal/terms/enterprise.rst:164 msgid "The Customer understands that the Bug and the information in the Security Advisory must be treated as Confidential Information as described in :ref:`confidentiality` during the embargo period prior to the public disclosure." msgstr "" -#: ../../content/legal/terms/enterprise.rst:161 +#: ../../content/legal/terms/enterprise.rst:171 +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:175 msgid "Cloud Platform" msgstr "" -#: ../../content/legal/terms/enterprise.rst:163 +#: ../../content/legal/terms/enterprise.rst:173 msgid "Odoo SA commits to apply the security remedies for any security Bug discovered in a version of the Software hosted on the Cloud Platform, on all systems under its control, as soon as the remedy is available, without requiring any manual action of the Customer." msgstr "" -#: ../../content/legal/terms/enterprise.rst:171 +#: ../../content/legal/terms/enterprise.rst:181 msgid "4.3 Upgrade Services" msgstr "" -#: ../../content/legal/terms/enterprise.rst:176 +#: ../../content/legal/terms/enterprise.rst:186 msgid "Upgrade Service for the Software" msgstr "" -#: ../../content/legal/terms/enterprise.rst:178 +#: ../../content/legal/terms/enterprise.rst:188 msgid "For the duration of this Agreement, the Customer can submit upgrade requests through the appropriate channel (typically Odoo SA's upgrade service website), in order to convert a database of the Software from any version of the Software to a more recent Covered Version (the \"Target Version\")." msgstr "" -#: ../../content/legal/terms/enterprise.rst:182 +#: ../../content/legal/terms/enterprise.rst:192 msgid "For the Cloud Platform, upgrade requests are submitted directly from the control panel of the Cloud Platform, and do not require any data upload. For Self-Hosting, upgrade requests must include a copy of the Customer's database and the associated data (typically obtained from the Backup menu of the Software)." msgstr "" -#: ../../content/legal/terms/enterprise.rst:187 +#: ../../content/legal/terms/enterprise.rst:197 msgid "This service provided through an automated platform in order to allow the Customer to perform unattended upgrades once a previous version of the Customer's database has been successfully upgraded for a Covered Version." msgstr "" -#: ../../content/legal/terms/enterprise.rst:191 +#: ../../content/legal/terms/enterprise.rst:201 msgid "The Upgrade Service is limited to the technical conversion and adaptation of the Customer's database to make it compatible with the Target Version, the correction of any Bug directly caused by the upgrade operation and not normally occurring in the Target Version, and the conversion of the source code and data of Covered Extra Modules for the Target Version." msgstr "" -#: ../../content/legal/terms/enterprise.rst:196 +#: ../../content/legal/terms/enterprise.rst:206 msgid "It is the responsibility of the Customer to verify and validate the upgraded database in order to detect Bugs, to analyze the impact of changes and new features implemented in the Target Version, and to convert and adapt for the Target Version any third-party extensions of the Software that were installed in the database before the upgrade (e.g. non-convered Extra Modules). The Customer may submit multiple upgrade requests for a database, until an acceptable result is achieved." msgstr "" -#: ../../content/legal/terms/enterprise.rst:206 +#: ../../content/legal/terms/enterprise.rst:216 msgid "4.4 Cloud Hosting Services" msgstr "" -#: ../../content/legal/terms/enterprise.rst:208 +#: ../../content/legal/terms/enterprise.rst:218 msgid "For the duration of this Agreement, when the Customer chooses to use the Cloud Platform, Odoo SA commits to providing at least the following services:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:211 +#: ../../content/legal/terms/enterprise.rst:221 msgid "Choice of multiple hosting regions (minimum 3: Europe, America, Asia/Pacific)" msgstr "" -#: ../../content/legal/terms/enterprise.rst:212 +#: ../../content/legal/terms/enterprise.rst:222 msgid "Hosting in Tier-III data centers or equivalent, with 99.9% network uptime" msgstr "" -#: ../../content/legal/terms/enterprise.rst:213 +#: ../../content/legal/terms/enterprise.rst:223 msgid "Grade A SSL (HTTPS) Encryption of communication" msgstr "" -#: ../../content/legal/terms/enterprise.rst:214 +#: ../../content/legal/terms/enterprise.rst:224 msgid "Fully automated, verified backups, replicated in multiple regions" msgstr "" -#: ../../content/legal/terms/enterprise.rst:215 +#: ../../content/legal/terms/enterprise.rst:225 msgid "Disaster Recovery Plan, tested regularly" msgstr "" -#: ../../content/legal/terms/enterprise.rst:217 +#: ../../content/legal/terms/enterprise.rst:227 msgid "The details of the Cloud Hosting Services are described on the Service Level Agreement page at https://www.odoo.com/cloud-sla." msgstr "" -#: ../../content/legal/terms/enterprise.rst:224 +#: ../../content/legal/terms/enterprise.rst:234 msgid "4.5 Support Services" msgstr "" -#: ../../content/legal/terms/enterprise.rst:227 +#: ../../content/legal/terms/enterprise.rst:237 msgid "Scope" msgstr "" -#: ../../content/legal/terms/enterprise.rst:229 +#: ../../content/legal/terms/enterprise.rst:239 msgid "For the duration of this Agreement, the Customer may open an unlimited number of support tickets free of charge, exclusively for questions regarding Bugs (see :ref:`bugfix`) or guidance with respect to the use of the standard features of the Software and Covered Extra Modules." msgstr "" -#: ../../content/legal/terms/enterprise.rst:233 +#: ../../content/legal/terms/enterprise.rst:243 msgid "Other assistance requests, such as questions related to development or customizations may be covered through the purchase of a separate service agreement. In case it’s not clear if a request is covered by this Agreement, the decision is at the discretion of Odoo SA." msgstr "" -#: ../../content/legal/terms/enterprise.rst:239 +#: ../../content/legal/terms/enterprise.rst:249 msgid "Availability" msgstr "" -#: ../../content/legal/terms/enterprise.rst:241 +#: ../../content/legal/terms/enterprise.rst:251 msgid "Tickets can be submitted via the web form or phone numbers listed on `odoo.com/help `_, or when working with an Odoo Partner, the channel provided by the partner, subject to local opening hours." msgstr "" -#: ../../content/legal/terms/enterprise.rst:249 +#: ../../content/legal/terms/enterprise.rst:259 msgid "4.6 Working with an Odoo Partner" msgstr "" -#: ../../content/legal/terms/enterprise.rst:251 +#: ../../content/legal/terms/enterprise.rst:261 msgid "For bug fixes, support and upgrade services, the Customer may either work with an Odoo Partner as the main point of contact, or work with Odoo SA directly." msgstr "" -#: ../../content/legal/terms/enterprise.rst:254 +#: ../../content/legal/terms/enterprise.rst:264 msgid "If the Customer decides to work with an Odoo Partner, Odoo SA will subcontract services related to the Covered Extra Modules to the Odoo Partner, who becomes the main point of contact of the customer. The Odoo Partner may contact Odoo SA on behalf of the customer for second-level assistance with regard to standard features of the Software." msgstr "" -#: ../../content/legal/terms/enterprise.rst:259 +#: ../../content/legal/terms/enterprise.rst:269 msgid "If the Customer decides to work with Odoo SA directly, services related to Covered Extra Modules are provided *if and only if* the Customer is hosted on the Odoo Cloud Platform." msgstr "" -#: ../../content/legal/terms/enterprise.rst:266 +#: ../../content/legal/terms/enterprise.rst:276 msgid "5 Charges and Fees" msgstr "" -#: ../../content/legal/terms/enterprise.rst:271 +#: ../../content/legal/terms/enterprise.rst:281 msgid "5.1 Standard charges" msgstr "" -#: ../../content/legal/terms/enterprise.rst:273 -msgid "The standard charges for the Odoo Enterprise subscription and the Services are based on the number of Users and the installed Apps used by the Customer, and specified in writing at the conclusion of the Agreement." +#: ../../content/legal/terms/enterprise.rst:283 +msgid "The standard charges for the Odoo Enterprise subscription and the Services are based on the number of Users and the Subscription Plan used by the Customer, and specified in writing at the conclusion of the Agreement." msgstr "" -#: ../../content/legal/terms/enterprise.rst:277 -msgid "When during the Term, the Customer has more Users or more installed Apps than specified at the time of conclusion of this Agreement, the Customer agrees to pay an extra fee equivalent to the applicable list price (at the beginning of the Term) for the additional Users or Apps, for the remainder of the Term." +#: ../../content/legal/terms/enterprise.rst:287 +msgid "When during the Term, the Customer has more Users or uses features that require another Subscription Plan than specified at the time of conclusion of this Agreement, the Customer agrees to pay an extra fee equivalent to the applicable list price (at the time of the deviation from the specified number of Users or Subscription Plan) for the additional Users or the required Subscription Plan, for the remainder of the Term." msgstr "" -#: ../../content/legal/terms/enterprise.rst:281 -msgid "In addition, services for Covered Extra Modules are charged based on the number of lines of code in these modules. When the Customer opts for the maintenance of Covered Extra Modules, the charge is a monthly fee of 16€ per 100 lines of code (rounded up to the next hundred), unless otherwise specified in writing at the conclusion of the Agreement. Lines of code will be counted with the ``cloc`` command of the Software, and include all text lines in the source code of those modules, regardless of the programming language (Python, Javascript, XML, etc.), excluding blank lines, comment lines and files that are not loaded when installing or executing the Software." +#: ../../content/legal/terms/enterprise.rst:293 +msgid "In addition, services for Covered Extra Modules are charged based on the number of lines of code in these modules. When the Customer opts for the maintenance of Covered Extra Modules, the charge is a monthly fee per 100 lines of code (rounded up to the next hundred), as specified in writing at the conclusion of the Agreement. Lines of code will be counted with the ``cloc`` command of the Software, and include all text lines in the source code of those modules, regardless of the programming language (Python, Javascript, XML, etc.), excluding blank lines, comment lines and files that are not loaded when installing or executing the Software." msgstr "" -#: ../../content/legal/terms/enterprise.rst:289 -msgid "When the Customer requests an upgrade, for each Covered Extra Module that has not been covered by a maintenance fee for the last 12 months, Odoo SA may charge a one-time extra fee of 16€ per 100 lines of code, for each missing month of coverage." +#: ../../content/legal/terms/enterprise.rst:301 +msgid "When the Customer requests an upgrade, for each Covered Extra Module that has not been covered by a maintenance fee for the last 12 months, Odoo SA may charge a one-time extra fee for each missing month of coverage." msgstr "" -#: ../../content/legal/terms/enterprise.rst:296 +#: ../../content/legal/terms/enterprise.rst:308 msgid "5.2 Renewal charges" msgstr "" -#: ../../content/legal/terms/enterprise.rst:298 -msgid "Upon renewal as covered in section :ref:`term`, if the charges applied during the previous Term (excluding any “Initial User Discounts”) are lower than the most current applicable list price, these charges will increase by up to 7%." +#: ../../content/legal/terms/enterprise.rst:310 +msgid "Upon renewal as covered in section :ref:`term`, if the charges applied during the previous Term are lower than the most current applicable list price, these charges will increase by up to 7%." msgstr "" -#: ../../content/legal/terms/enterprise.rst:305 +#: ../../content/legal/terms/enterprise.rst:316 msgid "5.3 Taxes" msgstr "" -#: ../../content/legal/terms/enterprise.rst:309 +#: ../../content/legal/terms/enterprise.rst:320 msgid "All fees and charges are exclusive of all applicable federal, provincial, state, local or other governmental taxes, fees or charges (collectively, \"Taxes\"). The Customer is responsible for paying all Taxes associated with purchases made by the Customer under this Agreement, except when Odoo SA is legally obliged to pay or collect Taxes for which the Customer is responsible." msgstr "" -#: ../../content/legal/terms/enterprise.rst:318 +#: ../../content/legal/terms/enterprise.rst:329 msgid "6 Conditions of Services" msgstr "" -#: ../../content/legal/terms/enterprise.rst:321 +#: ../../content/legal/terms/enterprise.rst:332 msgid "6.1 Customer Obligations" msgstr "" -#: ../../content/legal/terms/enterprise.rst:323 +#: ../../content/legal/terms/enterprise.rst:334 msgid "The Customer agrees to:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:325 +#: ../../content/legal/terms/enterprise.rst:336 msgid "pay Odoo SA any applicable charges for the Services of the present Agreement, in accordance with the payment conditions specified at the signature of this contract ;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:327 -msgid "immediately notify Odoo SA when their actual number of Users or their installed Apps exceed the numbers specified at the conclusion of the Agreement, and in this event, pay the applicable additional fee as described in section :ref:`charges_standard`;" -msgstr "" - -#: ../../content/legal/terms/enterprise.rst:330 -msgid "take all measures necessary to guarantee the unmodified execution of the part of the Software that verifies the validity of the Odoo Enterprise Edition usage, as described in :ref:`enterprise_access` ;" -msgstr "" - -#: ../../content/legal/terms/enterprise.rst:333 -msgid "appoint 1 dedicated Customer contact person for the entire duration of the Agreement;" -msgstr "" - -#: ../../content/legal/terms/enterprise.rst:334 -msgid "provide written notice to Odoo SA 30 days before changing their main point of contact to work with another Odoo Partner, or to work with Odoo SA directly." -msgstr "" - -#: ../../content/legal/terms/enterprise.rst:337 -msgid "When the Customer chooses to use the Cloud Platform, the Customer further agrees to:" -msgstr "" - -#: ../../content/legal/terms/enterprise.rst:339 -msgid "take all reasonable measures to keep their user accounts secure, including by choosing a strong password and not sharing it with anyone else;" +#: ../../content/legal/terms/enterprise.rst:338 +msgid "immediately notify Odoo SA when their actual number of Users exceeds the number specified at the conclusion of the Agreement, and in this event, pay the applicable additional fee as described in section :ref:`charges_standard`;" msgstr "" #: ../../content/legal/terms/enterprise.rst:341 -msgid "make a reasonable use of the Hosting Services, to the exclusion of any illegal or abusive activities, and strictly observe the rules outlined in the Acceptable Use Policy published at https://www.odoo.com/acceptable-use." +msgid "take all measures necessary to guarantee the unmodified execution of the part of the Software that verifies the validity of the Odoo Enterprise Edition usage, as described in :ref:`enterprise_access` ;" +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:344 +msgid "appoint 1 dedicated Customer contact person for the entire duration of the Agreement;" msgstr "" #: ../../content/legal/terms/enterprise.rst:345 -msgid "When the Customer chooses the Self-Hosting option, the Customer further agrees to:" +msgid "provide written notice to Odoo SA 30 days before changing their main point of contact to work with another Odoo Partner, or to work with Odoo SA directly." msgstr "" -#: ../../content/legal/terms/enterprise.rst:347 -msgid "take all reasonable measures to protect Customer’s files and databases and to ensure Customer’s data is safe and secure, acknowledging that Odoo SA cannot be held liable for any data loss;" +#: ../../content/legal/terms/enterprise.rst:348 +msgid "When the Customer chooses to use the Cloud Platform, the Customer further agrees to:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:349 -msgid "grant Odoo SA the necessary access to verify the validity of the Odoo Enterprise Edition usage upon request (e.g. if the automatic validation is found to be inoperant for the Customer);" +#: ../../content/legal/terms/enterprise.rst:350 +msgid "take all reasonable measures to keep their user accounts secure, including by choosing a strong password and not sharing it with anyone else;" +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:352 +msgid "make a reasonable use of the Hosting Services, to the exclusion of any illegal or abusive activities, and strictly observe the rules outlined in the Acceptable Use Policy published at https://www.odoo.com/acceptable-use." msgstr "" #: ../../content/legal/terms/enterprise.rst:356 -msgid "6.2 No Soliciting or Hiring" +msgid "When the Customer chooses the Self-Hosting option, the Customer further agrees to:" msgstr "" #: ../../content/legal/terms/enterprise.rst:358 +msgid "take all reasonable measures to protect Customer’s files and databases and to ensure Customer’s data is safe and secure, acknowledging that Odoo SA cannot be held liable for any data loss;" +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:360 +msgid "grant Odoo SA the necessary access to verify the validity of the Odoo Enterprise Edition usage upon request (e.g. if the automatic validation is found to be inoperant for the Customer)." +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:367 +msgid "6.2 No Soliciting or Hiring" +msgstr "" + +#: ../../content/legal/terms/enterprise.rst:369 msgid "Except where the other party gives its consent in writing, each party, its affiliates and representatives agree not to solicit or offer employment to any employee of the other party who is involved in performing or using the Services under this Agreement, for the duration of the Agreement and for a period of 12 months from the date of termination or expiration of this Agreement. In case of any breach of the conditions of this section that leads to the termination of said employee toward that end, the breaching party agrees to pay to the other party an amount of EUR (€) 30 000.00 (thirty thousand euros)." msgstr "" -#: ../../content/legal/terms/enterprise.rst:370 +#: ../../content/legal/terms/enterprise.rst:381 msgid "6.3 Publicity" msgstr "" -#: ../../content/legal/terms/enterprise.rst:372 +#: ../../content/legal/terms/enterprise.rst:383 msgid "Except where notified otherwise in writing, each party grants the other a non-transferable, non-exclusive, royalty free, worldwide license to reproduce and display the other party’s name, logos and trademarks, solely for the purpose of referring to the other party as a customer or supplier, on websites, press releases and other marketing materials." msgstr "" -#: ../../content/legal/terms/enterprise.rst:381 +#: ../../content/legal/terms/enterprise.rst:392 msgid "6.4 Confidentiality" msgstr "" -#: ../../content/legal/terms/enterprise.rst:389 +#: ../../content/legal/terms/enterprise.rst:400 msgid "Definition of \"Confidential Information\":" msgstr "" -#: ../../content/legal/terms/enterprise.rst:384 +#: ../../content/legal/terms/enterprise.rst:395 msgid "All information disclosed by a party (the \"Disclosing Party\") to the other party (the \"Receiving Party\"), whether orally or in writing, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure. In particular any information related to the business, affairs, products, developments, trade secrets, know-how, personnel, customers and suppliers of either party should be regarded as confidential." msgstr "" -#: ../../content/legal/terms/enterprise.rst:391 +#: ../../content/legal/terms/enterprise.rst:402 msgid "For all Confidential Information received during the Term of this Agreement, the Receiving Party will use the same degree of care that it uses to protect the confidentiality of its own similar Confidential Information, but not less than reasonable care." msgstr "" -#: ../../content/legal/terms/enterprise.rst:395 +#: ../../content/legal/terms/enterprise.rst:406 msgid "The Receiving Party may disclose Confidential Information of the Disclosing Party to the extent compelled by law to do so, provided the Receiving Party gives the Disclosing Party prior notice of the compelled disclosure, to the extent permitted by law." msgstr "" -#: ../../content/legal/terms/enterprise.rst:403 +#: ../../content/legal/terms/enterprise.rst:414 msgid "6.5 Data Protection" msgstr "" -#: ../../content/legal/terms/enterprise.rst:409 +#: ../../content/legal/terms/enterprise.rst:420 msgid "Definitions" msgstr "" -#: ../../content/legal/terms/enterprise.rst:406 +#: ../../content/legal/terms/enterprise.rst:417 msgid "\"Personal Data\", \"Controller\", \"Processing\" take the same meanings as in the Regulation (EU) 2016/679 and the Directive 2002/58/EC, and any regulation or legislation that amends or replaces them (hereafter referred to as “Data Protection Legislation”)" msgstr "" -#: ../../content/legal/terms/enterprise.rst:412 +#: ../../content/legal/terms/enterprise.rst:423 msgid "Processing of Personal Data" msgstr "" -#: ../../content/legal/terms/enterprise.rst:414 +#: ../../content/legal/terms/enterprise.rst:425 msgid "The parties acknowledge that the Customer's database may contain Personal Data, for which the Customer is the Controller. This data will be processed by Odoo SA when the Customer instructs so, by using any of the Services that require a database (e.g. the Cloud Hosting Services or the Database Upgrade Service), or if the Customer transfers their database or a part of their database to Odoo SA for any reason pertaining to this Agreement." msgstr "" -#: ../../content/legal/terms/enterprise.rst:420 +#: ../../content/legal/terms/enterprise.rst:431 msgid "This processing will be performed in conformance with Data Protection Legislation. In particular, Odoo SA commits to:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:423 +#: ../../content/legal/terms/enterprise.rst:434 msgid "(a) only process the Personal Data when and as instructed by the Customer, and for the purpose of performing one of the Services under this Agreement, unless required by law to do so, in which case Odoo SA will provide prior notice to the Customer, unless the law forbids it ;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:427 +#: ../../content/legal/terms/enterprise.rst:438 msgid "(b) ensure that all persons within Odoo SA authorised to process the Personal Data have committed themselves to confidentiality ;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:429 +#: ../../content/legal/terms/enterprise.rst:440 msgid "(c) implement and maintain appropriate technical and organizational measures to protect the Personal Data against unauthorized or unlawful processing and against accidental loss, destruction, damage, theft, alteration or disclosure ;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:432 +#: ../../content/legal/terms/enterprise.rst:443 msgid "(d) forward promptly to the Customer any Data Protection request that was submitted to Odoo SA with regard to the Customer's database ;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:434 +#: ../../content/legal/terms/enterprise.rst:445 msgid "(e) notify the Customer promptly upon becoming aware of and confirming any accidental, unauthorized, or unlawful processing of, disclosure of, or access to the Personal Data ;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:436 +#: ../../content/legal/terms/enterprise.rst:447 msgid "(f) notify the Customer if the processing instructions infringe applicable Data Protection Legislation, in the opinion of Odoo SA;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:438 +#: ../../content/legal/terms/enterprise.rst:449 msgid "(g) make available to the Customer all information necessary to demonstrate compliance with the Data Protection Legislation, allow for and contribute reasonably to audits, including inspections, conducted or mandated by the Customer;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:441 +#: ../../content/legal/terms/enterprise.rst:452 msgid "(h) permanently delete all copies of the Customer's database in possession of Odoo SA, or return such data, at the Customer’s choice, upon termination of this Agreement, subject to the delays specified in Odoo SA's `Privacy Policy `_ ;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:446 +#: ../../content/legal/terms/enterprise.rst:457 msgid "With regard to points (d) to (f), the Customer agrees to provide Odoo SA with accurate contact information at all times, as necessary to notify the Customer's Data Protection responsible." msgstr "" -#: ../../content/legal/terms/enterprise.rst:450 +#: ../../content/legal/terms/enterprise.rst:461 msgid "Subprocessors" msgstr "" -#: ../../content/legal/terms/enterprise.rst:452 +#: ../../content/legal/terms/enterprise.rst:463 msgid "The Customer acknowledges and agrees that in order to provide the Services, Odoo SA may use third-party service providers (Subprocessors) to process Personal Data. Odoo SA commits to only use Subprocessors in compliance with Data Protection Legislation. This use will be covered by a contract between Odoo SA and the Subprocessor that provides guarantees to that effect. Odoo SA's Privacy Policy, published at https://www.odoo.com/privacy provides up-to-date information regarding the names and purposes of Subprocessors currently in use by Odoo SA for the execution of the Services." msgstr "" -#: ../../content/legal/terms/enterprise.rst:464 +#: ../../content/legal/terms/enterprise.rst:475 msgid "6.6 Termination" msgstr "" -#: ../../content/legal/terms/enterprise.rst:466 +#: ../../content/legal/terms/enterprise.rst:477 msgid "In the event that either Party fails to fulfill any of its obligations arising herein, and if such breach has not been remedied within 30 calendar days from the written notice of such breach, this Agreement may be terminated immediately by the non-breaching Party." msgstr "" -#: ../../content/legal/terms/enterprise.rst:470 +#: ../../content/legal/terms/enterprise.rst:481 msgid "Further, Odoo SA may terminate the Agreement immediately in the event the Customer fails to pay the applicable fees for the Services within 21 days following the due date specified on the corresponding invoice, and after minimum 3 reminders." msgstr "" -#: ../../content/legal/terms/enterprise.rst:478 -#: ../../content/legal/terms/partnership.rst:247 +#: ../../content/legal/terms/enterprise.rst:489 +#: ../../content/legal/terms/partnership.rst:263 msgid "Surviving Provisions:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:475 +#: ../../content/legal/terms/enterprise.rst:486 msgid "The sections \":ref:`confidentiality`”, “:ref:`disclaimers`”, “:ref:`liability`”, and “:ref:`general_provisions`” will survive any termination or expiration of this Agreement." msgstr "" -#: ../../content/legal/terms/enterprise.rst:483 +#: ../../content/legal/terms/enterprise.rst:494 msgid "7 Warranties, Disclaimers, Liability" msgstr "" -#: ../../content/legal/terms/enterprise.rst:488 +#: ../../content/legal/terms/enterprise.rst:499 msgid "7.1 Warranties" msgstr "" -#: ../../content/legal/terms/enterprise.rst:492 +#: ../../content/legal/terms/enterprise.rst:503 msgid "Odoo SA owns the copyright or an equivalent [#cla1]_ on 100% of the code of the Software, and confirms that all the software libraries required to use the Software are available under a licence compatible with the licence of the Software." msgstr "" -#: ../../content/legal/terms/enterprise.rst:496 +#: ../../content/legal/terms/enterprise.rst:507 msgid "For the duration of this Agreement, Odoo SA commits to using commercially reasonable efforts to execute the Services in accordance with the generally accepted industry standards provided that:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:499 +#: ../../content/legal/terms/enterprise.rst:510 msgid "the Customer’s computing systems are in good operational order and, for Self-Hosting, that the Software is installed in a suitable operating environment;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:501 +#: ../../content/legal/terms/enterprise.rst:512 msgid "the Customer provides adequate troubleshooting information and, for Self-Hosting, any access that Odoo SA may need to identify, reproduce and address problems;" msgstr "" -#: ../../content/legal/terms/enterprise.rst:503 +#: ../../content/legal/terms/enterprise.rst:514 msgid "all amounts due to Odoo SA have been paid." msgstr "" -#: ../../content/legal/terms/enterprise.rst:505 +#: ../../content/legal/terms/enterprise.rst:516 msgid "The Customer's sole and exclusive remedy and Odoo SA's only obligation for any breach of this warranty is for Odoo SA to resume the execution of the Services at no additional charge." msgstr "" -#: ../../content/legal/terms/enterprise.rst:509 +#: ../../content/legal/terms/enterprise.rst:520 msgid "External contributions are covered by a `Copyright License Agreement `_ that provides a permanent, free and irrevocable, copyright and patent licence to Odoo SA." msgstr "" -#: ../../content/legal/terms/enterprise.rst:515 +#: ../../content/legal/terms/enterprise.rst:526 msgid "7.2 Disclaimers" msgstr "" -#: ../../content/legal/terms/enterprise.rst:519 +#: ../../content/legal/terms/enterprise.rst:530 msgid "Except as expressly provided herein, neither party makes any warranty of any kind, whether express, implied, statutory or otherwise, and each party specifically disclaims all implied warranties, including any implied warranty of merchantability, fitness for a particular purpose or non-infringement, to the maximum extent permitted by applicable law." msgstr "" -#: ../../content/legal/terms/enterprise.rst:524 +#: ../../content/legal/terms/enterprise.rst:535 msgid "Odoo SA does not warrant that the Software complies with any local or international law or regulations." msgstr "" -#: ../../content/legal/terms/enterprise.rst:529 +#: ../../content/legal/terms/enterprise.rst:540 msgid "7.3 Limitation of Liability" msgstr "" -#: ../../content/legal/terms/enterprise.rst:531 +#: ../../content/legal/terms/enterprise.rst:542 msgid "To the maximum extent permitted by law, the aggregate liability of each party together with its affiliates arising out of or related to this Agreement will not exceed 50% of the total amount paid by the Customer under this Agreement during the 12 months immediately preceding the date of the event giving rise to such claim. Multiple claims shall not enlarge this limitation." msgstr "" -#: ../../content/legal/terms/enterprise.rst:536 -msgid "In no event will either party or its affiliates be liable for any indirect, special, exemplary, incidental or consequential damages of any kind, including but not limited to loss of revenue, profits, savings, loss of business or other financial loss, costs of standstill or delay, lost or corrupted data, arising out of or in connection with this Agreement regardless of the form of action, whether in contract, tort (including strict negligence) or any other legal or equitable theory, even if a party or its affiliates have been advised of the possibility of such damages, or if a party or its affiliates' remedy otherwise fails of its essential purpose." +#: ../../content/legal/terms/enterprise.rst:547 +msgid "In no event will either party or its affiliates be liable for any indirect, special, exemplary, incidental or consequential damages of any kind, including but not limited to loss of revenue, profits, savings, loss of business or other financial loss, costs of standstill or delay, lost or corrupted data, arising out of or in connection with this Agreement regardless of the form of action, whether in contract, tort or otherwise, even if a party or its affiliates have been advised of the possibility of such damages, or if a party or its affiliates' remedy otherwise fails of its essential purpose." msgstr "" -#: ../../content/legal/terms/enterprise.rst:547 -#: ../../content/legal/terms/i18n/enterprise_fr.rst:584 +#: ../../content/legal/terms/enterprise.rst:558 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:591 msgid "7.4 Force Majeure" msgstr "" -#: ../../content/legal/terms/enterprise.rst:549 +#: ../../content/legal/terms/enterprise.rst:560 msgid "Neither party shall be liable to the other party for the delay in any performance or failure to render any performance under this Agreement when such failure or delay finds its cause in a case of *force majeure*, such as governmental regulations, fire, strike, war, flood, accident, epidemic, embargo, appropriation of plant or product in whole or in part by any government or public authority, or any other cause or causes, whether of like or different nature, beyond the reasonable control of such party as long as such cause or causes exist." msgstr "" -#: ../../content/legal/terms/enterprise.rst:561 +#: ../../content/legal/terms/enterprise.rst:572 msgid "8 General Provisions" msgstr "" -#: ../../content/legal/terms/enterprise.rst:566 +#: ../../content/legal/terms/enterprise.rst:577 msgid "8.1 Governing Law" msgstr "" -#: ../../content/legal/terms/enterprise.rst:568 +#: ../../content/legal/terms/enterprise.rst:579 msgid "This Agreement and all Customer orders will be subject to Belgian law. Any dispute arising out of or in connection with this Agreement or any Customer order will be subject to the exclusive jurisdiction of the Nivelles Business Court." msgstr "" -#: ../../content/legal/terms/enterprise.rst:576 +#: ../../content/legal/terms/enterprise.rst:587 msgid "8.2 Severability" msgstr "" -#: ../../content/legal/terms/enterprise.rst:578 +#: ../../content/legal/terms/enterprise.rst:589 msgid "In case any one or more of the provisions of this Agreement or any application thereof shall be invalid, illegal or unenforceable in any respect, the validity, legality and enforceability of the remaining provisions of this Agreement and any application thereof shall be in no way thereby affected or impaired. Both parties undertake to replace any invalid, illegal or unenforceable provision of this Agreement by a valid provision having the same effects and objectives." msgstr "" -#: ../../content/legal/terms/enterprise.rst:589 +#: ../../content/legal/terms/enterprise.rst:600 msgid "9 Appendix A: Odoo Enterprise Edition License" msgstr "" -#: ../../content/legal/terms/enterprise.rst:593 +#: ../../content/legal/terms/enterprise.rst:604 msgid "Odoo Enterprise Edition is licensed under the Odoo Enterprise Edition License v1.0, defined as follows:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:602 -#: ../../content/legal/terms/i18n/partnership_es.rst:372 -#: ../../content/legal/terms/partnership.rst:380 +#: ../../content/legal/terms/enterprise.rst:613 +#: ../../content/legal/terms/i18n/partnership_es.rst:393 +#: ../../content/legal/terms/partnership.rst:396 msgid "See :ref:`odoo_enterprise_license`." msgstr "" -#: ../../content/legal/terms/enterprise.rst:613 +#: ../../content/legal/terms/enterprise.rst:624 msgid "Agreement Registration" msgstr "" -#: ../../content/legal/terms/enterprise.rst:616 +#: ../../content/legal/terms/enterprise.rst:627 msgid "Customer contact information" msgstr "" -#: ../../content/legal/terms/enterprise.rst:618 +#: ../../content/legal/terms/enterprise.rst:629 msgid "Company name: Company address: VAT number (if applicable): Contact name: Email: Phone:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:626 +#: ../../content/legal/terms/enterprise.rst:637 msgid "Technical contact information (can be an Odoo partner):" msgstr "" -#: ../../content/legal/terms/enterprise.rst:627 +#: ../../content/legal/terms/enterprise.rst:638 msgid "Company name: Contact name: Email: Phone:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:633 +#: ../../content/legal/terms/enterprise.rst:644 msgid "By signing this Agreement I confirm I am a legal representative of Customer as stated in the resent section and approve all provisions and conditions of the present Agreement:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:636 +#: ../../content/legal/terms/enterprise.rst:647 msgid "For and on behalf of (company name): Last name, first name: Title: Date:" msgstr "" -#: ../../content/legal/terms/enterprise.rst:641 +#: ../../content/legal/terms/enterprise.rst:652 msgid "Signature:" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:6 -msgid "Odoo Enterprise Subscription Agreement (DE)" +msgid "Odoo Enterprise Abonnementsvertrag" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:9 -msgid "Dies ist eine deutsche Übersetzung des \"Odoo Enterprise Subscription Agreement\". Diese Übersetzung soll das Verständnis erleichtern, hat aber keinen rechtlichen Wert. Der einzige offizielle Verweis auf die Geschäftsbedingungen des „Odoo Enterprise Subscription Agreement“ ist :ref:`die englische Originalversion `." +#: ../../content/legal/terms/i18n/enterprise_de.rst:10 +msgid "`Download PDF `_" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:15 -msgid "DIESE VERSION IST NICHT AKTUELL, FÜR DIE AKTUELLE VERSION SIEHE :ref:`original english version `" +#: ../../content/legal/terms/i18n/enterprise_de.rst:12 +msgid "Dies ist eine deutsche Übersetzung des \"Odoo Enterprise Subscription Agreement\". Diese Übersetzung soll das Verständnis erleichtern, hat aber keinen rechtlichen Wert. Der einzige offizielle Verweis auf die Geschäftsbedingungen des \"Odoo Enterprise Subscription Agreement\" ist :ref:`die englische Original version `." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:22 -#: ../../content/legal/terms/i18n/enterprise_nl.rst:24 -msgid "Version 7.1 - 2018-03-16" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:24 -msgid "Durch das Abonnieren der von der Odoo SA und ihren Tochtergesellschaften (zusammen „Odoo SA“) hinsichtlich der Odoo Enterprise Edition oder der Odoo Community Edition (der „Software“) bereitgestellten Odoo Enterprise-Dienstleistungen (der „Dienste“) sind Sie (der „Kunde“) verpflichtet, die nachstehenden Allgemeinen Geschäftsbedingungen (die „Vereinbarung“) einzuhalten." +#: ../../content/legal/terms/i18n/enterprise_de.rst:18 +msgid "DIESE VERSION IST NICHT AKTUELL, FÜR DIE AKTUELLE VERSION SIEHE :ref:`original english version `." msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:32 -msgid "1. Laufzeit der Vereinbarung" +#: ../../content/legal/terms/i18n/enterprise_es.rst:19 +msgid "Version 9c - 2020-06-15" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:34 -msgid "Die Dauer dieser Vereinbarung (die „Laufzeit“) beträgt mindestens ein Jahr wie schriftlich bei Unterzeichnung dieser Vereinbarung festgelegt, beginnend zum Datum der Unterschrift. Sie wird automatisch um die gleiche Laufzeit verlängert, sofern nicht eine der Parteien mindestens 30 Tage vor Ablauf der Laufzeit gegenüber der anderen Partei per Einschreiben schriftlich kündigt." +msgid "Indem Sie (der \"Kunde\") die Odoo Enterprise-Dienstleistungen (die \"Dienstleistungen\"), die von Odoo SA und seinen verbundenen Unternehmen (zusammen \"Odoo SA\") in Verbindung mit der Odoo Enterprise Edition oder der Odoo Community Edition (die \"Software\") bereitgestellt und auf den Cloud- Plattformen von Odoo SA (die \"Cloud-Plattform\") oder vor Ort (\"Self-Hosting\") gehostet werden, abonnieren, erklären Sie sich mit den folgenden Bedingungen einverstanden (die \"Vereinbarung\")." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:42 -msgid "2. Definitionen" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:49 -msgid "Benutzer" +#: ../../content/legal/terms/i18n/enterprise_de.rst:43 +msgid "1. Laufzeit der Vereinbarung" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:45 -msgid "Alle aktiven Benutzerkonten mit Zugriff auf die Software im Erstellungs- und/oder Bearbeitungsmodus. Deaktivierte Benutzerkonten und Konten, die von externen Personen (oder Systemen) verwendet werden, die über das Portal nur eingeschränkten Zugriff auf die Software haben („Portalbenutzer“ genannt), werden nicht als Benutzer gezählt." +msgid "Die Dauer dieser Vereinbarung (die \"Laufzeit\") wird bei Abschluss dieser Vereinbarung schriftlich festgelegt und beginnt mit dem Datum des Abschlusses. Sie verlängert sich automatisch um die gleiche Laufzeit, es sei denn, eine der beiden Parteien kündigt die Vereinbarung mindestens 30 Tage vor Ablauf der Laufzeit schriftlich gegenüber der anderen Partei." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:52 -msgid "Eine „App“ ist eine spezielle Gruppe von Funktionen, die in der Software installiert werden können und bei Unterzeichnung dieser Vereinbarung in der öffentlichen Preisliste der `Odoo SA-Website `_ aufgeführt sind." +#: ../../content/legal/terms/i18n/enterprise_de.rst:53 +msgid "2. Definitionen" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:63 -msgid "Fehler (Bug)" +#: ../../content/legal/terms/i18n/enterprise_de.rst:59 +msgid "Benutzer" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:57 -msgid "Als Fehler (oder auch Bug) gilt jeder Fehler der Software, der zu einem vollständigen Stopp, einer Traceback-Fehlermeldung oder einer Sicherheitsverletzung führt und nicht direkt durch eine fehlerhafte Installation oder Konfiguration verursacht wird. Eine Nichteinhaltung von Spezifikationen oder Anforderungen wird im Ermessen von Odoo SA als Fehler angesehen (in der Regel dann, wenn die Software nicht die Ergebnisse oder die Leistungswerte liefert, für die sie entwickelt wurde oder wenn eine landesspezifische Funktion nicht mehr den gesetzlichen Buchhaltungsanforderungen entspricht)." +#: ../../content/legal/terms/i18n/enterprise_de.rst:56 +msgid "Jedes Benutzerkonto, das in der Software als aktiv angegeben ist und Zugang zum Erstell- und/oder Bearbeitungsmodus hat. Deaktivierte Benutzerkonten und Konten, die von externen Personen (oder Systemen) verwendet werden, die nur begrenzten Zugang zur Software über die Portalfunktionen haben (\"Portalbenutzer\"), werden nicht als Benutzer gezählt." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:62 +msgid "Eine \"App\" ist eine spezielle Gruppe von Funktionen, die zur Installation in der Software zur Verfügung steht und in der öffentlichen Preisliste der `Odoo SA-Website `_ aufgeführt ist." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:70 +msgid "Odoo-Partner" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:67 +msgid "Ein Odoo-Partner ist ein Drittunternehmen oder eine Einzelperson, die vom Kunden ausgewählt wurde und mit dem Kunden hinsichtlich seiner Dienstleistungen im Zusammenhang mit Odoo zusammenarbeitet. Der Kunde kann jederzeit entscheiden, mit einem anderen Odoo-Partner oder direkt mit Odoo SA zusammenzuarbeiten (nach vorheriger Ankündigung)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:76 +msgid "Zusatzmodul" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:73 -msgid "Abgedeckte Versionen" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:66 -msgid "Alle im Rahmen Vereinbarung erbrachten Dienstleistungen gelten nur für die abgedeckten Versionen der Software, welche die 3 (drei) zuletzt veröffentlichten Hauptversionen umfassen." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:69 -msgid "Um von der aktuellen Vereinbarung abgedeckt zu sein, müssen die Installationen des Kunden die aktuellste abgedeckte Version zum Zeitpunkt der Unterzeichnung dieser Vereinbarung aufweisen. Sollte dies nicht der Fall sein, so können zusätzliche Kosten anfallen, die unter :ref:`charges_de` beschrieben werden." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:78 -msgid "3. Zugriff auf die Odoo Enterprise Edition" +msgid "Ein Zusatzmodul ist ein Verzeichnis von Quellcodedateien oder eine Reihe von Python-basierten Anpassungen, die in einer Datenbank erstellt (z. B. mit Odoo Studio) wurden, das der Software Funktionen hinzufügt oder ihr Standardverhalten ändert. Es kann vom Kunden, von Odoo SA, von einem Odoo-Partner im Namen des Kunden oder von Dritten entwickelt worden sein." msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:80 -msgid "Für die Laufzeit dieser Vereinbarung gewährt Odoo SA dem Kunden eine nicht-ausschließliche, nicht übertragbare Nutzungslizenz (Ausführung, Änderung, Ausführung nach Änderung) der Odoo Enterprise Edition-Software unter den in :ref:`appendix_a_de` festgelegten Bedingungen." +msgid "Odoo unterstütztes Zusatzmodul" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:84 -msgid "Der Kunde erklärt, alle notwendigen Maßnahmen zu ergreifen, um die unveränderte Ausführung des Teils der Software zu gewährleisten, mit dem die gültige Nutzung der Odoo Enterprise Edition überprüft wird und die zu diesem Zweck Statistiken sammelt, einschließlich unter anderem die Ausführung einer Instanz, die Anzahl der Benutzer und die installierten Apps." +#: ../../content/legal/terms/i18n/enterprise_de.rst:79 +msgid "Ein unterstütztes Zusatzmodul ist ein Zusatzmodul, für das der Kunde eine Wartungsgebühr entrichtet, um Support-, Upgrade- und Fehlerbehebungsdienste zu erhalten." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:89 -msgid "Odoo SA ist verpflichtet, einzelne keine einzelnen oder benannten Zahlen ohne Zustimmung des Kunden an Dritte weiterzugeben und alle gesammelten Daten gemäß seiner offiziellen Datenschutzrichtlinie zu behandeln, die unter https://www.odoo.com/privacy veröffentlicht ist." +#: ../../content/legal/terms/i18n/enterprise_de.rst:83 +msgid "Als Bug gilt jeder Ausfall der Software oder eines unterstützten Zusatzmoduls, der zu einem vollständigen Stopp, einer Fehlersuche oder einer Sicherheitsverletzung führt und nicht direkt durch eine fehlerhafte Installation oder Konfiguration verursacht wird. Die Nichteinhaltung von Spezifikationen oder Anforderungen wird nach dem Ermessen von Odoo SA als Bug betrachtet (typischerweise, wenn die Software nicht die Ergebnisse oder die Leistung erbringt, für die sie entwickelt wurde, oder wenn eine länderspezifische Funktion nicht mehr den gesetzlichen Buchhaltungsanforderungen entspricht)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:93 -msgid "Nach Ablauf oder Kündigung dieser Vereinbarung wird diese Lizenz sofort widerrufen und der Kunde ist verpflichtet, die Nutzung der Odoo Enterprise Edition-Software einzustellen." +#: ../../content/legal/terms/i18n/enterprise_de.rst:94 +msgid "Unterstützte Versionen" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:96 -msgid "Sollte der Kunde gegen die Bestimmungen dieses Abschnitts verstoßen, so ist er verpflichtet, Odoo SA eine zusätzliche Gebühr in Höhe von 300 % des geltenden Listenpreises für die tatsächliche Anzahl der Nutzer zu zahlen." +#: ../../content/legal/terms/i18n/enterprise_de.rst:92 +msgid "Sofern nicht anders angegeben, gelten die im Rahmen dieser Vereinbarung erbrachten Dienstleistungen nur für die unterstützten Versionen der Software, zu denen die drei zuletzt veröffentlichten Hauptversionen gehören." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:104 -msgid "4. Inbegriffene Dienstleistungen" +#: ../../content/legal/terms/i18n/enterprise_de.rst:99 +msgid "3. Zugang zur Software" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:107 -msgid "4.1 Fehlerbehebung" +#: ../../content/legal/terms/i18n/enterprise_de.rst:101 +msgid "Der Kunde kann die auf der Cloud-Plattform gehostete Software nutzen oder die Option Self-Hosting wählen. Die Cloud-Plattform wird von Odoo SA gehostet und vollständig verwaltet, der Kunde kann per Fernzugriff darauf zugreifen. Bei der Self-Hosting-Option hostet der Kunde die Software stattdessen auf Computersystemen seiner Wahl, über die Odoo SA keine Kontrolle hat." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:109 -msgid "Während der Laufzeit dieser Vereinbarung ist Odoo SA verpflichtet, alle zumutbaren Anstrengungen zu unternehmen, um die Fehler zu beheben, die vom Kunden über den entsprechenden Kanal (üblicherweise die E-Mail-Adresse oder das Websiteformular des Odoo SA Servicedesks) eingereicht wurden, und mit der Bearbeitung dieser Einsendungen des Kunden innerhalb von 2 Werktagen zu beginnen." +#: ../../content/legal/terms/i18n/enterprise_de.rst:106 +msgid "Odoo SA gewährt dem Kunden für die Dauer dieser Vereinbarung eine nicht exklusive, nicht übertragbare Lizenz zur Nutzung (Ausführung, Änderung, Ausführung nach Änderung) der Odoo Enterprise Edition Software unter den in :ref:`appendix_a_de` genannten Bedingungen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:115 -msgid "Der Kunde versteht, dass Fehler, die durch eine Änderung oder Erweiterung verursacht wurden, die kein Teil der offiziellen Software sind, von dieser Dienstleistung nicht abgedeckt sind." +#: ../../content/legal/terms/i18n/enterprise_de.rst:110 +msgid "Der Kunde verpflichtet sich, alle erforderlichen Maßnahmen zu ergreifen, um die unveränderte Ausführung des Teils der Software zu gewährleisten, der die Gültigkeit der Nutzung der Odoo Enterprise Edition überprüft und zu diesem Zweck Statistiken sammelt, unter anderem zur Ausführung einer Instanz, der Anzahl der Benutzer, den installierten Apps und der Anzahl der Codezeilen der unterstützten Zusatzmodule." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:118 -msgid "Sobald der Fehler behoben wurde, wird dem Kunden eine geeignete Gegenmaßnahme mitgeteilt. Falls der Fehler in einer neueren Version der vom Kunden verwendeten Software behoben wurde, so ist der Kunde verpflichtet, seine Systeme auf diese Version zu aktualisieren, um die Korrektur zu erhalten. Der Kunde wird nicht aufgefordert, auf eine neuere abgedeckte Version der Software zu aktualisieren, um einen Fehler zu beheben." +#: ../../content/legal/terms/i18n/enterprise_de.rst:116 +msgid "Odoo SA verpflichtet sich, ohne Zustimmung des Kunden keine individuellen oder namentlichen Angaben an Dritte weiterzugeben und alle gesammelten Daten in Übereinstimmung mit der offiziellen Datenschutzpolitik zu behandeln, die unter https://www.odoo.com/privacy veröffentlicht ist." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:120 +msgid "Bei Ablauf oder Kündigung dieser Vereinbarung wird diese Lizenz unverzüglich widerrufen und der Kunde verpflichtet sich, die Nutzung der Odoo Enterprise Edition Software und der Cloud-Plattform einzustellen." msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:124 -msgid "Wenn ein Fehler in einer abgedeckten Version behoben wurde, ist Odoo SA verpflichtet, den Fehler auch in allen neueren abgedeckten Versionen der Software zu beheben." +msgid "Sollte der Kunde gegen die Bestimmungen dieses Abschnitts verstoßen, erklärt er sich bereit, Odoo SA eine zusätzliche Gebühr in Höhe von 300 % des geltenden Listenpreises für die tatsächliche Anzahl der Benutzer und installierten Apps zu zahlen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:127 -msgid "Beide Parteien erkennen an, dass Odoo SA gemäß der Softwarelizenz und dem Abschnitt :ref:`liability_de` dieser Vereinbarung für Fehler in der Software nicht haftbar gemacht werden kann." +#: ../../content/legal/terms/i18n/enterprise_de.rst:131 +msgid "4. Dienstleistungen" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:132 -msgid "4.2 Sicherheitsmitteilungen" +#: ../../content/legal/terms/i18n/enterprise_de.rst:136 +msgid "4.1 Fehlerbehebung" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:134 -msgid "Für die Dauer dieser Vereinbarung ist Odoo SA verpflichtet, dem Kunden für jedes Sicherheitsproblem, das in den abgedeckten Versionen der Software entdeckt wurde, eine Sicherheitsmitteilung zuzusenden. Diese Zusendung muss mindestens 2 Wochen vor Veröffentlichung der Sicherheitsmitteilung erfolgen, außer wenn der Fehler bereits von Dritten öffentlich gemacht wurde. Diese Sicherheitsberatung umfasst eine vollständige Beschreibung des Fehlers, seine Ursache, seine möglichen Auswirkungen auf die Kundensysteme sowie die entsprechenden Gegenmaßnahmen für jede abgedeckte Version." +#: ../../content/legal/terms/i18n/enterprise_de.rst:138 +msgid "Während der Laufzeit dieser Vereinbarung verpflichtet sich Odoo SA, alle zumutbaren Anstrengungen zu unternehmen, um Fehler der Software und der unterstützten Zusatzmodule zu beheben, die vom Kunden über den entsprechenden Kanal eingereicht werden (in der Regel das Webformular oder die Telefonnummern, die auf https://odoo.com/help aufgeführt sind, oder - im Falle der Zusammenarbeit mit einem Odoo-Partner - der vom Partner bereitgestellte Kanal), und mit der Bearbeitung innerhalb von zwei Werktagen nach Eingang zu beginnen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:142 -msgid "Der Kunde versteht, dass der Fehler und die Informationen in der Sicherheitsmitteilung während der Sperrfrist vor der öffentlichen Bekanntgabe als vertrauliche Informationen behandelt werden müssen, die im Abschnitt :ref:`confidentiality_de` beschrieben werden." +#: ../../content/legal/terms/i18n/enterprise_de.rst:145 +msgid "Sobald der Fehler behoben ist, wird dem Kunden eine entsprechende Problemlösung mitgeteilt. Wenn der Kunde eine unterstützte Version Version verwendet, wird er nicht zu einem Upgrade auf eine neuere unterstützte Version der Software aufgefordert, um einen Fehler zu beheben." msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:149 -msgid "4.3 Upgrade-Dienstleistungen" +msgid "Wenn ein Fehler in einer unterstützten Version behoben wird, verpflichtet sich Odoo SA, den Fehler ebenfalls in allen neueren unterstützten Versionen der Software zu beheben." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:154 +#: ../../content/legal/terms/i18n/enterprise_de.rst:152 +msgid "Beide Parteien erkennen an, dass Odoo SA, wie in der Lizenz der Software und im Abschnitt :ref:`liability_de` dieser Vereinbarung angegeben, nicht für Fehler in der Software oder in unterstützten Zusatzmodulen haftbar gemacht werden kann." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:157 +msgid "4.2 Service für Sicherheitsupdates" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:164 +msgid "Für die Dauer dieser Vereinbarung verpflichtet sich Odoo SA, dem Kunden für jeden Sicherheitsfehler, der in den unterstützten Versionen der Software (dies schließt Zusatzmodule aus) entdeckt wird, einen Sicherheitsbericht zuzusenden, mindestens zwei Wochen vor dessen Veröffentlichung, es sei denn, der Fehler wurde bereits von einer dritten Partei öffentlich bekannt gegeben. Sicherheitsberichte enthalten eine vollständige Beschreibung des Fehlers, seiner Ursache, seiner möglichen Auswirkungen auf die Systeme des Kunden und der entsprechenden Lösung für jede unterstützte Version." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:172 +msgid "Der Kunde nimmt zur Kenntnis, dass der Bug und die Informationen im Sicherheitsbericht während der Sperrfrist vor der öffentlichen Bekanntgabe als vertrauliche Informationen gemäß :ref:`confidentiality_de` zu behandeln sind." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:179 +msgid "Cloud-Plattform" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:181 +msgid "Odoo SA verpflichtet sich, die Sicherheitsmaßnahmen für jeden Sicherheitsfehler, der in einer auf der Cloud-Plattform gehosteten Version der Software entdeckt wird, auf alle von Odoo SA kontrollierten Systemen anzuwenden, sobald die entsprechenden Mittel verfügbar sind, ohne dass der Kunde manuell eingreifen muss." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:189 +msgid "4.3 Upgrade-Dienste" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:194 msgid "Upgrade-Service für die Software" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:156 -msgid "Während der Laufzeit dieser Vereinbarung kann der Kunde Upgrade-Anfragen über den entsprechenden Kanal übermitteln (üblicherweise die Website der Odoo SA für den Upgrade-Service), um eine Datenbank der Software einer abgedeckten Softwareversion auf eine neuere abgedeckte Version (die „Zielversion“) zu konvertieren." +#: ../../content/legal/terms/i18n/enterprise_de.rst:196 +msgid "Während der Laufzeit dieser Vereinbarung kann der Kunde über den entsprechenden Kanal (in der Regel die Upgrade-Service-Website von Odoo SA) Upgrade-Anträge stellen, um eine Datenbank der Software von einer beliebigen Version der Software auf eine neuere unterstützte Version (die \"Zielversion\") zu konvertieren." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:161 -msgid "Upgrade-Anfragen müssen eine vollständige Sicherungskopie der Kundendatenbank und die zugehörigen Daten enthalten (die in der Regel mit dem Backup-Menü der Software abgerufen werden können). Sollte es aus Gründen der Datensicherheit oder der Regulierung erforderlich sein, so umfasst der Upgrade-Service ein optionales Tool zur Anonymisierung identifizierbarer Daten einer Datenbank, bevor die Upgrade-Anfrage eingereicht wird, und ebenso ein Tool zum Wiederherstellen der anonymisierten Daten nach dem Upgrade." +#: ../../content/legal/terms/i18n/enterprise_de.rst:201 +msgid "Bei Nutzung der Cloud-Plattform werden Upgrade-Anträge direkt über das Bedienfeld der Cloud-Plattform eingereicht und erfordern keinen Daten-Upload. Im Falle von Self-Hosting müssen Upgrade-Anträge eine Kopie der Datenbank des Kunden und der zugehörigen Daten enthalten (in der Regel über das Backup-Menü der Software)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:168 -msgid "Dieser Service erfolgt über eine automatisierte Plattform, damit der Kunde unbeaufsichtigte Upgrades durchführen kann, sobald eine frühere Version der Kundendatenbank für eine abgedeckte Version erfolgreich aktualisiert worden ist. Der Kunde kann aufeinander folgende Upgrade-Anfragen für eine Datenbank einreichen. Er ist damit einverstanden, zuerst mindestens 1 (eine) Upgrade-Anfrage zu Testzwecken einzureichen, bevor er die abschließende Upgrade-Anfrage einreicht." +#: ../../content/legal/terms/i18n/enterprise_de.rst:206 +msgid "Dieser Service wird über eine automatisierte Plattform bereitgestellt, um dem Kunden die Ausführung unbeaufsichtigter Upgrades zu ermöglichen, sobald eine frühere Version der Datenbank des Kunden erfolgreich für eine unterstützte Version aktualisiert wurde." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:175 -msgid "Der Upgrade-Service ist beschränkt auf die technische Konvertierung und Anpassung der Kundendatenbank, um diese mit der Zielversion kompatibel zu machen, und auf die Korrektur von Fehlern, die unmittelbar durch den Upgrade-Vorgang verursacht werden und in der Zielversion normalerweise nicht auftreten würden." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:180 -msgid "Es liegt in der alleinigen Verantwortung des Kunden, die Datenbank nach dem Upgrade zu überprüfen und zu validieren, um Fehler zu erkennen, die Auswirkungen der in der Zielversion umgesetzten Änderungen und neuen Funktionen zu analysieren und diejenigen Erweiterungen der Software von Drittanbietern für die Zielversion zu konvertieren und anzupassen, die vor dem Upgrade in der Datenbank installiert waren (sofern nicht anders vorgesehen, siehe Abschnitt :ref:`upgrade_extra_de`). Der Kunde kann mehrere Upgrade-Anforderungen für eine Datenbank einreichen, bis ein akzeptables Ergebnis erzielt wird." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:191 -msgid "Upgrade-Service für Erweiterungen von Drittanbietern" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:193 -msgid "Für die Laufzeit dieser Vereinbarung kann der Kunde optionale Upgrade-Services optionale für von Drittanbieter angebotene Erweiterungsmodule der Software anfordern. Für diese optionale Dienstleistung fallen zusätzlichen Gebühren an (die unter „Gebühren“ beschrieben werden). Sie umfasst die technische Anpassung der Module von Drittanbietern, die in der Datenbank des Kunden installiert sind, und deren entsprechende Daten, damit sie mit der Zielversion kompatibel sind. Der Kunde wird eine Upgrade-Version aller installierten Module von Drittanbietern zusammen mit der aktualisierten Datenbank erhalten." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:204 -msgid "5. Abgaben und Gebühren" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:209 -msgid "5.1 Standardgebühren" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:211 -msgid "Die Standardgebühren für das Odoo Enterprise Abonnement, die Fehlerbehebung, die Sicherheitsmitteilungen und die Upgrades basieren auf der Anzahl der Benutzer, den installierten Apps, der vom Kunden verwendeten Softwareversion und werden bei Unterzeichnung der Vereinbarung schriftlich festgehalten." +#: ../../content/legal/terms/i18n/enterprise_de.rst:210 +msgid "Der Upgrade-Service beschränkt sich auf die technische Konvertierung und Anpassung der Datenbank des Kunden, um sie mit der Zielversion kompatibel zu machen, auf die Korrektur von Fehlern, die direkt durch den Upgrade-Vorgang verursacht werden und in der Zielversion normalerweise nicht auftreten, sowie auf die Konvertierung des Quellcodes und der Daten der abgedeckten Zusatzmodule für die Zielversion." msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:216 -msgid "Sollte der Kunde während der Laufzeit mehr Benutzer oder mehr installierte Apps als bei Unterzeichnung der vorliegenden Vereinbarung angegeben haben, so erklärt sich der Kunde bereit, für die restliche Laufzeit eine zusätzliche Gebühr in Höhe des (zu Beginn der Laufzeit) geltenden Listenpreises für die zusätzlichen Benutzer oder Apps zu entrichten." +msgid "Es liegt in der Verantwortung des Kunden, die aktualisierte Datenbank zu überprüfen, um Fehler zu erkennen, die Auswirkungen von Änderungen und neuen Funktionen, die in der Zielversion implementiert sind, zu analysieren und Erweiterungen von Drittanbietern der Software, die vor dem Upgrade in der Datenbank installiert waren (z. B. nicht unterstützte Zusatzmodule), zu konvertieren und für die Zielversion anzupassen. Der Kunde kann mehrere Upgrade-Anträge für eine Datenbank stellen, bis ein akzeptables Ergebnis erzielt wird." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:221 -msgid "Sollte der Kunde bei Unterzeichnung dieser Vereinbarung eine abgedeckte Version verwenden, bei der es sich nicht um die neueste Version handelt, so können die Standardgebühren für die erste Laufzeit im Ermessen der Odoo SA um 50 % erhöht werden, um die zusätzlichen Wartungskosten abzudecken." +#: ../../content/legal/terms/i18n/enterprise_de.rst:226 +msgid "4.4 Cloud-Hosting-Dienste" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:229 -msgid "5.2 Verlängerungsgebühren" +#: ../../content/legal/terms/i18n/enterprise_de.rst:228 +msgid "Wenn sich der Kunde für die Nutzung der Cloud-Plattform entscheidet, verpflichtet sich Odoo SA, während der Laufzeit dieser Vereinbarung mindestens folgendes anzubieten:" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:231 -msgid "Bei einer Verlängerung gemäß Abschnitt :ref:`term_de` erhöhen sich die Gebühren um bis zu 7 %, wenn die in der vorherigen Laufzeit erhobenen Gebühren niedriger als der dann gültige Listenpreis waren." +msgid "mehrere Hosting-Regionen (mindestens drei: Europa, Amerika, Asien/Pazifik)" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:232 +msgid "Hosting in Tier-III-Rechenzentren oder gleichwertigen Zentren mit einer Netzwerkverfügbarkeit von 99,9%" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:234 +msgid "erstklassige SSL (HTTPS) Verschlüsselung der Kommunikation" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:235 +msgid "vollautomatische, verifizierte Backups, repliziert in mehreren Regionen" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:236 +msgid "Notfallplan, regelmäßig getestet" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:238 -msgid "5.3 Gebühren für Upgrade-Services für Module von Drittanbietern" +msgid "Die Einzelheiten der Cloud-Hosting-Dienste sind in der Dienstgütevereinbarung unter https://www.odoo.com/cloud-sla beschrieben." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:240 -msgid "Die zusätzliche Gebühr für das Upgrade von Drittanbietern-Modulen beträgt 1000,00 € (eintausend Euro) pro 1000 Codezeilen in diesen Modulen, jeweils aufgerundet auf die nächsten Tausend Zeilen. Die Codezeilen umfassen alle Textzeilen im Quellcode dieser Module, unabhängig von Programmiersprache (Python, Javascript usw.) oder Datenformat (XML, TSV usw.). Ausgenommen sind Leer- und Kommentarzeilen." +#: ../../content/legal/terms/i18n/enterprise_de.rst:244 +msgid "4.5 Support-Dienste" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:246 -msgid "Odoo SA behält sich das Recht vor, eine Upgrade-Anfrage für Drittanbieter-Module unter den vorstehenden Bedingungen abzulehnen, wenn die Qualität des Quellcodes dieser Module zu schlecht sein oder diese Module eine Schnittstelle mit Drittanbieter-Software oder -Systemen darstellen sollten. Das Upgrade dieser Module erfolgt vorbehaltlich eines separaten Angebots außerhalb der vorliegenden Vereinbarung." +#: ../../content/legal/terms/i18n/enterprise_de.rst:247 +msgid "Umfang" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:255 -msgid "5.4 Steuern" +#: ../../content/legal/terms/i18n/enterprise_de.rst:249 +msgid "Während der Laufzeit dieser Vereinbarung kann der Kunde eine unbegrenzte Anzahl von kostenlosen Support-Tickets öffnen, die ausschließlich Fragen zu Fehlern (siehe :ref:`bugfix_de`) oder Anleitungen zur Nutzung der Standardfunktionen der Software und der unterstützten Zusatzmodule betreffen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:257 -msgid "Alle Gebühren und Abgaben verstehen sich ausschließlich aller geltenden Steuern, Gebühren oder Abgaben auf Bundes-, Provinz-, Bundesland- oder Kommunalebene oder anderer Behörden (zusammen als „Steuern“ bezeichnet). Der Kunde ist für die Zahlung sämtlicher Steuern im Zusammenhang mit seinen Käufen im Rahmen dieser Vereinbarung verantwortlich, außer wenn Odoo SA rechtlich verpflichtet sein sollte, Steuern zu zahlen oder einzuziehen, für welche der Kunde verantwortlich ist." +#: ../../content/legal/terms/i18n/enterprise_de.rst:254 +msgid "Andere Supportanfragen, wie z. B. Fragen zur Entwicklung oder zu Anpassungen, können durch den Erwerb einer separaten Servicevereinbarung abgedeckt werden. Falls nicht klar ist, ob eine Anfrage von diesem Vertrag abgedeckt ist, liegt die Entscheidung im Ermessen von Odoo SA." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:259 +msgid "Verfügbarkeit" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:261 +msgid "Tickets können über das Webformular oder die auf https://odoo.com/help aufgeführten Telefonnummern eingereicht werden, oder, wenn Sie mit einem Odoo-Partner zusammenarbeiten, über den von diesem bereitgestellten Kanal, abhängig von den örtlichen Öffnungszeiten." msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:268 -msgid "6. Dienstleistungsbedingungen" +msgid "4.6 Zusammenarbeit mit einem Odoo-Partner" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:271 -msgid "6.1 Pflichten des Kunden" +#: ../../content/legal/terms/i18n/enterprise_de.rst:270 +msgid "Für Fehlerbehebungen, Support- und Upgrade-Leistungen kann der Kunde entweder mit einem Odoo-Partner als Hauptansprechpartner oder direkt mit Odoo SA zusammenarbeiten." msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:273 -msgid "Der Kunde stimmt folgenden Klauseln zu:" +msgid "Entscheidet sich der Kunde für die Zusammenarbeit mit einem Odoo-Partner, beauftragt Odoo SA diesen mit Dienstleistungen im Zusammenhang mit den unterstützten Zusatzmodulen. Der Odoo-Partner kann sich im Namen des Kunden an Odoo SA wenden, um in Bezug auf die Standardfunktionen der Software Second Level Support zu erhalten." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:275 -msgid "er zahlt Odoo SA sämtliche Gebühren für die Dienstleistungen im Rahmen der vorliegenden Vereinbarung gemäß den Zahlungsbedingungen, die auf der entsprechenden Rechnung angegeben sind;" +#: ../../content/legal/terms/i18n/enterprise_de.rst:278 +msgid "Entscheidet sich der Kunde dafür, direkt mit Odoo SA zusammenzuarbeiten, werden Dienstleistungen im Zusammenhang mit unterstützten Zusatzmodulen *ausschließlich* dann erbracht, wenn der Kunde auf der Odoo Cloud-Plattform gehostet wird." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:277 -msgid "er wird Odoo SA unverzüglich informieren, sobald seine tatsächliche Benutzerzahl oder die Anzahl der installierten Apps die bei Unterzeichnung der Vereinbarung angegebenen Zahlen überschreiten sollten. In diesem Falle wird er die geltende zusätzliche Gebühr gemäß dem Abschnitt :ref:`charges_standard_de` entrichten;" +#: ../../content/legal/terms/i18n/enterprise_de.rst:285 +msgid "5. Kosten und Gebühren" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:281 -msgid "er wird alle notwendigen Maßnahmen zu ergreifen, um die unveränderte Ausführung des Teils der Software zu gewährleisten, mit dem die gültige Nutzung der Odoo Enterprise Edition überprüft, wie sie in :ref:`enterprise_access_de` beschrieben wird;" +#: ../../content/legal/terms/i18n/enterprise_de.rst:290 +msgid "5.1 Standardkosten" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:284 -msgid "er wird Odoo SA den notwendigen Zugang einräumen, um die Gültigkeit der Nutzung der Odoo Enterprise Edition auf Anfrage zu prüfen (z. B. wenn die automatische Validierung für den Kunden nicht funktioniert);" +#: ../../content/legal/terms/i18n/enterprise_de.rst:292 +msgid "Die Standardkosten für das Odoo Enterprise Abonnement und die Dienstleistungen basieren auf der Anzahl der Benutzer und der installierten Apps, die der Kunde nutzt, und werden bei Vertragsabschluss schriftlich festgehalten." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:287 -msgid "er wird 1 speziellen Ansprechpartner des Kunden für die gesamte Laufzeit der Vereinbarung ernennen;" +#: ../../content/legal/terms/i18n/enterprise_de.rst:296 +msgid "Wenn der Kunde während der Laufzeit eine höhere Anzahl an Benutzern oder installierten Apps nutzt, als zum Zeitpunkt des Vertragsabschlusses angegeben, stimmt der Kunde zu, hierfür für den Rest der Laufzeit eine zusätzliche Gebühr in Höhe des zu Beginn der Laufzeit geltenden Listenpreises zu zahlen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:289 -msgid "er wird alle angemessenen Maßnahmen ergreifen, um die Dateien und Datenbanken des Kunden zu schützen und sicherzustellen, dass die Kundendaten sicher sind, während er anerkennt, dass Odoo SA für Datenverluste nicht haftbar gemacht werden kann;" +#: ../../content/legal/terms/i18n/enterprise_de.rst:301 +msgid "Darüber hinaus werden die Kosten der Dienstleistungen im Zusammenhang mit unterstützten Zusatzmodulen basierend auf der Anzahl der Codezeilen in diesen Modulen berechnet. Entscheidet sich der Kunde für die Wartung von unterstützten Zusatzmodulen, beträgt die Gebühr monatlich 16,00 € pro 100 Codezeilen (aufgerundet auf die nächsten Hundert), sofern bei Vertragsabschluss nichts anderes schriftlich vereinbart wurde. Codezeilen werden mit dem cloc-Befehl der Software gezählt und umfassen alle Textzeilen im Quellcode dieser Module, unabhängig von der Programmiersprache (Python, Javascript, XML etc.), ausgenommen Leerzeilen, Kommentarzeilen und Dateien, die bei der Installation oder Ausführung der Software nicht geladen werden." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:297 -msgid "6.2 Verzicht auf Abwerbung oder Einstellung" +#: ../../content/legal/terms/i18n/enterprise_de.rst:310 +msgid "Wenn der Kunde ein Upgrade beantragt, kann Odoo SA für jedes unterstützte Zusatzmodul, das in den letzten 12 Monaten nicht durch eine Wartungsgebühr abgedeckt wurde, eine einmalige Zusatzgebühr von 16,00 € pro 100 Codezeilen für jeden fehlenden Abdeckungsmonat erheben." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:299 -msgid "Beide Parteien, ihre Tochtergesellschaften und Vertreter sind verpflichtet, während der Laufzeit dieser Vereinbarung und für einen Zeitraum von 12 Monaten ab dem Datum der Kündigung oder des Ablaufs dieser Vereinbarung keine Mitarbeiter der anderen Partei, die an der Erbringung oder Nutzung der Dienstleistungen im Rahmen dieser Vereinbarung beteiligt sind, abzuwerben oder eine Beschäftigung anzubieten, außer wenn diese andere Partei eine schriftliche Zustimmung dafür erteilt hat. Im Falle eines Verstoßes gegen die Bestimmungen dieses Abschnitts, der zu einer diesbezüglichen Kündigung dieses Arbeitnehmers führt, ist die dagegen verstoßende Partei verpflichtet, der anderen Partei einen Betrag in Höhe von 30.000,00 € (dreißigtausend Euro) zu zahlen." +#: ../../content/legal/terms/i18n/enterprise_de.rst:317 +msgid "5.2 Verlängerungsgebühren" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:313 -msgid "6.3 Werbung" +#: ../../content/legal/terms/i18n/enterprise_de.rst:319 +msgid "Bei einer Verlängerung gemäß Abschnitt :ref:`term_de` erhöhen sich die Gebühren um bis zu 7 %, wenn die während der vorherigen Laufzeit erhobenen Gebühren (mit Ausnahme etwaiger \"Erstnutzerrabatte\") unter dem jeweils gültigen Listenpreis liegen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:315 -msgid "Sofern keine anderslautende schriftliche Mitteilung erfolgte, gewährt jede Partei der anderen Partei eine nicht übertragbare, nicht ausschließliche, gebührenfreie, weltweite Lizenz zur Wiedergabe und Anzeige des Namens, der Logos und der Markenzeichen der jeweils anderen Partei. Diese Lizenz gilt ausschließlich für die Bezugnahme auf die andere Partei als Kunde oder Lieferant auf Websites, Pressemitteilungen und anderen Marketingmaterialien." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:325 -msgid "6.4 Vertraulichkeit" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:334 -msgid "Definition von „vertraulichen Informationen“:" +#: ../../content/legal/terms/i18n/enterprise_de.rst:326 +msgid "5.3 Steuern" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:328 -msgid "Alle von einer Partei (der „offenlegenden Partei“) gegenüber der anderen Partei (der „empfangenden Partei“) mündlich oder schriftlich mitgeteilten, offengelegten Informationen, die als vertraulich bezeichnet werden oder angesichts der Art der Informationen und den Umständen der Offenlegung vernünftigerweise als vertraulich verstanden werden sollten. Insbesondere sollten alle Informationen zu Unternehmen, Geschäften, Produkten, Entwicklungen, Geschäftsgeheimnissen, Fachwissen, Personal, Kunden und Lieferanten beider Parteien als vertraulich betrachtet werden." +msgid "Alle Gebühren und Entgelte verstehen sich zuzüglich aller anwendbaren Bundes-, Landes-, Staats-, Kommunal- oder sonstigen staatlichen Steuern, Gebühren oder Abgaben (zusammenfassend \"Steuern\"). Der Kunde ist für die Zahlung aller Steuern verantwortlich, die mit seinen im Rahmen dieser Vereinbarung getätigten Käufen verbunden sind, es sei denn, Odoo SA ist gesetzlich zur Zahlung oder Erhebung von Steuern verpflichtet, für die der Kunde verantwortlich ist." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:336 -msgid "Für alle während der Laufzeit dieser Vereinbarung empfangenen vertraulichen Informationen wird die empfangende Partei die gleiche Sorgfalt aufwenden, mit der sie die Vertraulichkeit ihrer eigenen, ähnlichen vertraulichen Informationen schützt, mindestens jedoch angemessene Sorgfalt." +#: ../../content/legal/terms/i18n/enterprise_de.rst:337 +msgid "6. Dienstleistungsbedingungen" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:341 -msgid "Die empfangende Partei kann vertrauliche Informationen der offenlegenden Partei offenlegen, soweit dies gesetzlich vorgeschrieben ist, sofern die empfangende Partei der offenlegenden Partei diese vorgeschriebene Offenlegung im gesetzlich zulässigen Umfang mitteilt." +#: ../../content/legal/terms/i18n/enterprise_de.rst:340 +msgid "6.1 Verpflichtungen des Kunden" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:348 -msgid "6.5 Kündigung" +#: ../../content/legal/terms/i18n/enterprise_de.rst:342 +msgid "Der Kunde verpflichtet sich:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:350 -msgid "Sollte eine der Parteien ihre Verpflichtungen aus dieser Vereinbarung nicht erfüllen und dieser Verstoß nicht innerhalb von 30 Kalendertagen nach schriftlicher Benachrichtigung über diesen Verstoß nicht behoben worden sein, so kann dieser Vertrag von der nicht säumigen Partei fristlos gekündigt werden." +#: ../../content/legal/terms/i18n/enterprise_de.rst:344 +msgid "Odoo SA alle anfallenden Gebühren für die Dienstleistungen dieser Vereinbarung gemäß den bei der Unterzeichnung dieses Vertrages festgelegten Zahlungsbedingungen zu zahlen;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:355 -msgid "Außerdem kann Odoo SA den Vertrag sofort kündigen, falls der Kunde die geltenden Gebühren für die Dienstleistungen nicht bis zum in der entsprechenden Rechnung angegebenen Fälligkeitsdatum bezahlt." +#: ../../content/legal/terms/i18n/enterprise_de.rst:346 +msgid "Odoo SA unverzüglich zu benachrichtigen, wenn die tatsächliche Anzahl der Benutzer oder der installierten Apps die bei Vertragsabschluss angegebene Anzahl übersteigt, und in diesem Fall die entsprechende Zusatzgebühr zu entrichten, wie in Abschnitt :ref:`charges_standard_de` beschrieben;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:349 +msgid "alle erforderlichen Maßnahmen zu ergreifen, um die unveränderte Ausführung des Teils der Software zu gewährleisten, der die Gültigkeit der Nutzung der Odoo Enterprise Edition prüft, wie in :ref:`enterprise_access_de` beschrieben;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:352 +msgid "einen festen Ansprechpartner für die gesamte Laufzeit des Vereinbarung zu benennen;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:353 +msgid "Odoo SA den Wechsel seines Hauptansprechpartners zu einem anderen Odoo-Partner oder zu einer direkten Zusammenarbeit mit Odoo SA 30 Tage vorher schriftlich mitzuteilen." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:356 +msgid "Wenn sich der Kunde für die Nutzung der Cloud-Plattform entscheidet, erklärt er sich außerdem damit einverstanden:" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:359 -msgid "Überdauernde Bestimmungen: Die Abschnitte \":ref:`confidentiality_de`”, “:ref:`disclaimers_de`”, “:ref:`liability_de`” sowie “:ref:`general_provisions_de`” werden jede Kündigung oder Ablauf dieser Vereinbarung überdauern." +msgid "alle angemessenen Maßnahmen zu ergreifen, um die Sicherheit seiner Benutzerkonten zu gewährleisten, einschließlich der Wahl eines sicheren Passworts und der Nichtweitergabe dieses Passworts an andere Personen;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:367 -msgid "7. Garantien, Haftungsausschlüsse, Haftung" +#: ../../content/legal/terms/i18n/enterprise_de.rst:363 +msgid "die Hosting-Dienste in angemessener Weise und unter Ausschluss jeglicher illegaler oder missbräuchlicher Aktivitäten zu nutzen und sich strikt an die Regeln zu halten, die in der unter https://www.odoo.com/acceptable-use veröffentlichten Acceptable Use Policy (Nutzungsrichtlinien) aufgeführt sind." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:368 +msgid "Sollte der Kunde die Self-Hosting-Option gewählt haben, erklärt er sich des weiteren dazu bereit:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:370 +msgid "alle angemessenen Maßnahmen zu ergreifen, um seine Dateien und Datenbanken zu schützen, wobei Odoo SA nicht für Datenverluste haftbar gemacht werden kann;" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:372 -#: ../../content/legal/terms/i18n/enterprise_fr.rst:521 -msgid "7.1 Garantie" +msgid "Odoo SA den notwendigen Zugang zu gewähren, um die Gültigkeit der Nutzung der Odoo Enterprise Edition auf Anfrage überprüfen zu können (z.B. wenn die automatische Validierung für den Kunden nicht funktioniert)" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:374 -msgid "Für die Laufzeit dieser Vereinbarung ist Odoo SA verpflichtet, wirtschaftlich angemessene Anstrengungen zu unternehmen, um die Dienstleistungen gemäß den allgemein branchenweit anerkannten Standards auszuführen, sofern folgende Bedingungen erfüllt sind:" +#: ../../content/legal/terms/i18n/enterprise_de.rst:379 +msgid "6.2 Verzicht auf Abwerbung oder Einstellung" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:378 -msgid "die Computersysteme des Kunden befinden sich in einem guten Betriebszustand und die Software ist in einer geeigneten Betriebsumgebung installiert;" +#: ../../content/legal/terms/i18n/enterprise_de.rst:381 +msgid "Falls schriftlich nicht anders vereinbart, verpflichten sich die Parteien, ihre verbundenen Unternehmen und Vertreter, für die Dauer der Vereinbarung und für einen Zeitraum von 12 Monaten ab dem Datum der Beendigung oder des Ablaufs dieser Vereinbarung keinen Mitarbeiter der anderen Partei, der an der Erbringung oder Nutzung der Dienstleistungen im Rahmen dieser Vereinbarung beteiligt ist, abzuwerben oder ihm eine Beschäftigung anzubieten. Im Falle eines Verstoßes gegen die Bedingungen dieses Abschnitts, der zum Austritt des Mitarbeiters führt, verpflichtet sich die verletzende Partei, der anderen Partei einen Betrag von 30.000,00 € (dreißigtausend Euro) zu zahlen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:380 -msgid "der Kunde stellt angemessene Informationen und Zugänge für die Fehlerbehebung bereit, damit Odoo SA Probleme identifizieren, reproduzieren und beheben kann;" +#: ../../content/legal/terms/i18n/enterprise_de.rst:392 +msgid "6.3 Werbung" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:382 -msgid "alle Odoo SA zustehenden Beträge wurden bezahlt." +#: ../../content/legal/terms/i18n/enterprise_de.rst:394 +msgid "Sofern nicht anders schriftlich mitgeteilt, gewährt jede Partei der anderen eine nicht übertragbare, nicht exklusive, gebührenfreie, weltweite Lizenz, den Namen, die Logos und die Marken der anderen Partei zu reproduzieren und darzustellen, und zwar ausschließlich zu dem Zweck, auf die andere Partei als Kunden oder Lieferanten zu verweisen, und zwar auf Websites, in Pressemitteilungen und anderen Marketingmaterialien." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:384 -msgid "Das einzige und ausschließliche Rechtsmittel des Kunden und die einzige Verpflichtung von Odoo SA bei Verstößen gegen diese Garantie besteht darin, dass Odoo SA die Ausführung der Dienste ohne zusätzliche Kosten wiederaufnimmt." +#: ../../content/legal/terms/i18n/enterprise_de.rst:403 +msgid "6.4 Vertraulichkeit" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:391 -msgid "7.2 Haftungsausschlüsse" +#: ../../content/legal/terms/i18n/enterprise_de.rst:411 +msgid "Definition \"Vertrauliche Informationen\":" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:393 -msgid "Außer wenn in diesem Dokument ausdrücklich angegeben, räumt keine der beiden Parteien weder ausdrückliche noch stillschweigende, gesetzliche oder anderweitige Gewährleistungen irgendeiner Art ein, und beide Parteien lehnen alle implizierten Garantien ausdrücklich ab, einschließlich jeglicher stillschweigenden Zusicherung der Marktgängigkeit, der Eignung für einen bestimmten Zweck oder der Nichtverletzung, soweit diese Einschränkung nach geltendem Recht zulässig ist." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:399 -msgid "Odoo SA garantiert nicht, dass die Software örtlichen oder internationalen Gesetzen oder Rechtsvorschriften entspricht." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:405 -msgid "7.3 Haftungsbeschränkung" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_de.rst:407 -msgid "Im gesetzlich maximal zulässigen Umfang darf die Gesamthaftung jeder Partei zusammen mit ihren Tochtergesellschaften aus oder im Zusammenhang mit dieser Vereinbarung 50 % des vom Kunden im Rahmen dieser Vereinbarung in den 12 Monaten unmittelbar vor dem Datum des Ereignisses, das zu diesem Anspruch führt, gezahlten Gesamtbetrags nicht übersteigen. Auch bei mehreren Ansprüchen darf diese Beschränkung nicht verändert werden." +#: ../../content/legal/terms/i18n/enterprise_de.rst:406 +msgid "Alle von einer Partei (der \"offenlegenden Partei\") der anderen Partei (der \"empfangenden Partei\") mündlich oder schriftlich offengelegten Informationen, die als vertraulich bezeichnet werden oder die angesichts Ihrer Beschaffenheit und der Umstände der Offenlegung als vertraulich zu verstehen sind. Als vertraulich sind insbesondere alle Informationen zu betrachten, die sich auf die Geschäfte, Angelegenheiten, Produkte, Entwicklungen, Geschäftsgeheimnisse, das Know-how, die Mitarbeiter, Kunden und Lieferanten einer der Parteien beziehen." msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:413 -msgid "Keine der beiden Parteien oder ihre Tochtergesellschaften werden unter keinen Umständen für indirekte, besondere, exemplarische, zufällige oder Folgeschäden jeglicher Art haften, einschließlich unter anderem Verluste von Erträgen, Gewinnen, Einsparungen, verlorene Geschäftsgelegenheiten oder andere finanzielle Verluste, Kosten für Stillstand oder Verspätung, verlorene oder beschädigte Daten, die aus oder im Zusammenhang mit dieser Vereinbarung entstehen. Dies gilt unabhängig von der Art der Handlung, egal ob vertraglicher Art, unerlaubte Handlung (einschließlich grober Fahrlässigkeit) oder einer anderen rechtlichen oder billigen Theorie, selbst wenn eine Partei oder ihre Tochtergesellschaften auf die Möglichkeit solcher Schäden hingewiesen wurden oder die von einer Partei oder ihren Tochtergesellschaften ergriffenen Abhilfemaßnahmen ihren wesentlichen Zweck verfehlen." +msgid "Für alle vertraulichen Informationen, die die empfangende Partei während der Laufzeit dieser Vereinbarung erhält, wendet sie die gleiche Sorgfalt an wie für den Schutz der Vertraulichkeit ihrer eigenen ähnlich vertraulichen Informationen, sofern es sich um ein Mindestmaß an Sorgfalt handelt." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:417 +msgid "Die empfangende Partei darf vertrauliche Informationen der offenlegenden Partei veröffentlichen, soweit sie gesetzlich dazu gezwungen ist, vorausgesetzt, die empfangende Partei unterrichtet die offenlegende Partei vorher über die erzwungene Offenlegung, soweit dies gesetzlich zulässig ist." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:424 +msgid "6.5 Datenschutz" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:430 +msgid "Definitionen" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:427 -msgid "7.4 Höhere Gewalt" +msgid "\"Personenbezogene Daten\", \"Verantwortliche\" und \"Auftragsverarbeiter\" haben dieselbe Bedeutung wie in der Verordnung (EU) 2016/679 und der Richtlinie 2002/58/EG sowie in allen Verordnungen oder Rechtsvorschriften, die diese ändern oder ersetzen (im Folgenden als \"Datenschutzgesetzgebung\" bezeichnet)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:429 -msgid "Keine der beiden Parteien haftet gegenüber der anderen Partei für die Verzögerung oder die Nichterbringung einer Leistung im Rahmen dieser Vereinbarung, wenn diese Nichterbringung oder Verzögerung durch folgende Punkte verursacht wurden: staatliche Rechtsvorschriften, Brand, Streik, Krieg, Überschwemmung, Unfall, Epidemie, Embargo, vollständige oder teilweise Enteignung von Anlagen oder Produkten seitens einer Regierung oder einer öffentlichen Behörde oder aus allen anderen Gründen oder Ursachen gleicher oder unterschiedlicher Art, die außerhalb des angemessenen Einflussbereichs dieser Partei liegen. Dies gilt, solange diese Gründe oder Ursachen vorliegen." +#: ../../content/legal/terms/i18n/enterprise_de.rst:433 +msgid "Verarbeitung von personenbezogenen Daten" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:441 -msgid "8. Allgemeine Bestimmungen" +#: ../../content/legal/terms/i18n/enterprise_de.rst:435 +msgid "Die Parteien erkennen an, dass die Datenbank des Kunden personenbezogene Daten enthalten kann, für die der Kunde verantwortlich ist. Diese Daten werden von Odoo SA verarbeitet, wenn der Kunde dies anweist, indem er eine der Dienstleistungen nutzt, für die eine Datenbank erforderlich ist (z. B. Cloud-Hosting-Dienste oder Datenbank-Upgrade-Service), oder wenn der Kunde seine Datenbank oder einen Teil seiner Datenbank aus irgendeinem Grund im Zusammenhang mit dieser Vereinbarung an Odoo SA überträgt." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:446 -msgid "8.1 Geltendes Recht" +#: ../../content/legal/terms/i18n/enterprise_de.rst:442 +msgid "Diese Verarbeitung erfolgt in Übereinstimmung mit der Datenschutzgesetzgebung. Insbesondere verpflichtet sich Odoo SA dazu:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:448 -msgid "Beide Parteien stimmen zu, dass im Falle von Streitigkeiten aus oder im Zusammenhang mit dieser Vereinbarung das belgische Recht angewendet wird, ohne Rücksicht auf Wahl- oder Kollisionsrecht. Soweit im Rahmen dieser Bestimmung eine Klage oder ein Gerichtsverfahren zulässig ist, stimmen beide Parteien bei, die Gerichte in Nivelles (Belgien) für die Beilegung aller Streitigkeiten als ausschließlich zuständig anzuerkennen." +#: ../../content/legal/terms/i18n/enterprise_de.rst:445 +msgid "(a) die personenbezogenen Daten nur zu verarbeiten, wenn und wie sie vom Kunden angewiesen werden, und zwar zum Zweck der Erbringung einer der Dienstleistungen im Rahmen dieser Vereinbarung, es sei denn, dies ist gesetzlich vorgeschrieben; in diesem Fall wird Odoo SA den Kunden vorher informieren, es sei denn, das Gesetz verbietet dies;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:457 -msgid "8.2 Salvatorische Klausel" +#: ../../content/legal/terms/i18n/enterprise_de.rst:449 +msgid "(b) sicherzustellen, dass alle Personen innerhalb von Odoo SA, die zur Verarbeitung der personenbezogenen Daten befugt sind, sich zur Vertraulichkeit verpflichtet haben;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:451 +msgid "(c) angemessene technische und organisatorische Maßnahmen zu ergreifen und einzuhalten, um die personenbezogenen Daten vor unbefugter oder unrechtmäßiger Verarbeitung und vor versehentlichem Verlust, Zerstörung, Beschädigung, Diebstahl, Änderung oder Offenlegung zu schützen;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:454 +msgid "d) alle Datenschutzanfragen, die an Odoo SA in Bezug auf die Datenbank des Kunden gestellt werden, unverzüglich an den Kunden weiterzuleiten;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:456 +msgid "(e) den Kunden unverzüglich zu benachrichtigen, sobald Odoo SA von einer versehentlichen, unbefugten oder rechtswidrigen Verarbeitung, Offenlegung oder einem Zugriff auf die personenbezogenen Daten erfährt und dies bestätigt;" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:459 -msgid "Sollten eine oder mehrere Bestimmungen dieser Vereinbarung oder deren Anwendung unwirksam, rechtswidrig oder nicht durchsetzbar sein, so werden die Wirksamkeit, Rechtmäßigkeit und Durchsetzbarkeit der übrigen Bestimmungen dieser Vereinbarung und ihrer Anwendung davon nicht berührt oder beeinträchtigt. Beide Parteien verpflichten sich, alle unwirksamen, rechtswidrigen oder nicht durchsetzbaren Bestimmungen dieser Vereinbarung durch eine wirksame Bestimmung möglichst mit gleichen Wirkungen und Zielen zu ersetzen." +msgid "(f) den Kunden zu benachrichtigen, wenn die Verarbeitungsanweisungen nach Ansicht von Odoo SA gegen die geltende Datenschutzgesetzgebung verstoßen;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:461 +msgid "(g) dem Kunden alle Informationen zur Verfügung zu stellen, die erforderlich sind, um die Einhaltung der Datenschutzgesetzgebung nachzuweisen, und Prüfungen, einschließlich Inspektionen, die vom Kunden durchgeführt oder in Auftrag gegeben werden, zuzulassen und in angemessener Weise dazu beizutragen;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:465 +msgid "(h) je nach Wahl des Kunden, alle Kopien der Datenbank des Kunden, die sich im Besitz von Odoo SA befinden, bei Beendigung dieser Vereinbarung entweder dauerhaft zu löschen oder zurückzugeben, unter Einhaltung der in der `Datenschutzrichtlinie `_ von Odoo SA genannten Fristen" msgstr "" #: ../../content/legal/terms/i18n/enterprise_de.rst:470 +msgid "In Bezug auf die Punkte (d) bis (f) verpflichtet sich der Kunde, Odoo SA jederzeit genaue Kontaktinformationen zur Verfügung zu stellen, die für die Benachrichtigung des Datenschutzbeauftragten des Kunden erforderlich sind." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:475 +msgid "Unterauftragsverarbeiter" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:477 +msgid "Der Kunde nimmt zur Kenntnis und erklärt sich damit einverstanden, dass Odoo SA zur Erbringung der Dienstleistungen Dritte (Unterauftragsverarbeiter) mit der Verarbeitung personenbezogener Daten beauftragt. Odoo SA verpflichtet sich, Unterauftragsverarbeiter nur in Übereinstimmung mit der Datenschutzgesetzgebung einzusetzen. Diese Nutzung wird durch einen Vertrag zwischen Odoo SA und dem Unterauftragsverarbeiter abgedeckt, der entsprechende Garantien enthält. Die Datenschutzrichtlinie von Odoo SA, die unter https://www.odoo.com/privacy veröffentlicht ist, enthält aktuelle Informationen zu den Namen und Zwecken der Unterauftragsverarbeiter, die Odoo SA derzeit für die Erbringung der Dienstleistungen einsetzt." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:489 +msgid "6.6 Beendigung" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:491 +msgid "Für den Fall, dass eine der Parteien eine ihrer Verpflichtungen aus diesem Vertrag nicht erfüllt und diese Verletzung nicht innerhalb von 30 Kalendertagen nach der schriftlichen Benachrichtigung über diese Verletzung behoben wird, kann diese Vereinbarung umgehend von der nicht verletzenden Partei gekündigt werden." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:496 +msgid "Ferner kann Odoo SA den Vertrag mit sofortiger Wirkung kündigen, sollte der Kunde die für die Dienstleistungen anfallenden Gebühren innerhalb von 21 Tagen nach dem auf der entsprechenden Rechnung angegebenen Fälligkeitsdatum und nach mindestens drei Mahnungen nicht bezahlt haben." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:502 +msgid "Fortgeltende Bestimmungen:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:501 +msgid "Die Abschnitte :ref:`confidentiality_de`, :ref:`disclaimers_de`, :ref:`liability_de` und :ref:`general_provisions_de` gelten auch nach Beendigung oder Ablauf dieser Vereinbarung." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:507 +msgid "7. Garantien, Haftungsausschlüsse, Haftung" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:512 +msgid "7.1 Garantien" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:514 +msgid "Odoo SA besitzt das Urheberrecht oder ein gleichwertiges Recht [#cla_de1]_ an 100 % des Codes der Software und bestätigt, dass alle Softwarebibliotheken, die für die Nutzung der Software erforderlich sind, unter einer mit der Softwarelizenz kompatiblen Lizenz verfügbar sind." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:518 +msgid "Odoo SA verpflichtet sich für die Dauer dieser Vereinbarung, Dienstleistungen nach wirtschaftlich vertretbarem Aufwand in Übereinstimmung mit den allgemein anerkannten Branchenstandards auszuführen, vorausgesetzt, dass:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:523 +msgid "die Computersysteme des Kunden sich in einem guten Betriebszustand befinden und die Software bei Self-Hosting in einer geeigneten Betriebsumgebung installiert ist;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:525 +msgid "der Kunde angemessene Informationen zur Fehlerbehebung zur Verfügung stellt und Odoo SA im Falle von Self-Hosting jeden nötigen Zugang gewährt, um Probleme zu identifizieren, zu reproduzieren und zu beheben;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:528 +msgid "alle an Odoo SA geschuldeten Beträge bezahlt wurden." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:530 +msgid "Das einzige und ausschließliche Rechtsmittel des Kunden und die einzige Verpflichtung von Odoo SA bei einem Verstoß gegen diese Garantie besteht darin, dass Odoo SA die Ausführung der Dienstleistungen ohne zusätzliche Kosten wieder aufnimmt." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:534 +msgid "Externe Beiträge sind durch einen `Copyright-Lizenzvertrag `_ abgedeckt, der Odoo SA eine dauerhafte, kostenlose und unwiderrufliche Copyright- und Patentlizenz gewährt." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:541 +msgid "7.2 Haftungsausschlüsse" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:543 +msgid "Sofern nicht ausdrücklich in diesem Dokument vorgesehen, übernimmt keine der Parteien irgendeine Garantie, sei es ausdrücklich, stillschweigend, gesetzlich oder anderweitig, und jede Partei lehnt ausdrücklich alle stillschweigenden Garantien ab, einschließlich jeglicher stillschweigenden Garantie der Marktgängigkeit, Eignung für einen bestimmten Zweck oder Nichtverletzung von Rechten Dritter, soweit dies nach geltendem Recht zulässig ist." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:549 +msgid "Odoo SA übernimmt keine Garantie dafür, dass die Software mit lokalen oder internationalen Gesetzen oder Vorschriften konform ist." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:555 +msgid "7.3 Haftungsbeschränkung" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:557 +msgid "Soweit gesetzlich zulässig, übersteigt die Gesamthaftung jeder Partei zusammen mit ihren verbundenen Unternehmen, die sich aus dieser Vereinbarung ergibt oder mit ihr in Zusammenhang steht, nicht 50 % des Gesamtbetrags, den der Kunde im Rahmen dieser Vereinbarung in den 12 Monaten unmittelbar vor dem Datum des Ereignisses, das einen solchen Anspruch begründet, gezahlt hat. Mehrfachansprüche führen nicht zu einer Ausweitung dieser Begrenzung." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:563 +msgid "In keinem Fall haften die Parteien oder ihre verbundenen Unternehmen für indirekte, besondere, exemplarische, zufällige oder Folgeschäden jeglicher Art, einschließlich, aber nicht beschränkt auf Einnahmeverluste, Gewinne, Einsparungen, Geschäftsverluste oder andere finanzielle Verluste, Kosten für Stockungen oder Verzögerung, verlorene oder beschädigte Daten, die sich aus oder in Verbindung mit dieser Vereinbarung ergeben, unabhängig von der Form der Klage, ob auf vertraglicher Basis, aufgrund unerlaubter Handlung (einschließlich strikter Fahrlässigkeit) oder einer anderen rechtlichen oder gerechtfertigten Grundlage, selbst wenn eine Partei oder ihre Partner auf die Möglichkeit solcher Schäden hingewiesen wurden oder wenn das Rechtsmittel einer Partei oder ihrer Partner auf andere Weise seinen wesentlichen Zweck verfehlt." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:576 +msgid "7.4 Höhere Gewalt" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:578 +msgid "Keine der Parteien haftet gegenüber der anderen Partei für die Verzögerung oder das Nichterbringen einer Leistung aus dieser Vereinbarung, wenn die Ursache für die Verzögerung oder das Nichterbringen auf höhere Gewalt zurückzuführen ist, wie z. B. behördliche Vorschriften, Feuer, Streik, Krieg, Überschwemmung, Unfall, Epidemie, Embargo, vollständige oder teilweise Aneignung von Anlagen oder Produkten durch eine Regierung oder Behörde oder andere Ursachen gleicher oder anderer Art, die außerhalb der zumutbaren Kontrolle der betreffenden Partei liegen, solange diese Ursachen bestehen." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:588 +msgid "8. Allgemeine Bestimmungen" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:593 +msgid "8.1 Geltendes Recht" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:595 +msgid "Diese Vereinbarung und alle Kundenaufträge unterliegen dem belgischen Recht. Alle Streitigkeiten, die sich aus oder im Zusammenhang mit dieser Vereinbarung oder einem Kundenauftrag ergeben, unterliegen der ausschließlichen Zuständigkeit des Handelsgerichts von Nivelles." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:602 +msgid "8.2 Salvatorische Klausel" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:604 +msgid "Sollten eine oder mehrere Bestimmungen dieser Vereinbarung oder ihrer Anwendung ungültig, rechtswidrig oder nicht durchsetzbar sein, so wird die Gültigkeit, Rechtmäßigkeit und Durchsetzbarkeit der übrigen Bestimmungen dieser Vereinbarung und ihrer Anwendung dadurch in keiner Weise berührt oder beeinträchtigt. Beide Parteien verpflichten sich, jede ungültige, rechtswidrige oder nicht durchsetzbare Bestimmung dieser Vereinbarung durch eine gültige Bestimmung zu ersetzen, die die gleichen Auswirkungen und Ziele hat." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_de.rst:615 msgid "9. Anhang A: Odoo Enterprise Edition-Lizenz" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:474 +#: ../../content/legal/terms/i18n/enterprise_de.rst:619 msgid "Die Odoo Enterprise Edition ist unter nachstehend definierten der Odoo Enterprise Edition Lizenz v1.0 lizenziert:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_de.rst:483 +#: ../../content/legal/terms/i18n/enterprise_de.rst:628 msgid "Siehe :ref:`odoo_enterprise_license`." msgstr "" @@ -1379,583 +1483,587 @@ msgstr "" msgid "Acuerdo de suscripción de Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:9 +#: ../../content/legal/terms/i18n/enterprise_es.rst:10 +msgid "`Download PDF `_" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_es.rst:12 msgid "Esta es una traducción al español del \"Odoo Enterprise Subscription Agreement\". Esta traducción se proporciona con la esperanza de que facilite la comprensión, pero no tiene valor legal. La única referencia oficial de los términos y condiciones del \"Odoo Enterprise Subscription Agreement\" es :ref:`la versión original en inglés `" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:18 +#: ../../content/legal/terms/i18n/enterprise_es.rst:21 msgid "Al suscribirse a los servicios de Odoo Enterprise (en adelante “los Servicios”) proporcionados por Odoo SA y sus filiales (en adelante denominadas conjuntamente “Odoo SA”), relacionados con las versiones Odoo Enterprise o Odoo community (en adelante “el Software”) y alojados en los servidores de la nube de Odoo SA (en adelante “Servicio en la Nube”) o en servidores locales (en adelante “Auto-hospedaje”), usted (en adelante “el Cliente”) acepta los términos y condiciones establecidos a continuación (en adelante “el Acuerdo”)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:28 +#: ../../content/legal/terms/i18n/enterprise_es.rst:31 msgid "1 Término del Acuerdo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:30 +#: ../../content/legal/terms/i18n/enterprise_es.rst:33 msgid "La duración de la suscripción (en adelante el “Plazo”) será indicada por escrito en este Acuerdo, y comenzará a partir de la fecha de firma del Acuerdo. La suscripción se considerará renovada automáticamente por un período igual al Plazo estipulado originalmente, salvo que alguna de las partes del Acuerdo proporcione un aviso por escrito expresando su deseo de culminar los Servicios al menos 30 días antes de la fecha de culminación del Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:39 +#: ../../content/legal/terms/i18n/enterprise_es.rst:42 msgid "2 Definiciones" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:45 +#: ../../content/legal/terms/i18n/enterprise_es.rst:48 msgid "Usuario" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:42 +#: ../../content/legal/terms/i18n/enterprise_es.rst:45 msgid "El término usuario hace referencia a cualquier cuenta de usuario identificada como activa en el Software, con potestates de creación y/o edición. No se consideran como Usuarios a las cuentas desactivadas y aquellas cuentas utilizadas por personas (o sistemas) que solo tienen acceso limitado al Software a través del portal del usuario." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:50 +#: ../../content/legal/terms/i18n/enterprise_es.rst:53 msgid "Aplicación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:48 +#: ../../content/legal/terms/i18n/enterprise_es.rst:51 msgid "Una ‘aplicación’ es un grupo especializado de funciones disponibles para ser instaladas en el Software, las cuales están enunciadas en la sección de Precios del `sitio web de Odoo SA `__" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:56 +#: ../../content/legal/terms/i18n/enterprise_es.rst:59 msgid "Partner de Odoo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:53 +#: ../../content/legal/terms/i18n/enterprise_es.rst:56 msgid "Un ‘Partner’ de Odoo es una empresa o individuo externo a Odoo SA que ofrece servicios relacionados con el Software, y quien ha sido seleccionado por el Cliente para trabajar directamente con él. En cualquier momento, el cliente puede decidir trabajar con un Partner diferente o con Odoo SA directamente (sujeto a previo aviso)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:63 +#: ../../content/legal/terms/i18n/enterprise_es.rst:66 msgid "Módulo adicional" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:59 +#: ../../content/legal/terms/i18n/enterprise_es.rst:62 msgid "Un módulo adicional es un directorio de archivos de código fuente, o un conjunto de personalizaciones basadas en lenguaje de programación Python, creadas en una base de datos (por ejemplo, con Odoo Studio), que agrega características o cambia el comportamiento estándar de Software. Pueden haber sido desarrolladas por el Cliente, por Odoo SA, por un Partner de Odoo en nombre del Cliente o por terceros." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:68 +#: ../../content/legal/terms/i18n/enterprise_es.rst:71 msgid "Módulo adicional de mantenimiento" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:66 +#: ../../content/legal/terms/i18n/enterprise_es.rst:69 msgid "Un módulo adicional de mantenimiento es un módulo adicional por el cual el Cliente ha elegido pagar un costo de mantenimiento con el fin de obtener servicios de soporte, actualizaciones y corrección de errores." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:77 +#: ../../content/legal/terms/i18n/enterprise_es.rst:80 msgid "Error/Bug" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:71 +#: ../../content/legal/terms/i18n/enterprise_es.rst:74 msgid "Se considera como ‘bug’ a cualquier falla del Software o de un módulo adicional de mantenimiento que resulte en una disrupción completa, una cadena de errores o un fallo de seguridad, y que no es causado directamente por una instalación o configuración defectuosa. El incumplimiento de algunas especificaciones o requisitos será considerado como un Bug a la discreción de Odoo SA (por ejemplo, cuando el Software no cumple con el comportamiento ni los resultados para el cual fue diseñado, o cuando una característica específica del país deja de cumplir los requisitos legales de contabilidad)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:82 +#: ../../content/legal/terms/i18n/enterprise_es.rst:85 msgid "Versiones Cubiertas" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:80 +#: ../../content/legal/terms/i18n/enterprise_es.rst:83 msgid "A menos que se especifique lo contrario, los Servicios proporcionados por en virtud de este Acuerdo son únicamente aplicables a las versiones cubiertas del Software, las cuales incluyen las últimas tres (3) versiones publicadas." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:87 +#: ../../content/legal/terms/i18n/enterprise_es.rst:90 msgid "3 Acceso al Software" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:89 +#: ../../content/legal/terms/i18n/enterprise_es.rst:92 msgid "El Cliente puede hacer uso del Software alojado en la nube o instalar el Software en un servidor propio. La plataforma en la nube es ofrecida y administrada en su totalidad por Odoo SA, y el Cliente puede acceder a ella de forma remota. Si el cliente elige la opción de instalar el Software en un servidor propio o un sistema informático de su elección, Odoo SA no tendrá control sobre el Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:95 +#: ../../content/legal/terms/i18n/enterprise_es.rst:98 msgid "Durante la vigencia de este Acuerdo, Odoo SA le otorga al Cliente una licencia no exclusiva e intransferible para usar (ejecutar, modificar, ejecutar después de las modificaciones) el Software, bajo los términos establecidos en el Anexo A: Licencia de la versión Enterprise de Odoo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:99 +#: ../../content/legal/terms/i18n/enterprise_es.rst:102 msgid "El Cliente acepta tomar todas las medidas necesarias para garantizar que no se modificará la parte del Software que ejecuta y verifica el uso y la recolección de estadísticas válidas, incluyendo pero sin limitarse a la ejecución de una instancia, el número de usuarios, las aplicaciones instaladas y el número de líneas de códigos incluidas en los módulos adicionales de mantenimiento." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:104 +#: ../../content/legal/terms/i18n/enterprise_es.rst:107 msgid "Odoo SA se compromete a no divulgar cifras individuales o mencionadas a terceros sin el consentimiento del Cliente, y a tratar todos los datos recopilados de conformidad con la Política de Privacidad oficial publicada en `Odoo Privacy `__" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:108 +#: ../../content/legal/terms/i18n/enterprise_es.rst:111 msgid "Después de la expiración o terminación de este Acuerdo, la licencia concedida al Cliente será revocada inmediatamente y el Cliente acepta dejar de usar el Software, especialmente la versión Odoo Enterprise, y la plataforma en la nube." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:112 +#: ../../content/legal/terms/i18n/enterprise_es.rst:115 msgid "En caso de que exista algún incumplimiento por parte del Cliente a los términos de esta sección, el Cliente acuerda indemnizar a Odoo SA una cuota adicional equivalente al 300% del precio aplicable por el número actual de usuarios y aplicaciones instaladas." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:119 +#: ../../content/legal/terms/i18n/enterprise_es.rst:122 msgid "4 Servicios" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:124 +#: ../../content/legal/terms/i18n/enterprise_es.rst:127 msgid "4.1 Servicio de corrección de Bugs" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:126 +#: ../../content/legal/terms/i18n/enterprise_es.rst:129 msgid "Durante la vigencia de este Acuerdo, Odoo SA se compromete a hacer todos los esfuerzos razonables para remediar cualquier Bug presente en el Software y los Módulos adicionales de mantenimiento, que haya reportado el Cliente a través del medio apropiado (como el formulario del sitio web o vía llamada telefónica a los numeros enlistados en `Odoo Help `__, o cuando se trabaja con un Partner a través del medio establecido por el Partner), y a manejar las solicitudes del Cliente dentro de 2 días hábiles posteriores a la creación del reporte por parte del Cliente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:134 +#: ../../content/legal/terms/i18n/enterprise_es.rst:137 msgid "El Cliente recibirá una notificación de la solución adecuada una vez se haya solucionado el Bug. En caso que el Cliente esté usando una versión cubierta, no se le pedirá que actualice el Software a una versión más reciente como solución a un Bug." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:138 +#: ../../content/legal/terms/i18n/enterprise_es.rst:141 msgid "Cuando se corrige un Bug de cualquiera de las versiones cubiertas, Odoo SA se compromete a corregir el error en todas las versiones cubiertas más recientes del software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:141 +#: ../../content/legal/terms/i18n/enterprise_es.rst:144 msgid "Las partes de este Acuerdo reconocen que Odoo SA no es responsable de los Bugs en el Software o en los módulos adicionales de mantenimiento de conformidad con lo establecido en la sección 7.3 de este Acuerdo y en la licencia del Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:146 +#: ../../content/legal/terms/i18n/enterprise_es.rst:149 msgid "4.2 Servicio de actualizaciones de seguridad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:151 +#: ../../content/legal/terms/i18n/enterprise_es.rst:154 msgid "Hospedaje en servidores propios" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:153 +#: ../../content/legal/terms/i18n/enterprise_es.rst:156 msgid "Durante la vigencia de este Acuerdo, Odoo SA se compromete a enviar un “Aviso de Seguridad” al Cliente al identificar algún Bug de seguridad en las versiones cubiertas del Software (excluyendo módulos adicionales), al menos 2 semanas antes de hacer público el Aviso de Seguridad, al menos que el Bug ya haya sido revelado públicamente por algún tercero. Los Avisos de Seguridad pueden incluir una descripción completa del Bug, sus causas, el posible impacto en los sistemas del Cliente y la respectiva solución para cada una de las versiones cubiertas del Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:160 +#: ../../content/legal/terms/i18n/enterprise_es.rst:163 msgid "El Cliente entiende que el Bug y la información establecida en el Aviso de Seguridad deben ser tratados como Información Confidencial de acuerdo a lo descrito en la sección :ref:`confidentiality_es` del presente Acuerdo, hasta la fecha de publicación del Aviso de Seguridad." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:165 +#: ../../content/legal/terms/i18n/enterprise_es.rst:168 msgid "Plataforma en la nube" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:167 +#: ../../content/legal/terms/i18n/enterprise_es.rst:170 msgid "En el momento que exista una medida de seguridad, Odoo SA se compromete a aplicar dicha medida de seguridad ante cualquier Bug que comprometa la seguridad del Software, siempre y cuando este Bug haya sido encontrado en la versión de Odoo Enterprise alojada en la nube y en todos los sistemas bajo el control de esta plataforma, sin requerir de alguna acción manual por parte del Cliente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:175 +#: ../../content/legal/terms/i18n/enterprise_es.rst:178 msgid "4.3 Servicios de actualización" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:180 +#: ../../content/legal/terms/i18n/enterprise_es.rst:183 msgid "Servicio de actualización para el software" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:182 +#: ../../content/legal/terms/i18n/enterprise_es.rst:185 msgid "Durante la vigencia de este Acuerdo, el Cliente puede solicitar la actualización de su versión del Software a través del medio apropiado (generalmente a través de la sección de servicios de actualizaciones del sitio web de Odoo SA), con la finalidad de actualizar la base de datos del Software que tiene a una versión más reciente de las versiones cubiertas (en adelante la “Versión Deseada”)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:188 +#: ../../content/legal/terms/i18n/enterprise_es.rst:191 msgid "Las solicitudes de actualización de los Clientes que usan los servicios en la nube deben ser solicitadas directamente desde el panel de control de la Plataforma en la nube y no requieren ninguna data adicional. Para servicios de hospedaje en servidores locales, el Cliente debe incluir una copia de su base de datos y de la data asociada para realizar la solicitud (usualmente esta información se obtiene del menú de respaldo del Software)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:194 +#: ../../content/legal/terms/i18n/enterprise_es.rst:197 msgid "Este servicio se proporciona a través de una plataforma automatizada que le permite al Cliente realizar actualizaciones sin asistencia una vez que una versión anterior de la base de datos del Cliente ha sido exitosamente actualizada a una versión cubierta." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:198 +#: ../../content/legal/terms/i18n/enterprise_es.rst:201 msgid "El Servicio de Actualización se limita a la conversión técnica y adaptación de la base de datos del Cliente para hacerla compatible con la Versión Deseada, y la corrección de cualquier Bug causado directamente por la operación de actualización que no ocurre usualmente en la Versión Deseada." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:202 +#: ../../content/legal/terms/i18n/enterprise_es.rst:205 msgid "El Cliente tiene la responsabilidad de verificar y validar la base de datos actualizada para detectar bugs, analizar e impacto de los cambios y las nuevas funcionalidades implementadas en la Versión Deseada, y de convertir y adaptar cualquier extensión del Software desarrollada por terceros que haya sido instalada antes de la actualización a la Versión Deseada (por ejemplo, módulos adicionales sin mantenimiento de Odoo). El Cliente puede enviar múltiples solicitudes de actualización de una base de datos hasta que se haya logrado un resultado aceptable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:212 +#: ../../content/legal/terms/i18n/enterprise_es.rst:215 msgid "4.4 Servicios de alojamiento en la nube" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:214 +#: ../../content/legal/terms/i18n/enterprise_es.rst:217 msgid "Si el Cliente decide alojar sus datos en la Plataforma en la Nube, Odoo SA se compromete a proporcionar los siguientes servicios durante la vigencia de este Acuerdo:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:217 +#: ../../content/legal/terms/i18n/enterprise_es.rst:220 msgid "Alojamiento de datos en diferentes regiones geográficas (al menos 3: Europa, América, Asia/Pacifico);" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:219 +#: ../../content/legal/terms/i18n/enterprise_es.rst:222 msgid "Alojamiento en centros de datos nivel III o equivalentes, con un tiempo de actividad de la red del 99.9%;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:221 +#: ../../content/legal/terms/i18n/enterprise_es.rst:224 msgid "Cifrado de comunicaciones SSL de grado A (HTTPS);" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:222 +#: ../../content/legal/terms/i18n/enterprise_es.rst:225 msgid "Copias de seguridad completamente verificadas y automatizadas, duplicadas en múltiples regiones;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:223 +#: ../../content/legal/terms/i18n/enterprise_es.rst:226 msgid "Plan de Contingencia ante desastres, probado regularmente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:225 +#: ../../content/legal/terms/i18n/enterprise_es.rst:228 msgid "Los detalles de los Servicios de alojamiento de datos en la nube están descritos en el Acuerdo sobre el nivel del servicio, disponible en `Cloud SLA `__." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:231 +#: ../../content/legal/terms/i18n/enterprise_es.rst:234 msgid "4.5 Servicios de soporte" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:234 +#: ../../content/legal/terms/i18n/enterprise_es.rst:237 msgid "Alcance" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:236 +#: ../../content/legal/terms/i18n/enterprise_es.rst:239 msgid "Durante la vigencia del presente Acuerdo, el Cliente puede crear un número ilimitado de tickets de soporte sin costos adicionales, exclusivamente para preguntas relacionadas a Bugs (consultar sección :ref:`bugfix_es`) u orientación en cuanto al uso de las funcionalidades estándares del Software y de los módulos adicionales de mantenimiento." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:241 +#: ../../content/legal/terms/i18n/enterprise_es.rst:244 msgid "Otras solicitudes de asistencias como preguntas relacionadas con desarrollos o personalizaciones pueden ser cubiertas mediante otros servicios a contratar por parte de Odoo SA. En caso que no sea claro si una solicitud puede ser respondida por el Servicio de soporte, la decisión queda a discreción de Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:247 +#: ../../content/legal/terms/i18n/enterprise_es.rst:250 msgid "Disponibilidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:249 +#: ../../content/legal/terms/i18n/enterprise_es.rst:252 msgid "Los tickets de soporte pueden ser enviados a través del formulario en el sitio web o a los números de contacto que se encuentran en `Odoo Help `__, o cuando se trabaje con un Partner, en el canal señalado por el Partner, sujeto a los horarios de apertura." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:256 +#: ../../content/legal/terms/i18n/enterprise_es.rst:259 msgid "4.6 Trabajar con un Partner de Odoo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:258 +#: ../../content/legal/terms/i18n/enterprise_es.rst:261 msgid "Para la corrección de Bugs, soporte y servicios de actualización, el Cliente puede trabajar un Partner de Odoo como su principal punto de contacto, o directamente con Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:261 +#: ../../content/legal/terms/i18n/enterprise_es.rst:264 msgid "Odoo SA subcontratará los servicios relacionados a los Módulos adicionales de mantenimiento al Partner de Odoo, quien se convierte en el principal punto de contacto del Cliente en caso que el Cliente decida trabajar con un Partner de Odoo. El Partner de Odoo puede contactar a Odoo SA en nombre del Cliente para obtener asistencia de segundo nivel con respecto a las características estándar del Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:267 +#: ../../content/legal/terms/i18n/enterprise_es.rst:270 msgid "Si el cliente decide trabajar con Odoo SA directamente, los servicios relacionados con los módulos adicionales de mantenimiento serán cubiertos por Odoo SA siempre que el Cliente esté alojado en la plataforma de la nube de Odoo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:274 +#: ../../content/legal/terms/i18n/enterprise_es.rst:277 msgid "5 Cargos y Tarifas" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:279 +#: ../../content/legal/terms/i18n/enterprise_es.rst:282 msgid "5.1 Cargos estándares" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:281 +#: ../../content/legal/terms/i18n/enterprise_es.rst:284 msgid "Los cargos estándares de la suscripción de Odoo Enterprise y los Servicios están basados en la cantidad de Usuarios y las Aplicaciones instaladas que utiliza el Cliente y se especifican por escrito al concluir el Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:285 +#: ../../content/legal/terms/i18n/enterprise_es.rst:288 msgid "Si el Cliente tiene más usuarios o aplicaciones instaladas durante el Plazo que las especificadas en el momento de la celebración de este Acuerdo, el Cliente acepta pagar (al inicio del nuevo Plazo) una tarifa adicional equivalente al precio aplicable de conformidad con la lista de precios por aquellos usuarios o aplicaciones adicionales, por el resto del Plazo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:290 +#: ../../content/legal/terms/i18n/enterprise_es.rst:293 msgid "Además, los servicios de los módulos adicionales de mantenimiento se cobran en función al número de líneas de código de estos módulos. Cuando el cliente opta por el mantenimiento de estos módulos adicionales de mantenimiento, el costo es una tarifa mensual de 16 € por 100 líneas de código (redondeadas a las siguientes 100), al menos que se especifique lo contrario por escrito al celebrar este Acuerdo. Las líneas de código serán contadas con el comando ‘cloc’ del Software, e incluyen todas las líneas de texto en el código fuente de esos módulos, independientemente del lenguaje de programación (Python, Javascript, XML, etc), excluyendo líneas en blanco, comentarios y archivos que no se cargan al instalar o ejecutar el software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:299 +#: ../../content/legal/terms/i18n/enterprise_es.rst:302 msgid "Cuando el Cliente solicita una actualización, por cada módulo adicional de mantenimiento que no haya sido cubierto por los costos de mantenimiento durante los últimos 12 meses, Odoo SA puede cobrar una tarifa adicional única de 16 € por cada 100 líneas de código, por cada mes faltante de cobertura." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:306 +#: ../../content/legal/terms/i18n/enterprise_es.rst:309 msgid "5.2 Cargos de renovación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:308 +#: ../../content/legal/terms/i18n/enterprise_es.rst:311 msgid "Siguiendo la renovación descrita en la sección :ref:`term_es` del presente Acuerdo, si los cargos aplicados durante el Plazo anterior (excluyendo cualquier “Descuento para usuarios iniciales”) son más bajos que el precio aplicable en la lista de precios actual, dichos cargos podrán aumentar 7% como máximo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:316 +#: ../../content/legal/terms/i18n/enterprise_es.rst:319 msgid "5.3 Impuestos" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:318 +#: ../../content/legal/terms/i18n/enterprise_es.rst:321 msgid "Todas las tarifas y cargos son exclusivos de todos los impuestos, tarifas o cargos federales, provinciales, estatales, locales o gubernamentales aplicables (conjuntamente los “Impuestos”). El Cliente es responsable de pagar todos los Impuestos asociados con las compras realizadas por el Cliente en virtud de este Acuerdo, excepto cuando Odoo SA esté legítimamente obligado a pagar o recolectar los Impuestos que el Cliente debe asumir." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:327 +#: ../../content/legal/terms/i18n/enterprise_es.rst:330 msgid "6 Condiciones de los servicios" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:330 +#: ../../content/legal/terms/i18n/enterprise_es.rst:333 msgid "6.1 Obligaciones del cliente" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:332 +#: ../../content/legal/terms/i18n/enterprise_es.rst:335 msgid "El Cliente se compromete a:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:334 +#: ../../content/legal/terms/i18n/enterprise_es.rst:337 msgid "Pagar a Odoo SA cualquier cargo aplicable por los Servicios del presente Acuerdo, según las condiciones de pago especificadas en la factura correspondiente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:338 +#: ../../content/legal/terms/i18n/enterprise_es.rst:341 msgid "Notificar inmediatamente a Odoo SA cuando su número real de usarios o aplicaciones instaladas exceda el número especificado al final del Acuerdo y, en este caso, el pago de la tarifa adicional aplicable como se describe en la sección :ref:`charges_standard_es`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:343 +#: ../../content/legal/terms/i18n/enterprise_es.rst:346 msgid "Tomar todas las medidas necesarias para garantizar la ejecución no modificada de la parte del Software que verifica la validez del uso de Odoo Enterprise Edition, como se describe en la sección :ref:`enterprise_access_es`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:347 +#: ../../content/legal/terms/i18n/enterprise_es.rst:350 msgid "Designar a 1 persona de contacto dedicada del Cliente durante toda la duración del Acuerdo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:349 +#: ../../content/legal/terms/i18n/enterprise_es.rst:352 msgid "Designar a 1 persona de contacto que se dedique al Cliente a lo largo de la Duración del Acuerdo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:351 +#: ../../content/legal/terms/i18n/enterprise_es.rst:354 msgid "Notificar por escrito a Odoo SA 30 días antes de cambiar el punto principal de contacto para trabajar con otro Partner de Odoo o directamente con Odoo SA" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:355 +#: ../../content/legal/terms/i18n/enterprise_es.rst:358 msgid "Cuando el Cliente elige usar la Plataforma en la nube, el Cliente acuerda además:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:358 +#: ../../content/legal/terms/i18n/enterprise_es.rst:361 msgid "Tomar todas las medidas razonables para mantener sus cuentas de Usuario seguras, incluso al elegir una contraseña segura y no compartirla con nadie más;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:362 +#: ../../content/legal/terms/i18n/enterprise_es.rst:365 msgid "Hacer uso razonable de los servicios de alojamiento, cone xclusiónde cualquier actividad ilegal o actividades abusivas, y observar estrictamente las reglas descritas en la Política de uso aceptable publicada en `acceptable use `__." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:366 +#: ../../content/legal/terms/i18n/enterprise_es.rst:369 msgid "Cuando el Cliente elige la opción de Auto-alojamiento, el Cliente acepta además:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:369 +#: ../../content/legal/terms/i18n/enterprise_es.rst:372 msgid "Tomar todas las medidas razonables para proteger los archivos y las bases de datos del Cliente y para garantizar que los datos del Cliente sean seguros y estén protegidos, reconociendo que Odoo SA no se hace responsable de ninguna pérdida de datos" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:373 +#: ../../content/legal/terms/i18n/enterprise_es.rst:376 msgid "Otorgar a Odoo SA el acceso necesario para verificar la validez de la Edición Enterprise de Odoo uso a solicitud (por ejemplo, si la validación automática no es válida para el Cliente);" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:377 +#: ../../content/legal/terms/i18n/enterprise_es.rst:380 msgid "6.2 No solicitar o contratar" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:378 +#: ../../content/legal/terms/i18n/enterprise_es.rst:381 msgid "Excepto cuando la otra Parte de su consentimiento por escrito, cada una de las Partes, sus filiales y representantes acuerdan no solicitar u ofrecer empleo a ningún empleado de la otra Parte que esté involucrado en la prestación o el uso de los Servicios en virtud de este Acuerdo, durante la vigencia del Acuerdo y por un periodo de 12 meses a partir de la fecha de terminación o vencimiento de este Acuerdo. En caso que ocurra algún incumplimiento de las condiciones de esta sección, se dará por terminado el contrato con el empleado en cuestión y la Parte que ha incumplido esta prohibición acuerda indemnizar a la otra Parte la cifra de treinta mil euros 30.000 EUR (€)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:389 +#: ../../content/legal/terms/i18n/enterprise_es.rst:392 msgid "6.3 Publicidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:391 +#: ../../content/legal/terms/i18n/enterprise_es.rst:394 msgid "Salvo que se notifique lo contrario por escrito, cada Parte otorga a la otra una licencia mundial intransferible, no exclusiva, libre de regalías, para reproducir y mostrar el nombre, logotipos y marcas de la otra Parte, con el único propósito de referirse a la otra Parte como su cliente o proveedor, en sitios web, comunicados de prensa y otros medios de marketing." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:399 +#: ../../content/legal/terms/i18n/enterprise_es.rst:402 msgid "6.4 Confidencialidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:407 +#: ../../content/legal/terms/i18n/enterprise_es.rst:410 msgid "Definición de \"Información confidencial\":" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:402 +#: ../../content/legal/terms/i18n/enterprise_es.rst:405 msgid "Toda la información divulgada por una de las Partes del presente Acuerdo, ya sea oralmente o por escrito, designada como confidencial o razonablemente considerada confidencial dada la naturaleza de la información y las circunstancias de divulgación. En particular, cualquier información relacionada a los negocios, asuntos, productos, desarrollos, secretos comerciales, “know-how”, el personal, los clientes y los proveedores de cualquiera de las Partes del presente Acuerdo, debe ser considerada como confidencial." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:409 +#: ../../content/legal/terms/i18n/enterprise_es.rst:412 msgid "Para cualquier tipo de información confidencial recibida durante el Plazo de este Acuerdo, la Parte que haya recibido la información confidencial hará uso del mismo grado de precaución que usaría esta Parte para proteger la confidencialidad de información similar que le pertenezca con un grado de precaución razonable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:414 +#: ../../content/legal/terms/i18n/enterprise_es.rst:417 msgid "La Parte que haya recibido la información confidencial puede dar a conocer Información Confidencial de la Parte que haya divulgado dicha información en la medida en que la ley se lo permita. La Parte que haya recibido la información confidencial le dará aviso previo a la Parte que haya divulgado dicha información sobre la información que planea dar a conocer, en la medida en que la ley se lo permita." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:423 +#: ../../content/legal/terms/i18n/enterprise_es.rst:426 msgid "6.5 Protección de datos" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:428 +#: ../../content/legal/terms/i18n/enterprise_es.rst:431 msgid "Definiciones" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:426 +#: ../../content/legal/terms/i18n/enterprise_es.rst:429 msgid "Los términos “Datos Personales”, “Responsable del tratamiento”, “Tratamiento” tienen los mismos significados que en el Reglamento (UE) 2016/679 y la Directiva 2002/58 / CE, y cualquier reglamento o legislación que los modifique o sustituya (en adelante, “Legislacion de Proteccion de Datos”)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:431 +#: ../../content/legal/terms/i18n/enterprise_es.rst:434 msgid "Procesamiento de datos personales" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:433 +#: ../../content/legal/terms/i18n/enterprise_es.rst:436 msgid "Las Partes reconocen que la base de datos del Cliente puede contener Datos Personales, de los cuales el Cliente es el Responsable del tratamiento. Esta data será procesada por Odoo SA cuando el Cliente lo indique, al usar cualquiera de los Servicios que requieran una base de datos (por ejemplo, el servicio de hospedaje en la nube o los servicios de actualizaciones), o si el Cliente transfiere su base de datos o una parte de su base de datos a Odoo SA por cualquier motivo relacionado con este Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:440 +#: ../../content/legal/terms/i18n/enterprise_es.rst:443 msgid "Este procesamiento se realizará de conformidad con la legislación de protección de datos. En particular, Odoo SA se compromete a:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:443 +#: ../../content/legal/terms/i18n/enterprise_es.rst:446 msgid "(a) Solo procesar los datos personales cuando y como lo indique el Cliente, y para elp ropósito de realizar uno de los Servicios en virtud de este Acuerdo, a menos que sea requerido por la ley, en cuyo caso, Odoo SA proporcionará un aviso previo al Cliente, a menos que la ley lo prohíba;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:446 +#: ../../content/legal/terms/i18n/enterprise_es.rst:449 msgid "(b) garantizar que todas las personas dentro de Odoo SA” autorizadas para procesar los Datos personales estén comprometidos con la confidencialidad;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:448 +#: ../../content/legal/terms/i18n/enterprise_es.rst:451 msgid "(c) implementar y mantener medidas técnicas y organizativas adecuadas para proteger los datos personales contra el procesamiento no autorizado o ilegal y contra la pérdida accidental, destrucción, daño, robo, alteración o divulgación;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:451 +#: ../../content/legal/terms/i18n/enterprise_es.rst:454 msgid "(d) enviará sin demora al Cliente cualquier solicitud de protección de datos que se haya enviado a Odoo SA con respecto a la base de datos del Cliente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:453 +#: ../../content/legal/terms/i18n/enterprise_es.rst:456 msgid "(e) notificar al Cliente inmediatamente al momento de conocer y confirmar cualquier accidente, el procesamiento no autorizado o ilegal de, la divulgación o el acceso a los datos personales;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:455 +#: ../../content/legal/terms/i18n/enterprise_es.rst:458 msgid "(f) notificar al Cliente si las instrucciones de procesamiento infringen la Protección de datos aplicables a la legislación, en opinión de Odoo SA;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:457 +#: ../../content/legal/terms/i18n/enterprise_es.rst:460 msgid "(g) poner a disposición del Cliente toda la información necesaria para demostrar el cumplimiento con la legislación de protección de datos, permitir y contribuir razonablemente a las auditorías, incluidas las inspecciones, realizadas o exigidas por el Cliente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:460 +#: ../../content/legal/terms/i18n/enterprise_es.rst:463 msgid "(h) eliminar permanentemente todas las copias de la base de datos del Cliente en posesión de Odoo SA, o devolver dichos datos, a elección del Cliente, a la terminación de este Acuerdo, sujeto a los retrasos especificados en la Política de privacidad de Odoo SA (`Privacy `__)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:465 +#: ../../content/legal/terms/i18n/enterprise_es.rst:468 msgid "En relación a los puntos (d) y (f), el Cliente acepta proporcionar a Odoo SA información de contacto precisa en todo momento, según sea necesario para notificar al responsable de la Legislación de Protección de Datos del Cliente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:470 +#: ../../content/legal/terms/i18n/enterprise_es.rst:473 msgid "Sub procesadores" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:472 +#: ../../content/legal/terms/i18n/enterprise_es.rst:475 msgid "El Cliente reconoce y acepta que, para proporcionar los Servicios, Odoo SA puede utilizar a terceros como proveedores de servicios para procesar Datos Personales (en adelante “Sub-procesadores”). Odoo SA se compromete a utilizar Sub-procesadores únicamente de conformidad con la Legislación de Protección de Datos. Este uso estará amparado bajo un contrato entre Odoo SA y el Sub-procesador que de garantías para estos servicios." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:478 +#: ../../content/legal/terms/i18n/enterprise_es.rst:481 msgid "La Política de privacidad de Odoo SA, publicada en `Odoo Privacy `_ establece información actualizada en relación a los nombres y propósitos de los Sub-procesadores que se encuentran actualmente en uso por Odoo SA para la ejecución de los Servicios." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:485 +#: ../../content/legal/terms/i18n/enterprise_es.rst:488 msgid "6.6 Terminación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:487 +#: ../../content/legal/terms/i18n/enterprise_es.rst:490 msgid "En el supuesto de que alguna de las Partes incumpla con alguna de sus obligaciones establecidas en el presente Acuerdo, y si dicho incumplimiento no ha sido subsanado entre los siguientes 30 días contados a partir de la fecha de notificación escrita de dicho incumplimiento, este Acuerdo se considerará como terminado inmediatamente por la Parte que ha cumplido sus obligaciones." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:492 +#: ../../content/legal/terms/i18n/enterprise_es.rst:495 msgid "De igual manera, Odoo SA puede terminar el Acuerdo inmediatamente si el Cliente no cumple con su obligación de pago del Servicio dentro de los 21 días siguientes a la fecha de la respectiva facturación, y después de haber emitido al menos 3 recordatorios de pago." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:496 +#: ../../content/legal/terms/i18n/enterprise_es.rst:499 msgid "Disposiciones supervivientes: Las secciones \":ref:`confidentiality_es`\", “:ref:`disclaimers_es`\",“:ref:`liability_es`\", y “:ref:`general_provisions_es`” estarán vigentes incluso después de cualquier terminación o vencimiento del presente Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:503 +#: ../../content/legal/terms/i18n/enterprise_es.rst:506 msgid "7 Garantías, Renuncias, Responsabilidad Civil." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:508 +#: ../../content/legal/terms/i18n/enterprise_es.rst:511 msgid "7.1 Garantías" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:510 +#: ../../content/legal/terms/i18n/enterprise_es.rst:513 msgid "Odoo SA posee los derechos de autor o un equivalente [#cla1]_ sobre el 100% del código del Software. Odoo SA confirma que todas las bibliotecas de software necesarias para el uso del Software están disponibles bajo una licencia compatible con la licencia del Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:514 +#: ../../content/legal/terms/i18n/enterprise_es.rst:517 msgid "Durante la vigencia del presente Acuerdo, Odoo SA se compromete a emplear esfuerzos comercialmente razonables para ejecutar los Servicios de conformidad con los estándares de la industria generalmente aceptados, siempre que:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:518 +#: ../../content/legal/terms/i18n/enterprise_es.rst:521 msgid "Los sistemas informáticos del Cliente se encuentren en un buen estado operacional y, para el alojamiento en servidores propios, el Software será instalado en un ambiente adecuado y operativo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:521 +#: ../../content/legal/terms/i18n/enterprise_es.rst:524 msgid "El Cliente brindará información pertinente para la resolución de problemas y, para el alojamiento en servidores propios, cualquier acceso que Odoo SA pueda necesitar para identificar, reproducir y solventar los problemas;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:525 +#: ../../content/legal/terms/i18n/enterprise_es.rst:528 msgid "Todas las cantidades debidas a Odoo SA hayan sido pagadas." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:527 +#: ../../content/legal/terms/i18n/enterprise_es.rst:530 msgid "Odoo SA está obligado únicamente a reanudar la ejecución de los Servicios sin cargos adicionales en caso que Odoo SA incumpla alguna de las garantías establecidas. Este será el único y exclusivo recurso que el Cliente podrá usar." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:531 +#: ../../content/legal/terms/i18n/enterprise_es.rst:534 msgid "Contribuciones externas son cubiertas por el Acuerdo de Licencia de Derechos de Autor, el cual provee a Odoo SA una licencia de derechos de autor y de patente permanente, gratis e irrevocable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:535 +#: ../../content/legal/terms/i18n/enterprise_es.rst:538 msgid "Las contribuciones externas están cubiertas por un `acuerdo de licencia de derechos de autor `__, que proporciona una licencia de derechos de autor y patente permanente, gratuita e irrevocable a Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:543 +#: ../../content/legal/terms/i18n/enterprise_es.rst:546 msgid "7.2 Aviso legal" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:545 +#: ../../content/legal/terms/i18n/enterprise_es.rst:548 msgid "Excepto por lo establecido expresamente en este Acuerdo, ninguna de las Partes podrá ofrecer garantías de ningún tipo, ya sean expresas, implícitas, estatutarias o de otro tipo, y cada Parte rechaza cualquier garantía implícita, tal y como garantías de comercialización, idóneas para un propósito especifico o de no cumplimiento, en la medida máxima permitida por la ley aplicable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:550 +#: ../../content/legal/terms/i18n/enterprise_es.rst:553 msgid "Odoo SA no garantiza que el Software cumpla con leyes o regulaciones locales o internacionales." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:555 +#: ../../content/legal/terms/i18n/enterprise_es.rst:558 msgid "7.3 Limitación de responsabilidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:557 +#: ../../content/legal/terms/i18n/enterprise_es.rst:560 msgid "De conformidad a la medida máxima permitida por la ley, la responsabilidad agregada de cada una de las Partes junto con sus afiliados que surjan de o estén relacionados con este Acuerdo, no excederá el 50% del monto total pagado por el Cliente en virtud de este Acuerdo durante los 12 meses inmediatamente anteriores a la fecha del evento que da lugar a tal reclamo. Las reclamaciones múltiples no ampliarán esta limitación." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:563 +#: ../../content/legal/terms/i18n/enterprise_es.rst:566 msgid "En ningún caso, ninguna de las Parte o sus afiliados serán responsables por daños directos, especiales, ejemplares, incidentales o consecuentes de cualquier tipo, incluidos, entre otros, la pérdida de ingresos, ganancias, ahorros, pérdida de negocios u otras pérdidas financieras, costos de inactividad o demora, datos perdidos o dañados, que surjan de o en conexión con este Acuerdo, independientemente de la forma de acción, ya sea en contrato, responsabilidad civil (incluida negligencia estricta) o cualquier otra teoría legal o equitativa, incluso si una de las Partes o sus afiliados han sido informados de la posibilidad de tales daños, o si las medidas de una de las Partes o sus afiliados no cumplen con su propósito esencial." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:575 +#: ../../content/legal/terms/i18n/enterprise_es.rst:578 msgid "7.4 Fuerza mayor" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:577 +#: ../../content/legal/terms/i18n/enterprise_es.rst:580 msgid "Ninguna de las Partes será responsable ante la otra Parte por la demora o la falta de cumplimiento de sus obligaciones estipuladas en este Acuerdo cuando tal incumplimiento o retraso sea causado por fuerza mayor, tal y como regulaciones gubernamentales, incendios, huelgas, guerras, inundaciones, accidentes, epidemias, embargos, apropiaciones de instalaciones o productos en su totalidad o en parte por cualquier autoridad gubernamental o pública, o cualquier otra causa o causas, ya sean de naturaleza similares o diferentes, que están más allá del control razonable de dicha parte siempre que tal causa o causas existan efectivamente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:588 +#: ../../content/legal/terms/i18n/enterprise_es.rst:591 msgid "8 Disposiciones generales" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:593 +#: ../../content/legal/terms/i18n/enterprise_es.rst:596 msgid "8.1 Ley aplicable" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:595 +#: ../../content/legal/terms/i18n/enterprise_es.rst:598 msgid "Este Acuerdo y todos los pedidos del Cliente estarán sujetos a las leyes del Reino de Bélgica. Cualquier disputa que surja en relación a este Acuerdo o de cualquier pedido del Cliente será sujeta a la jurisdicción exclusiva del Tribunal de Nivelles pertinente para litigar estas disputas." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:602 +#: ../../content/legal/terms/i18n/enterprise_es.rst:605 msgid "8.2 Divisibilidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:604 +#: ../../content/legal/terms/i18n/enterprise_es.rst:607 msgid "En caso de que una o más de las disposiciones establecidas en este Acuerdo o cualquiera de sus aplicaciones sean inválidas, ilegales o no exigibles en algún aspecto, la validez, legalidad y exigibilidad de las disposiciones restantes del presente Acuerdo y sus aplicaciones no se verán afectadas ni menoscabadas ninguna manera. Ambas Partes se comprometen a reemplazar cualquier provisión inválida, ilegal o inaplicable de este Acuerdo por una provisión válida que tenga el mismo efecto y objetivo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:614 +#: ../../content/legal/terms/i18n/enterprise_es.rst:617 msgid "9 Apéndice A: Licencia de Odoo Enterprise Edition" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:618 +#: ../../content/legal/terms/i18n/enterprise_es.rst:621 msgid "La versión Enterprise de Odoo tiene la licencia Odoo Enterprise Edition v1.0, la cual es definida de la siguiente manera:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:627 +#: ../../content/legal/terms/i18n/enterprise_es.rst:630 msgid "Ver :ref:`odoo_enterprise_license`." msgstr "" @@ -1963,605 +2071,621 @@ msgstr "" msgid "Odoo Enterprise Subscription Agreement (FR)" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:8 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:9 +msgid "`Download PDF `_" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:11 msgid "Ceci est une traduction en français du contrat “Odoo Enterprise Subscription Agreement”. Cette traduction est fournie dans l’espoir qu’elle facilitera sa compréhension, mais elle n'a aucune valeur légale. La seule référence officielle des termes du contrat “Odoo Enterprise Subscription Agreement” est la :ref:`version originale en anglais `." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:28 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:34 msgid "En vous abonnant aux services de Odoo Enterprise (les \"Services\") fournis par Odoo SA et ses filiales (collectivement, \"Odoo SA\") en relation avec Odoo Enterprise Edition ou Odoo Community Edition (le \"Logiciel\"), hébergé sur le plate-formes Cloud d'Odoo SA (la \"Plate-forme Cloud\") ou sur site (\"Auto-Hébergement\"), vous (le \"Client\") acceptez d'être lié par les conditions générales suivantes (le \"Contrat\")." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:37 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:43 msgid "1 Durée du Contrat" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:39 -msgid "La durée du présent contrat (la \"Durée\") sera spécifiée par écrit à la conclusion du Contrat, à compter de la date de la conclusion. Celui-ci est automatiquement reconduit pour une même durée, à moins que l'une des parties n’envoie à l'autre partie un préavis écrit de résiliation, et au moins 30 jours avant la date d'échéance du contrat." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_fr.rst:47 -msgid "2 Définitions" +#: ../../content/legal/terms/i18n/enterprise_fr.rst:45 +msgid "La durée du présent Contrat (la \"Durée\") sera spécifiée par écrit à la conclusion du Contrat, à compter de la date de la conclusion. Celui-ci est automatiquement reconduit pour une même durée, à moins que l'une des parties n’envoie à l'autre partie un préavis écrit de résiliation, et au moins 30 jours avant la date d'échéance du contrat." msgstr "" #: ../../content/legal/terms/i18n/enterprise_fr.rst:53 +msgid "2 Définitions" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:59 msgid "Utilisateur" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:50 -msgid "Tout compte utilisateur indiqué comme actif dans le Logiciel et donnant accès au mode création et/ou édition. Les comptes désactivés ainsi que ceux utilisés par des personnes ou systèmes extérieur(e)s n'ayant qu'un accès limité au Logiciel via le portail (\"Utilisateurs Portail\") ne sont pas comptés comme Utilisateurs." -msgstr "" - #: ../../content/legal/terms/i18n/enterprise_fr.rst:56 -msgid "Une \"App\" est un ensemble de fonctionnalités, disponible pour installation dans le Logiciel, et inclus dans la section Tarifs Odoo sur `le site d'Odoo SA `_, au moment de la conclusion de ce Contrat." +msgid "Tout compte utilisateur indiqué comme actif dans le Logiciel et donnant accès au mode création et/ou édition. Les comptes désactivés ainsi que ceux utilisés par des personnes ou systèmes extérieurs n'ayant qu'un accès limité au Logiciel via le portail (\"Utilisateurs Portail\") ne sont pas comptés comme Utilisateurs." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:63 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:62 +msgid "Une \"App\" est un ensemble de fonctionnalités, disponible pour installation dans le Logiciel." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:67 msgid "Partenaire Odoo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:61 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:65 msgid "Un Partenaire Odoo est un individu ou société tierce, choisi par le Client et qui collabore avec celui-ci pour les services liés à Odoo. Le Client peut choisir à tout moment de travailler avec un autre Partenaire Odoo, ou avec Odoo SA directement (moyennant préavis)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:70 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:74 msgid "Module Supplémentaire" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:66 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:70 msgid "Un Module Supplémentaire est un répertoire de fichiers de code source, ou un ensemble de personnalisations nécessitant du code Python créées dans une base de données (par ex. avec Odoo Studio), pour ajouter des fonctionnalités ou changer des comportements du Logiciel. Il peut avoir été développé par le Client, par Odoo SA, par un Partenaire Odoo pour le compte du Client, ou par des tiers." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:75 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:79 msgid "Module Supplémentaire Couvert" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:73 -msgid "Un Module Supplémentaire Couvert est un Module Supplémentaire pour lequel le Client choisit de payer un abonnement de maintenance afin d'obtenir de l'assistance, des corrections de bug et des migrations." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:77 +msgid "Un Module Supplémentaire Couvert est un Module Supplémentaire pour lequel le Client choisit de payer un abonnement de maintenance afin d'obtenir de l'assistance, des corrections de bugs et des migrations." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:78 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:82 msgid "Désigne toute défaillance du Logiciel ou d'un Module Supplémentaire Couvert, qui se traduit par un arrêt complet, un message d'erreur avec trace d'exécution, ou une brèche de sécurité, et n'est pas directement causé par un problème d'installation ou une configuration défectueuse. Un non-respect des spécifications ou des besoins sera considéré comme un Bug à la discrétion d'Odoo SA (en général, lorsque le Logiciel ne produit pas les résultats ou la performance pour lesquels il a été conçu, ou lorsqu'une fonctionnalité spécifique à un pays ne répond plus aux exigences comptables légales de ce pays)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:89 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:92 msgid "Versions Couvertes" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:87 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:91 msgid "Sauf exception explicite, tous les Services dans le cadre du présent contrat s'appliquent uniquement aux Versions Couvertes du Logiciel, qui comprennent les 3 plus récentes versions majeures." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:94 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:97 +msgid "Formule d'Abonnement" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:95 +msgid "Une Formule d'Abonnement définit un ensemble d'Apps, fonctionnalités et solutions d'hébergement couvertes par ce Contrat, tel que précisé par écrit à la conclusion de ce Contrat." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:102 msgid "3 Accès au Logiciel" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:96 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:104 msgid "Le Client peut utiliser le Logiciel hébergé sur la Plate-forme Cloud, ou choisir l'option de l'Auto-Hébergement. La Plate-forme Cloud est hébergée et entièrement gérée par Odoo SA, and accédée à distance par le Client. En cas d'Auto-Hébergement, le Client héberge lui-même le Logiciel sur un système informatique de son choix, hors du contrôle d'Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:101 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:109 msgid "Pour toute la durée du présent Contrat, Odoo SA octroie au Client une licence non exclusive, non transférable d'utilisation (exécution, modification, exécution après modification) du logiciel Odoo Enterprise Edition, conformément aux conditions énoncées à la section :ref:`appendix_a_fr`." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:105 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:113 msgid "Le Client accepte de prendre toutes les mesures nécessaires pour garantir l'exécution sans aucune modification de la partie du Logiciel qui vérifie la validité de l'utilisation d'Odoo Enterprise Edition et recueille des statistiques à cet effet, y compris mais sans s'y limiter, l'exécution du Logiciel, le nombre d'Utilisateurs, les Apps installées et le nombre de lignes de code des Modules Supplémentaires Couverts." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:111 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:119 msgid "Odoo SA s'engage à ne pas divulguer à une tierce partie d'informations chiffrées personnelles ou spécifiques sans le consentement du Client, et à traiter toutes les données recueillies en respectant sa politique officielle de confidentialité, telle que publiée sur https://www.odoo.com/privacy." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:116 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:124 msgid "À l'expiration ou la résiliation de ce Contrat, cette licence est immédiatement révoquée et le Client accepte de cesser toute utilisation du logiciel Odoo Enterprise Edition et de la Plate-forme Cloud." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:120 -msgid "Si le Client devait enfreindre les dispositions de la présente section, il accepte de payer à Odoo SA des frais supplémentaires équivalents à 300 % du tarif en vigueur applicable correspondant au nombre réel d'Utilisateurs et aux Apps installées." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:128 +msgid "Si le Client devait enfreindre les dispositions de la présente section, il accepte de payer à Odoo SA des frais supplémentaires équivalents à 300 % du tarif en vigueur applicable correspondant au nombre réel d'Utilisateurs." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:128 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:136 msgid "4 Services inclus" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:133 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:141 msgid "4.1 Service de correction de Bugs" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:135 -msgid "Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts raisonnables pour corriger tout Bug du Logiciel ou des Modules Supplémentaires Couverts qui pourrait être signalé par le Client en suivant la procédure appropriée (généralement par le biais du formulaire en ligne ou des numéros de téléphone indiqués sur Module Supplémentaire Couvert, ou en cas de travail avec un Partenaire Odoo, le canal prévu par le partenaire), et de commencer à traiter ces signalements du Client dans un délai de 2 jours ouvrables." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:143 +msgid "Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts raisonnables pour corriger tout Bug du Logiciel ou des Modules Supplémentaires Couverts qui pourrait être signalé par le Client en suivant la procédure appropriée (généralement par le biais du formulaire en ligne ou des numéros de téléphone indiqués sur http://www.odoo.com.help, ou en cas de travail avec un Partenaire Odoo, le canal prévu par le partenaire), et de commencer à traiter ces signalements du Client dans un délai de 2 jours ouvrables." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:142 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:150 msgid "Dès que le Bug est remédié, un correctif approprié sera communiqué au Client. Si le Client utilise une Version Couverte, il ne lui sera jamais demandé de passer à une Version Couverte plus récente pour obtenir un correctif." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:146 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:154 msgid "Lorsqu'un Bug est corrigé dans une Version Couverte, Odoo SA s'engage à le corriger dans toutes les Versions Couvertes plus récentes du Logiciel." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:149 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:157 msgid "Les deux parties reconnaissent que comme spécifié dans la licence du Logiciel et à la section :ref:`liability_fr` de ce Contrat, Odoo SA ne peut être tenue responsable des Bugs du Logiciel ou des Modules Supplémentaires Couverts." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:155 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:163 msgid "4.2 Mises à jour de sécurité" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:160 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:168 msgid "Auto-Hébergement" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:162 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:170 msgid "Pour la durée du Contrat, Odoo SA s'engage à envoyer une \"alerte de sécurité\"\" au Client pour tout Bug présentant un risque de sécurité qui serait découvert dans les Versions Couvertes du Logiciel (à l'exclusion des Modules Supplémentaires), au moins 2 semaines avant de rendre ladite alerte de sécurité publique, et ce à moins que le Bug ait déjà été rendu public par un tiers. Les alertes de sécurité comprennent une description complète du Bug, de sa cause, ses conséquences possibles sur les systèmes du Client, et le correctif correspondant pour chaque Version Couverte." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:169 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:177 msgid "Le Client s'engage à traiter le Bug de sécurité et les informations figurant dans l'alerte de sécurité comme des Informations Confidentielles telles que décrites à la section :ref:`confidentiality_fr` pendant toute la période d'embargo avant la divulgation publique." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:176 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:184 msgid "Plate-forme Cloud" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:178 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:186 msgid "Odoo SA s'engage à appliquer les correctifs de sécurité pour tout Bug de sécurité découvert dans une version du Logiciel hébergé sur la Plate-forme Cloud, sur tous les systèmes sous son contrôle, dès que le correctif est disponible, et sans intervention manuelle du Client." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:186 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:194 msgid "4.3 Service de migration" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:191 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:199 msgid "Service de migration du Logiciel" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:193 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:201 msgid "Pour la durée du présent Contrat, le Client peut soumettre des demandes de migration en suivant les procédures appropriées (généralement, via le site du service de migration d'Odoo SA), afin de convertir une base de données du Logiciel depuis n'importe quelle version du Logiciel vers une Version Couverte plus récente (la \"Version Cible\")." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:198 -msgid "Pour la Plate-forme Cloud, les demandes de migration sont envoyées directement depuis la panneau de contrôle de la Plate-forme Cloud, et ne requièrent pas d'envoi de données. Pour l'Auto-Hébergement, les demandes de migration doivent inclure une copie complète de la base de données du Client et les données associées (généralement obtenues à partir du menu Backup du Logiciel)." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:206 +msgid "Pour la Plate-forme Cloud, les demandes de migration sont envoyées directement depuis le panneau de contrôle de la Plate-forme Cloud, et ne requièrent pas d'envoi de données. Pour l'Auto-Hébergement, les demandes de migration doivent inclure une copie complète de la base de données du Client et les données associées (généralement obtenues à partir du menu Backup du Logiciel)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:205 -msgid "Ce service est fourni par le biais d'une plateforme automatisée, afin de permettre au Client d'effectuer des migration sans intervention humain, dès lors qu’une version précédente de la base de données du Client a été migrée avec succès pour une Version Couverte donnée." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:213 +msgid "Ce service est fourni par le biais d'une plate-forme automatisée, afin de permettre au Client d'effectuer des migrations sans intervention humaine, dès lors qu’une version précédente de la base de données du Client a été migrée avec succès pour une Version Couverte donnée." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:209 -msgid "Le service de migration est limité à la conversion et à l'adaptation techniques de la base de données du Client pour la rendre compatible avec la Version Cible, et à la correction de tout Bug directement causé par l'opération de migration, et ne se produisant normalement pas dans la Version Cible, et la conversion du code et des données des Modules Supplémentaires Couverts vers la Version Cible." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:217 +msgid "Le service de migration est limité à la conversion et à l'adaptation techniques de la base de données du Client pour la rendre compatible avec la Version Cible, à la correction de tout Bug directement causé par l'opération de migration, et ne se produisant normalement pas dans la Version Cible, et la conversion du code source et des données des Modules Supplémentaires Couverts vers la Version Cible." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:215 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:223 msgid "Il incombe au Client de vérifier et valider la base de données migrée afin de détecter tout Bug, d'analyser l'impact des changements et des nouvelles fonctionnalités ajoutées dans la Version Cible, de convertir et d'adapter pour la Version Cible les modules tiers du Logiciel qui auraient été installées dans la base de données avant la migration (par ex. des Modules Supplémentaires non-couverts). Le client peut soumettre plusieurs demandes de migration pour une base de données, jusqu'à ce qu'un résultat satisfaisant soit obtenu." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:226 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:234 msgid "4.4 Service d'Hébergement Cloud" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:228 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:236 msgid "Pour la durée du présent Contrat, lorsque le Client choisit d'utiliser la Plate-forme Cloud, Odoo SA s'engage à fournir au minimum le service suivant:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:231 -msgid "Choix de plusieurs régions d'hébergement (minimum 3: Europe, America, Asia/Pacific)" +#: ../../content/legal/terms/i18n/enterprise_fr.rst:239 +msgid "Choix de plusieurs régions d'hébergement (minimum 3: Europe, Amérique, Asie/Pacifique)" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:232 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:240 msgid "Hébergement en centre de données Tiers-III ou équivalent, avec 99.9% de disponibilité" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:233 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:241 msgid "Cryptage des communications SSL Grade A (HTTPS)" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:234 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:242 msgid "Sauvegardes automatisées et vérifiées, répliquées dans plusieurs régions" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:235 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:243 msgid "Plan de Reprise d'Activité, testé régulièrement" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:237 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:245 msgid "Les détails du Service d'Hébergement Cloud sont décrits sur la page du Service Level Agreement: https://www.odoo.com/cloud-sla." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:244 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:252 msgid "4.5 Service d'Assistance" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:247 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:255 msgid "Portée" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:249 -msgid "Pour la durée du présent Contrat, le Client peut ouvrir un nombre non limité de demandes d'assistance sans frais, exclusivement pour des questions relatives à des Bugs (voir :ref:`bugfix_fr`) ou des explications au sujet de l'utilisation des fonctions standard du Logiciel et des Modules Supplémentaires Couverts" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_fr.rst:254 -msgid "D'autres types de demandes, telles que celles relatives à des développements ou des personnalisations, peuvent être couvertes par l'achat d'un contrat de service séparé. Au cas où il n'est pas clair qu'une demande est couverte par ce Contrat, la décision sera à la discrétion d'Odoo SA." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_fr.rst:260 -msgid "Disponibilité" +#: ../../content/legal/terms/i18n/enterprise_fr.rst:257 +msgid "Pour la durée du présent Contrat, le Client peut ouvrir un nombre non limité de demandes d'assistance sans frais, exclusivement pour des questions relatives à des Bugs (voir :ref:`bugfix_fr`) ou des explications au sujet de l'utilisation des fonctions standards du Logiciel et des Modules Supplémentaires Couverts" msgstr "" #: ../../content/legal/terms/i18n/enterprise_fr.rst:262 -msgid "Les demandes d'assistances peuvent être soumises à tout moment en ligne via https://www.odoo.com/help, ou par téléphone directement aux différents bureaux d'Odoo SA, ou en cas de travail avec un Partenaire Odoo, le canal préconisé par ce partenaire, pendant les heures de bureau correspondantes." +msgid "D'autres types de demandes, telles que celles relatives à des développements ou des personnalisations, peuvent être couvertes par l'achat d'un contrat de service séparé. Au cas où il n'est pas clair qu'une demande est couverte par ce Contrat, la décision sera à la discrétion d'Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:271 -msgid "Collaboration avec un Partenaire Odoo" +#: ../../content/legal/terms/i18n/enterprise_fr.rst:268 +msgid "Disponibilité" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:273 -msgid "Pour les services de correction de Bug, d'assistance et de migration, le Client peut choisir de collaborer avec un Partenaire Odoo comme point de contact principal, ou directement avec Odoo SA." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:270 +msgid "Les demandes d'assistances peuvent être soumises via le formulaire en ligne ou les numéros de téléphone indiqués sur https://www.odoo.com/help, ou en cas de travail avec un Partenaire Odoo, le canal préconisé par ce partenaire, pendant les heures de bureau correspondantes." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:277 -msgid "Si le Client choisit un Partenaire Odoo, Odoo SA sous-traitera les services liés au Modules Supplémentaires Couverts à ce partenaire, qui deviendra le point de contact principal du client. Le Partenaire Odoo peut obtenir de l'assistance de second niveau auprès d'Odoo SA pour le compte du Client, concernant les fonctions standard du Logiciel." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:279 +msgid "4.6 Collaboration avec un Partenaire Odoo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:282 -msgid "Si le Client décide de collaborer directement avec Odoo SA, les services liés aux Modules Supplémentaires Couverts ne seront fournis que *si et seulement si* le Client est hébergé sur la Plate-forme Cloud d'Odoo." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:281 +msgid "Pour les services de correction de Bugs, d'assistance et de migration, le Client peut choisir de collaborer avec un Partenaire Odoo comme point de contact principal, ou directement avec Odoo SA." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:285 +msgid "Si le Client choisit un Partenaire Odoo, Odoo SA sous-traitera les services liés au Modules Supplémentaires Couverts à ce partenaire, qui deviendra le point de contact principal du client. Le Partenaire Odoo peut obtenir de l'assistance de second niveau auprès d'Odoo SA pour le compte du Client, concernant les fonctions standards du Logiciel." msgstr "" #: ../../content/legal/terms/i18n/enterprise_fr.rst:290 +msgid "Si le Client décide de collaborer directement avec Odoo SA, les services liés aux Modules Supplémentaires Couverts ne seront fournis que *si et seulement si* le Client est hébergé sur la Plate-forme Cloud d'Odoo." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:298 msgid "5 Tarifs et Frais" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:295 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:303 msgid "5.1 Tarifs standards" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:297 -msgid "Les tarifs standards pour le contrat d'abonnement à Odoo Enterprise et les Services sont basés sur le nombre d'Utilisateurs et les Apps installées, et précisés par écrit à la conclusion du contrat." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_fr.rst:300 -msgid "Pendant la durée du contrat, si le Client a plus d'Utilisateurs ou d'Apps que spécifié au moment de la conclusion du présent Contrat, le Client accepte de payer un supplément équivalent au tarif en vigueur applicable (au début du Contrat) pour les utilisateurs supplémentaires, pour le reste de la durée." -msgstr "" - #: ../../content/legal/terms/i18n/enterprise_fr.rst:305 -msgid "Par ailleurs, les services concernant les Modules Supplémentaires Couverts sont facturés sur base du nombre de lignes de code dans ces modules. Lorsque le client opte pour l'abonnement de maintenance des Modules Supplémentaires Couverts, le coût mensuel est de 16€ par 100 lignes de code (arrondi à la centaine supérieure), sauf si spécifié par écrit à la conclusion du Contrat. Les lignes de code sont comptées avec la commande ``cloc`` du Logiciel, et comprennent toutes les lignes de texte du code source de ces modules, peu importe le langage de programmation (Python, Javascript, XML, etc.), à l'exclusion des lignes vides, des lignes de commentaires et des fichiers qui ne sont pas chargés à l'installation ou à l'exécution du Logiciel." +msgid "Les tarifs standards pour le contrat d'abonnement à Odoo Enterprise et les Services sont basés sur le nombre d'Utilisateurs et la Formule d'Abonnement utilisés par le Client, et précisés par écrit à la conclusion du contrat." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:314 -msgid "Lorsque le Client demande une migration, pour chaque Module Supplémentaire Couvert qui n'a pas fait l'objet de frais de maintenance pour les 12 derniers mois, Odoo SA peut facturer des frais supplémentaires unique de 16€ par 100 lignes de code, pour chaque mois de maintenance manquant." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:308 +msgid "Pendant la durée du contrat, si le Client a plus d'Utilisateurs ou utilise des fonctionnalités qui requièrent une autre Formule d'Abonnement que celle précisée au moment de la conclusion du présent Contrat, le Client accepte de payer un supplément équivalent au tarif en vigueur applicable (au moment de la divergence par rapport au nombre d'Utilisateurs ou de la Formule d'Abonnement spécifiés) pour les utilisateurs supplémentaires ou la Formule d'Abonnement requise, pour le reste de la Durée." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:322 -msgid "5.2 Tarifs de reconduction" +#: ../../content/legal/terms/i18n/enterprise_fr.rst:315 +msgid "Par ailleurs, les services concernant les Modules Supplémentaires Couverts sont facturés sur base du nombre de lignes de code dans ces modules. Lorsque le client opte pour l'abonnement de maintenance des Modules Supplémentaires Couverts, le coût mensuel est défini par 100 lignes de code (arrondi à la centaine supérieure), tel que spécifié par écrit à la conclusion du Contrat. Les lignes de code sont comptées avec la commande ``cloc`` du Logiciel, et comprennent toutes les lignes de texte du code source de ces modules, peu importe le langage de programmation (Python, Javascript, XML, etc.), à l'exclusion des lignes vides, des lignes de commentaires et des fichiers qui ne sont pas chargés à l'installation ou à l'exécution du Logiciel." msgstr "" #: ../../content/legal/terms/i18n/enterprise_fr.rst:324 -msgid "Lors de la reconduction telle que décrite à la section :ref:`term_fr`, si les tarifs par Utilisateur (à l'exclusion des “Initial User Discounts”) qui ont été appliqués pendant la Durée précédente sont inférieurs aux tarifs par Utilisateur en vigueur les plus récents, les tarifs par Utilisateur augmenteront automatiquement de maximum 7% par reconduction, sans dépasser les tarifs en vigueur les plus récents." +msgid "Lorsque le Client demande une migration, pour chaque Module Supplémentaire Couvert qui n'a pas fait l'objet de frais de maintenance pour les 12 derniers mois, Odoo SA peut facturer des frais supplémentaires uniques, pour chaque mois de maintenance manquant." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:333 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:332 +msgid "5.2 Tarifs de reconduction" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:334 +msgid "Lors de la reconduction telle que décrite à la section :ref:`term_fr`, si les tarifs appliqués pendant la Durée précédente du contrat sont inférieurs aux tarifs en vigueur les plus récents, ces frais augmenteront de maximum 7 %." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:341 msgid "5.3 Taxes et impôts" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:335 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:343 msgid "Tous les frais et tarifs sont indiqués hors taxes, frais et charges fédérales, provinciales, locales ou autres taxes gouvernementales applicables (collectivement, les \"Taxes\"). Le Client est responsable du paiement de toutes les Taxes liées aux achats effectués par le Client en vertu du présent Contrat, sauf lorsque Odoo SA est légalement tenue de payer ou de percevoir les Taxes dont le client est responsable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:344 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:352 msgid "6 Conditions des Services" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:347 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:355 msgid "6.1 Obligations du Client" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:349 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:357 msgid "Le Client accepte de / d':" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:351 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:359 msgid "Payer à Odoo SA les frais applicables pour les Services en vertu du présent Contrat, conformément aux conditions de paiement spécifiées à la souscription du présent Contrat ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:353 -msgid "Aviser immédiatement Odoo SA si le nombre réel d'Utilisateurs ou les Apps installées dépassent les nombres spécifiés à la conclusion du Contrat, et dans ce cas, de régler les frais supplémentaires applicables telles que décrits à la section :ref:`charges_standard_fr`;" +#: ../../content/legal/terms/i18n/enterprise_fr.rst:361 +msgid "Aviser immédiatement Odoo SA si le nombre réel d'Utilisateurs dépasse le nombre spécifié à la conclusion du Contrat, et dans ce cas, de régler les frais supplémentaires applicables telles que décrits à la section :ref:`charges_standard_fr`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:356 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:364 msgid "Prendre toutes les mesures nécessaires pour garantir l'exécution non modifiée de la partie du Logiciel qui vérifie la validité de l'utilisation de Odoo Enterprise Edition, comme décrit à la section :ref:`enterprise_access_fr`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:359 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:367 msgid "Désigner 1 personne de contact représentant le Client pour toute la durée du contrat ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:360 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:368 msgid "Signaler par écrit à Odoo SA avec un préavis de 30 jours en cas de changement de point de contact principal, pour collaborer avec un autre Partenaire Odoo, ou directement avec Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:363 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:371 msgid "Lorsque le Client choisit d'utiliser la Plate-forme Cloud, il accepte aussi de:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:365 -msgid "Prendre toute mesure raisonnable pour garantir la sécurité de ses comptes utilisateur, y compris en choisissant un mot de passe sûr et en ne le partageant avec personne;" +#: ../../content/legal/terms/i18n/enterprise_fr.rst:373 +msgid "Prendre toute mesure raisonnable pour garantir la sécurité de ses comptes utilisateurs, y compris en choisissant un mot de passe sûr et en ne le partageant avec personne;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:367 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:375 msgid "Faire une utilisation raisonnable des Services d'Hébergement, à l'exclusion de toute activité illégale ou abusive, et de respecter strictement les règles indiquées dans la Politique d'Utilisation Acceptable: https://www.odoo.com/acceptable-use." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:371 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:379 msgid "Lorsque le Client choisit l'Auto-Hébergement, il accepte aussi de:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:373 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:381 msgid "Fournir tout accès nécessaire à Odoo SA pour vérifier la validité de l'utilisation d'Odoo Enterprise Edition sur demande (par exemple, si la validation automatique ne fonctionne pas pour le Client) ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:376 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:384 msgid "Prendre toutes les mesures raisonnables pour protéger les fichiers et les bases de données du Client et s'assurer que les données du Client sont en sûreté et sécurisées, en reconnaissant qu'Odoo SA ne peut être tenue responsable de toute perte de données ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:382 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:390 msgid "6.2 Non solicitation ou embauche" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:384 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:392 msgid "Sauf si l'autre partie donne son consentement par écrit, chaque partie, ses sociétés affiliées et ses représentants conviennent de ne pas solliciter ou offrir un emploi à tout employé de l'autre partie qui est impliqué dans l'exécution ou l'utilisation des Services en vertu du présent Contrat, pendant la Durée du Contrat et pendant une période de 12 mois à compter de la date de résiliation ou de l'expiration du présent Contrat. En cas de violation des conditions de la présente section qui conduirait à la démission dudit employé à cette fin, la partie ayant enfreint ces dispositions accepte de payer à l'autre partie un montant forfaitaire de 30 000,00 euros (€) (trente mille euros)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:397 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:405 msgid "6.3 Publicité" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:399 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:407 msgid "Sauf demande contraire par écrit, chaque partie accorde à l'autre partie une licence mondiale libre de droits, non transférable, non exclusive pour reproduire et afficher le nom, les logos et les marques de l'autre partie, dans le seul but de citer l'autre partie en tant que client ou fournisseur, sur les sites Web, dans des communiqués de presse et autres documents de marketing." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:407 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:415 msgid "6.4 Confidentialité" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:418 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:426 msgid "Définition des \"Informations Confidentielles\" :" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:410 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:418 msgid "Désigne toutes les informations divulguées par une partie (la \"Partie Communicante\") à l'autre partie (la \"Partie Bénéficiaire\"), que ce soit oralement ou par écrit, qui sont désignées comme confidentielles ou qui devraient raisonnablement être comprises comme étant confidentielles étant donné la nature des informations et les circonstances de la divulgation. En particulier, toute information liée aux activités, aux affaires, aux produits, aux développements, aux secrets commerciaux, au savoir-faire, au personnel, aux clients et aux fournisseurs de l'une des parties doit être considérée comme confidentielle." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:420 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:428 msgid "Pour toute Information Confidentielle reçue pendant la durée du présent contrat, la Partie Bénéficiaire utilisera le même degré de précaution qu'elle utilise pour protéger la confidentialité de ses propres Informations Confidentielles de même importance. Ce degré de précaution devra correspondre au minimum à une précaution raisonnable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:425 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:433 msgid "La Partie Bénéficiaire peut divulguer les Informations Confidentielles de la Partie Communicante dans la mesure où la loi l'y oblige, à condition que la Partie Bénéficiaire avise au préalable par écrit la Partie Communicante de son obligation de divulgation, dans la mesure permise par la loi." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:433 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:441 msgid "6.5 Protection de données" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:438 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:446 msgid "Définitions" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:436 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:444 msgid "\"Données à Caractère Personnel\", \"Responsable de Traitement\", \"Traitement\" prennent le même sens que dans le Règlement (EU) 2016/679 et la Directive 2002/58/EC, et dans tout règlement ou législation qui les amende ou les remplace (collectivement, la \"Législation sur la Protection des Données\")" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:441 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:449 msgid "Traitement de Données à Caractère Personnel" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:443 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:451 msgid "Les parties conviennent que la base de données du Client peut contenir des Données à Caractère Personnel, pour lesquelles le Client est le Responsable de Traitement. Ces données seront traitées par Odoo SA quand le Client en donnera l'instruction, par son utilisation des Services qui requièrent une base de données (tels que le Service d'Hébergement ou le Service de migration), ou si le Client transfère sa base de données ou une partie de celle-ci à Odoo SA pour toute autre raison relative à l'exécution du présent Contrat." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:450 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:458 msgid "Ce traitement sera exécuté en conformité avec la Législation sur la Protection des Données. En particulier, Odoo SA s'engage à:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:453 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:461 msgid "(a) Ne traiter les Données à Caractère Personnel que quand et comme demandé par le Client, et pour la finalité de l'exécution de l'un des Services du Contrat, à moins que la loi ne l'exige, auquel cas Odoo SA préviendra préalablement le Client, à moins que la loi ne l'interdise;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:456 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:464 msgid "(b) S'assurer que tout le personnel d'Odoo SA autorisé à traiter les Données à Caractère Personnel soit soumis à un devoir de confidentialité ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:458 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:466 msgid "(c) Mettre en oeuvre et maintenir des mesures de sécurité appropriées au niveau technique et organisationnel, afin de protéger les Données à Caractère Personnel de tout traitement non autorisé ou illégal, et de toute perte accidentelle, destruction, dégât, vol, altération ou divulgation ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:462 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:470 msgid "(d) Transmettre promptement au Client toute demande relative à des Données à Caractère Personnel qui aurait été soumise à Odoo SA au sujet de la base de données du Client ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:464 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:472 msgid "(e) Signaler au Client dès la prise de connaissance et la confirmation de tout traitement, accès ou divulgation non autorisés, accidentels ou illégal des Données à Caractère Personnel ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:466 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:474 msgid "(f) Signaler au Client lorsque ses instructions de traitement vont à l'encontre de la Législation sur la Protection des Données, d'après Odoo SA ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:468 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:476 msgid "(g) Fournir au Client toute information nécessaire à la démonstration de la conformité avec la Législation sur la Protection des Données, autoriser et contribuer de façon raisonnable à des audits, y compris des inspections, conduits ou mandatés par le Client dans ce but;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:471 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:479 msgid "(h) Supprimer définitivement tout copie de la base de données du Client en possession d'Odoo SA, ou retourner ces données, au choix du Client, lors de la résiliation de ce Contrat, en respect des délais indiqués dans la `Politique de Protection des Données `_ d'Odoo SA ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:476 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:484 msgid "Concernant les points (d) à (f), le Client s'engage à fournir à Odoo SA des informations de contact valables, tel que nécessaire pour toute notification auprès du responsable de protection des données du Client." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:481 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:489 msgid "Sous-traitants" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:483 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:491 msgid "Le Client convient et accepte que pour fournir les Services, Odoo SA peut faire appel à des prestataires de service tiers (Sous-traitants) pour traiter les Données à Caractère Personnel. Odoo SA s'engage à n'utiliser de tels Sous-traitants qu'en conformité avec la Législation sur la Protection des Données. Cet usage sera couvert par un contrat entre Odoo SA et le Sous-traitant qui offrira toutes les garanties nécessaires à cet effet. La Politique de Protection des Données d'Odoo SA, publiée à l'adresse https://www.odoo.com/privacy fournit des informations actualisées sur les noms et les finalités des Sous-traitants utilisés par Odoo SA pour l'exécution des Services." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:496 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:504 msgid "6.6 Résiliation" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:498 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:506 msgid "Dans le cas où l'une des parties ne remplit pas ses obligations découlant du présent contrat, et si une telle violation n’est pas résolue dans les 30 jours civils à compter de la notification écrite de cette violation, le présent contrat peut être résilié immédiatement par la partie qui n'a pas commis la violation." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:504 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:512 msgid "En outre, Odoo SA peut résilier le contrat immédiatement dans le cas où le Client ne paie pas les frais applicables pour les services dans les 21 jours suivant la date d'échéance indiquée sur la facture correspondante, après minimum 3 rappels." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:511 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:519 msgid "Durée de l'applicabilité des dispositions:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:509 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:517 msgid "Les sections \":ref:`confidentiality_fr`\", “:ref:`disclaimers_fr`\", “:ref:`liability_fr`\", et “:ref:`general_provisions_fr`\" survivront la résiliation ou l'expiration du présent contrat." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:516 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:524 msgid "7 Limitations de garantie et de responsabilité" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:523 -msgid "Odoo SA détient le copyright ou un équivalent [#cla_fr1]_ sur 100% du code du Logiciel, et confirme que toutes les librairies logicielles nécessaires au fonctionnement du Logiciel sont disponibles sous une licence compatible avec la licence du Logiciel." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_fr.rst:527 -msgid "Pendant la durée du présent contrat, Odoo SA s'engage à déployer les efforts raisonnables sur le plan commercial pour exécuter les Services conformément aux normes du secteur généralement acceptées à condition que :" +#: ../../content/legal/terms/i18n/enterprise_fr.rst:529 +msgid "7.1 Garantie" msgstr "" #: ../../content/legal/terms/i18n/enterprise_fr.rst:531 +msgid "Odoo SA détient le copyright ou un équivalent [#cla_fr1]_ sur 100% du code du Logiciel, et confirme que toutes les librairies logicielles nécessaires au fonctionnement du Logiciel sont disponibles sous une licence compatible avec la licence du Logiciel." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:535 +msgid "Pendant la durée du présent contrat, Odoo SA s'engage à déployer les efforts raisonnables sur le plan commercial pour exécuter les Services conformément aux normes du secteur généralement acceptées à condition que :" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_fr.rst:539 msgid "Les systèmes informatiques du Client soient en bon état de fonctionnement et, pour l'Auto-Hébergement, que le Logiciel soit installé selon les bonnes pratiques en vigueur;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:533 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:541 msgid "Le Client fournisse les informations adéquates nécessaires au dépannage et, pour l'Auto-Hébergement, tout accès utile, de telle sorte qu'Odoo SA puisse identifier, reproduire et gérer les problèmes ;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:536 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:544 msgid "Tous les montants dus à Odoo SA, qui sont échus, aient été réglés." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:538 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:546 msgid "La reprise de l'exécution des Services par Odoo SA sans frais supplémentaires constitue la seule et unique réparation pour le Client et la seule obligation d'Odoo SA pour tout manquement à cette garantie." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:542 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:550 msgid "Les contributions externes sont couvertes par un `Copyright License Agreement `_ fournissant une licence de copyright et de brevet permanente, gratuite et irrévocable à Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:549 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:557 msgid "7.2 Limitation de garantie" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:551 -msgid "Mis à part les dispositions expresses du présent Contrat, aucune des parties ne donne de garantie d'aucune sorte, expresse, implicite ou autre, et chaque partie décline expressément toutes garanties implicites, y compris toute garantie implicite de qualité marchande, d'adéquation à un usage particulier ou de non- contrefaçon, dans les limites autorisées par la loi en vigueur." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:559 +msgid "Mis à part les dispositions expresses du présent Contrat, aucune des parties ne donne de garantie d'aucune sorte, expresse, implicite ou autre, et chaque partie décline expressément toutes garanties implicites, y compris toute garantie implicite de qualité marchande, d'adéquation à un usage particulier ou de non-contrefaçon, dans les limites autorisées par la loi en vigueur." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:557 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:565 msgid "Odoo SA ne garantit pas que le Logiciel soit conforme à toute loi ou réglementation locale ou internationale." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:564 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:572 msgid "7.3 Limitation de responsabilité" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:566 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:574 msgid "Dans la limite autorisée par la loi, la responsabilité globale de chaque partie, ainsi que de ses filiales, découlant ou liée au présent Contrat ne dépassera pas 50% du montant total réglé par le Client en vertu du présent Contrat au cours des 12 mois précédant la date de l'événement donnant lieu à une telle réclamation. Des réclamations multiples n'augmenteront pas cette limite." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:571 -msgid "Les parties et leurs filiales ne pourront en aucun cas être tenues responsables des dommages indirects, spéciaux, accessoires ou consécutifs de quelque nature que ce soit, y compris, mais sans s'y limiter, la perte de revenus, perte de profits, perte d’économies, perte commerciale ou toute autre perte financière, les coûts relatifs à l'arrêt ou au retard, la perte ou altération des données, découlant ou en relation avec le présent Contrat, quelle que soit la forme de l'action, qu'elle soit fondée sur une obligation contractuelle, délictuelle ou fondée sur toute autre règle de droit ou d'équité, même si la partie ou ses filiales ont été informées du risque de tels dommages, ou si le recours proposé par la partie ou ses filiales n'atteint pas son but essentiel." +#: ../../content/legal/terms/i18n/enterprise_fr.rst:579 +msgid "Les parties et leurs filiales ne pourront en aucun cas être tenues responsables des dommages indirects, spéciaux, punitifs, accessoires ou consécutifs de quelque nature que ce soit, y compris, mais sans s'y limiter, la perte de revenus, perte de profits, perte d’économies, perte commerciale ou toute autre perte financière, les coûts relatifs à l'arrêt ou au retard, la perte ou altération des données, découlant ou en relation avec le présent Contrat, quelle que soit la forme de l'action, qu'elle soit fondée sur une obligation contractuelle, délictuelle ou autre, même si la partie ou ses filiales ont été informées du risque de tels dommages, ou si le recours proposé par la partie ou ses filiales n'atteint pas son but essentiel." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:586 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:593 msgid "Aucune des parties ne sera tenue pour responsable envers l'autre partie de tout retard ou manquement d'exécution en vertu du présent Contrat, si ce manquement ou retard trouve sa cause dans un cas de *force majeure*, comme une règlementation gouvernementale, un incendie, une grève, une guerre, une inondation, un accident, une épidémie, un embargo, la saisie d'une usine ou d'un produit dans son intégralité ou en partie par un gouvernement ou une autorité publique, ou toute (s) autre (s) cause (s), qu’elle (s) soit (soient) de nature similaire ou différente, pour autant que cette cause soit hors du contrôle raisonnable de la partie concernée, et tant qu'une telle cause existe." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:598 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:605 msgid "8 Dispositions générales" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:603 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:610 msgid "8.1 Droit applicable" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:605 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:612 msgid "Le présent contrat et les commandes passées par le client sont exclusivement régis par le droit belge. Tout différend relatif au présent contrat ou à une commande passée par le Client relève de la compétence exclusive du tribunal de l’entreprise de Nivelles." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:612 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:619 msgid "8.2 Divisibilité" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:614 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:621 msgid "Dans le cas où une ou plusieurs des dispositions du présent contrat ou toute autre application de celles-ci se trouvent non valables, illégales ou non exécutoires, la validité, la légalité et le caractère exécutoire des autres dispositions du présent contrat et toute application de celles-ci ne doivent en aucun cas en être affectés ou compromis. Les parties s'engagent à remplacer toute disposition non valable, illégale ou non exécutoire du présent contrat par une disposition valable ayant les mêmes effets et objectifs." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:624 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:631 msgid "9 Appendice A: Odoo Enterprise Edition License" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:626 -#: ../../content/legal/terms/i18n/partnership_fr.rst:386 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:633 +#: ../../content/legal/terms/i18n/partnership_fr.rst:404 msgid "Odoo Enterprise Edition est publié sous la licence Odoo Enterprise Edition License v1.0, définie ci-dessous." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:630 -#: ../../content/legal/terms/i18n/partnership_fr.rst:390 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:637 +#: ../../content/legal/terms/i18n/partnership_fr.rst:408 msgid "Ceci est une traduction en français de la licence “Odoo Enterprise Edition License”. Cette traduction est fournie dans l’espoir qu’elle facilitera sa compréhension, mais elle n'a aucune valeur légale. La seule référence officielle des termes de la licence “Odoo Enterprise Edition License” est la :ref:`version originale `." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:636 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:643 msgid "This is a french translation of the \"Odoo Enterprise Edition License”. This translation is provided in the hope that it will facilitate understanding, but it has no legal value. The only official reference of the terms of the “Odoo Enterprise Edition License” is the :ref:`original english version `." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:653 -#: ../../content/legal/terms/i18n/partnership_fr.rst:407 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:660 +#: ../../content/legal/terms/i18n/partnership_fr.rst:425 msgid "Ce logiciel et les fichiers associés (le \"Logiciel\") ne peuvent être utilisés (c'est-à-dire exécutés, modifiés, ou exécutés avec des modifications) qu'avec un contrat Odoo Enterprise Subscription en ordre de validité, et pour le nombre d'utilisateurs prévus dans ce contrat." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:658 -#: ../../content/legal/terms/i18n/partnership_fr.rst:412 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:665 +#: ../../content/legal/terms/i18n/partnership_fr.rst:430 msgid "Un contrat de Partnariat avec Odoo S.A. en ordre de validité donne les mêmes permissions que ci-dessus, mais uniquement pour un usage restreint à un environnement de test ou de développement." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:662 -#: ../../content/legal/terms/i18n/partnership_fr.rst:416 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:669 +#: ../../content/legal/terms/i18n/partnership_fr.rst:434 msgid "Vous êtes autorisé à développer des modules Odoo basés sur le Logiciel et à les distribuer sous la license de votre choix, pour autant que cette licence soit compatible avec les conditions de la licence Odoo Enterprise Edition Licence (Par exemple: LGPL, MIT ou d'autres licenses propriétaires similaires à celle-ci)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:667 -#: ../../content/legal/terms/i18n/partnership_fr.rst:421 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:674 +#: ../../content/legal/terms/i18n/partnership_fr.rst:439 msgid "Vous êtes autorisé à utiliser des modules Odoo publiés sous n'importe quelle licence, pour autant que leur licence soit compatible avec les conditions de la licence Odoo Enterprise Edition License (Notamment tous les modules publiés sur l'Odoo Apps Store sur odoo.com/apps)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:672 -#: ../../content/legal/terms/i18n/partnership_fr.rst:426 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:679 +#: ../../content/legal/terms/i18n/partnership_fr.rst:444 msgid "Il est interdit de publier, distribuer, accorder des sous-licences, ou vendre tout copie du Logiciel ou toute copie modifiée du Logiciel." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:675 -#: ../../content/legal/terms/i18n/partnership_fr.rst:429 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:682 +#: ../../content/legal/terms/i18n/partnership_fr.rst:447 msgid "Toute copie du Logiciel ou d'une partie substantielle de celui-ci doit inclure l'avis de droit d'auteur original ainsi que le texte de la présente licence." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:678 -#: ../../content/legal/terms/i18n/partnership_fr.rst:432 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:685 +#: ../../content/legal/terms/i18n/partnership_fr.rst:450 msgid "LE LOGICIEL EST FOURNI \"EN L'ETAT\", SANS AUCUNE GARANTIE DE QUELQUE NATURE QUE CE SOIT, EXPRESSE OU IMPLICITE, Y COMPRIS, MAIS SANS Y ETRE LIMITE, LES GARANTIES IMPLICITES DE COMMERCIABILITE, DE CONFORMITE A UNE UTILISATION PARTICULIERE, OU DE NON INFRACTION AUX DROITS D'UN TIERS." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_fr.rst:683 -#: ../../content/legal/terms/i18n/partnership_fr.rst:437 +#: ../../content/legal/terms/i18n/enterprise_fr.rst:690 +#: ../../content/legal/terms/i18n/partnership_fr.rst:455 msgid "EN AUCUN CAS LES AUTEURS OU TITULAIRES DE DROITS D'AUTEUR NE POURRONT ETRE TENUS POUR RESPONSABLE A VOTRE EGARD DE RECLAMATIONS, DOMMAGES OU AUTRES RESPONSABILITES, EN VERTU D'UN CONTRAT, DÉLIT OU AUTREMENT, RELATIVEMENT AU LOGICIEL, A L'UTILISATION DU LOGICIEL, OU A TOUTE AUTRE MANIPULATION RELATIVE AU LOGICIEL." msgstr "" @@ -2569,1009 +2693,1774 @@ msgstr "" msgid "Odoo Enterprise Subscription Agreement (NL)" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:9 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:10 +msgid "`Download PDF `_" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:12 msgid "Dit is een Nederlandse vertaling van de \"Odoo Enterprise Subscription Agreement\". Deze vertaling wordt verstrekt in de hoop dat deze het begrip zal vergemakkelijken, maar heeft geen juridische waarde. De enige officiële referentie van de algemene voorwaarden van de \"Odoo Enterprise Subscription Agreement\" is :ref:`de originele Engelse versie `" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:16 -msgid "DEZE VERSIE IS NIET ACTUEEL. VOOR DE NIEUWSTE VERSIE ZIE DE :ref:`ORIGINELE ENGELSE VERSIE `" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:33 +msgid "Door u op de Odoo Enterprise-diensten (de “Diensten”) te abonneren die door Odoo NV en haar dochterondernemingen (gezamenlijk “Odoo NV”) worden verleend met betrekking tot de Odoo Enterprise Edition of de Odoo Community Edition (de “Software”) gehost op de Cloudplatforms van Odoo NV (het \"Cloudplatform\") of op locatie (\"Self-Hosting\"), gaat u (de \"Klant\") ermee akkoord om gebonden te zijn door de volgende algemene voorwaarden (de “Overeenkomst”)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:26 -msgid "Door u op de Odoo Enterprise-diensten (de “Diensten”) te abonneren die door Odoo NV/SA en zijn dochterondernemingen (gezamenlijk “Odoo NV”) worden verleend met betrekking tot de Odoo Enterprise Edition of de Odoo Community Edition (de “Software”), gaat u (de \"Klant\") ermee akkoord om gebonden te zijn door de volgende algemene voorwaarden (de “Overeenkomst”)." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:35 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:43 msgid "1 Looptijd van de Overeenkomst" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:37 -msgid "De duur van deze Overeenkomst (de \"Looptijd\") zal minimaal één jaar zijn en, zoals schriftelijk verduidelijkt bij de ondertekening van deze Overeenkomst, ingaan op de datum van de ondertekening. De duur wordt automatisch verlengd voor dezelfde Looptijd, tenzij een van beide partijen minstens 30 dagen voor het einde van de Looptijd de Overeenkomst per aangetekend schrijven aan de andere partij opzegt." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:47 -msgid "2 Definities" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:45 +msgid "De duur van deze Overeenkomst (de \"Looptijd\") wordt schriftelijk bepaald bij het afsluiten van deze Overeenkomst en gaat in op de datum van de afsluiting. De duur wordt automatisch verlengd met dezelfde Looptijd, tenzij een van beide partijen de andere partij minstens 30 dagen voor het einde van de Looptijd schriftelijk in kennis stelt van de beëindiging." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:54 +msgid "2 Definities" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:61 msgid "Gebruiker" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:50 -msgid "Elke actieve gebruikersaccount met toegang tot de Software in de creatie- en/of bewerkingsmodus. Gedeactiveerde gebruikersaccounts en accounts die worden gebruikt door externe mensen (of systemen) die slechts beperkte toegang hebben tot de Software via de portalfaciliteiten (ook wel \"Portalgebruikers\" genoemd) tellen niet mee als Gebruikers." -msgstr "" - #: ../../content/legal/terms/i18n/enterprise_nl.rst:57 -msgid "Een \"App\" is een gespecialiseerde groep functies die beschikbaar is voor installatie in de Software en wordt vermeld in de publieke sectie “Prijzen” van de website van Odoo NV bij de ondertekening van deze Overeenkomst." +msgid "Elke actieve gebruikersaccount met toegang tot de Software in de creatie- en/of bewerkingsmodus. Gedeactiveerde gebruikersaccounts en accounts die worden gebruikt door externe personen (of systemen) die slechts beperkte toegang hebben tot de Software via de portaalfaciliteiten (\"Portaalgebruikers\") tellen niet mee als Gebruikers." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:63 -msgid "Elke storing van de Software die resulteert in een volledige stilstand," +#: ../../content/legal/terms/i18n/enterprise_nl.rst:64 +msgid "Een \"App\" is een gespecialiseerde groep functies die beschikbaar is voor installatie in de Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:65 -msgid "foutopsporing of beveiligingsinbreuk en die niet rechtstreeks door een gebrekkige installatie of configuratie wordt veroorzaakt, wordt als een Bug beschouwd. Niet-naleving van specificaties of vereisten zal als een Bug worden beschouwd naar goeddunken van Odoo NV (doorgaans wanneer de Software niet de resultaten of prestaties levert die hij moet leveren, of wanneer een landspecifieke functie niet langer aan de wettelijke boekhoudkundige vereisten voldoet)." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:82 -msgid "Gedekte Versies" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:68 +msgid "Een Odoo Partner is een derde bedrijf of persoon, gekozen door de Klant, die met de Klant samenwerkt voor zijn Odoo-gerelateerde diensten. De Klant kan op elk moment beslissen om met een andere Odoo Partner of rechtstreeks met Odoo NV samen te werken (mits voorafgaande kennisgeving)." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:74 -msgid "Alle Diensten die onder deze Overeenkomst vallen, zijn alleen van toepassing op de Gedekte Versies van de Software, waaronder de 3 (drie) meest recent uitgebrachte hoofdversies." +msgid "Een extra module is een map met broncode bestanden of een reeks op Python gebaseerde aanpassingen die in een database zijn gemaakt (bijv. met Odoo Studio), die functies toevoegt of het standaardgedrag van de Software wijzigt. Het kan zijn ontwikkeld door een Klant, door Odoo NV, door een Odoo Partner namens de klant, of door derden." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:78 -msgid "Om onder de onderhavige Overeenkomst te vallen, moet de meest recente Gedekte Versie op de installaties van de Klant draaien op het moment van de ondertekening van deze Overeenkomst. Wanneer dit niet het geval is, zijn aanvullende kosten van toepassing, zoals beschreven in :ref:`charges_standard_nl`." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:83 +msgid "Ondersteunde Extra Module" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:87 -msgid "3 Toegang tot de Odoo Enterprise Edition" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:81 +msgid "Een Ondersteunde Extra Module is een extra module waarvoor de Klant ervoor kiest een onderhoudsbijdrage te betalen om van ondersteunings-, upgrade- en bugfixingdiensten te genieten." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:89 -msgid "Voor de duur van deze Overeenkomst geeft Odoo NV de Klant een niet-exclusieve, niet-overdraagbare licentie om de Odoo Enterprise Edition-software te gebruiken (uitvoeren, wijzigen, uitvoeren na wijziging) onder de voorwaarden uiteengezet in :ref:`appendix_a_nl`." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:86 +msgid "Wordt beschouwd als een Bug, elke storing van de Software of een Ondersteunde Extra Module die resulteert in een volledige stilstand, foutopsporing of beveiligingsinbreuk en die niet rechtstreeks wordt veroorzaakt voor een gebrekkige installatie of configuratie. De niet-naleving van specificaties of vereisten zal als een Bug worden beschouwd naar goeddunken van Odoo NV (doorgaans wanneer de Software niet de resultaten of prestaties levert die hij moet leveren of wanneer een landspecifieke functie niet langer aan de wettelijke boekhoudkundige vereisten voldoet)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:94 -msgid "De Klant gaat ermee akkoord alle nodige maatregelen te nemen om de ongewijzigde uitvoering te waarborgen van het deel van de Software dat de geldigheid van het gebruik van de Odoo Enterprise Edition controleert en statistieken verzamelt voor dat doel, met inbegrip van maar niet beperkt tot het uitvoeren van een extensie, het aantal Gebruikers en geïnstalleerde Apps." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:98 +msgid "Ondersteunde Versies" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:100 -msgid "Odoo NV verbindt zich ertoe om individuele of vermelde cijfers niet bekend te maken aan derden zonder de toestemming van de Klant, en om alle verzamelde gegevens te behandelen in overeenstemming met zijn officiële Privacybeleid, gepubliceerd op https://www.odoo.com/privacy." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:96 +msgid "Behalve anderluidende bepaling zijn de Diensten die op grond van deze Overeenkomst worden verleend, uitsluitend van toepassing op de Ondersteunde Versies van de Software, waaronder de 3 (drie) laatst uitgebrachte hoofdversies." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:105 -msgid "Bij het aflopen of beëindigen van deze Overeenkomst wordt deze licentie onmiddellijk ingetrokken en gaat de Klant ermee akkoord om de Odoo Enterprise Edition-software niet meer te gebruiken." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:103 +msgid "Abonnementsplan" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:109 -msgid "Indien de Klant de voorwaarden van deze sectie schendt, gaat de Klant ermee akkoord om Odoo NV een extra vergoeding te betalen gelijk aan 300% van de geldende catalogusprijs voor het werkelijke aantal Gebruikers." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:101 +msgid "Een abonnementsplan bepaalt een reeks Apps, functies en hostingoplossingen die onder deze Overeenkomst vallen en wordt schriftelijk vastgelegd bij het afsluiten van deze Overeenkomst." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:108 +msgid "3 Toegang tot de Software" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:110 +msgid "De Klant kan de op het Cloudplatform gehoste Software gebruiken of kiezen voor de Self-Hosting optie. Het Cloudplatform wordt gehost en volledig beheerd door Odoo NV, en is op afstand toegankelijk voor de Klant. Met de Self-Hosting optie host de Klant de Software op een computersysteem naar keuze, die niet onder de controle staat van Odoo NV." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:116 -msgid "4 Inbegrepen diensten" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:119 -msgid "4.1 Bugfixingdienst" +msgid "Voor de duur van deze Overeenkomst verstrekt Odoo NV aan de Klant een niet-exclusieve, niet-overdraagbare licentie om de Odoo Enterprise Edition Software te gebruiken (uitvoeren, wijzigen, uitvoeren na wijziging) onder de voorwaarden uiteengezet in :ref:`appendix_a_nl`." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:121 -msgid "Voor de duur van deze Overeenkomst verbindt Odoo NV zich ertoe alle redelijke inspanningen aan te wenden om elke Bug van de Software die via het juiste kanaal (gewoonlijk het e-mailadres of het websiteformulier van de servicedesk van Odoo NV) door de Klant wordt ingediend, te verhelpen en dergelijke indiening van de Klant binnen 2 werkdagen af te handelen." +msgid "De Klant gaat ermee akkoord alle nodige maatregelen te nemen om de ongewijzigde uitvoering te waarborgen van het deel van de Software dat de geldigheid van het gebruik van de Odoo Enterprise Edition controleert en dat statistieken verzamelt voor dat doel, met inbegrip van, maar niet beperkt tot het uitvoeren van de Software, het aantal Gebruikers, de geïnstalleerde Apps en het aantal coderegels van de Ondersteunde Extra Modules." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:127 -msgid "De Klant begrijpt dat Bugs die worden veroorzaakt door een wijziging of uitbreiding die niet deel uitmaakt van de officiële Software niet onder deze dienst valt." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:128 +msgid "Odoo NV verbindt zich ertoe om individuele of persoonlijke cijfers niet bekend te maken aan derden zonder de toestemming van de Klant en om alle verzamelde gegevens te behandelen in overeenstemming met haar officiële Privacybeleid, gepubliceerd op https://www.odoo.com/privacy." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:131 -msgid "Zodra de Bug verholpen is, zal een passende oplossing aan de Klant worden meegedeeld. Indien de Bug reeds verholpen is in een recentere herziening van de Gedekte Versie van de Software die door de Klant wordt gebruikt, stemt de Klant ermee in om zijn systemen bij te werken naar die herziening om de correctie te verkrijgen. Er zal niet aan de Klant worden gevraagd om naar een recentere Gedekte Versie van de Software te upgraden als oplossing voor een Bug." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:133 +msgid "Bij het aflopen of beëindigen van deze Overeenkomst wordt deze licentie onmiddellijk ingetrokken en gaat de Klant ermee akkoord om de Odoo Enterprise Edition Software en het Cloudplatform niet meer te gebruiken." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:138 -msgid "Wanneer een Bug verholpen is in een Gedekte Versie verbindt Odoo NV zich ertoe om de Bug in alle recentere Gedekte Versies van de software te verhelpen." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:137 +msgid "Indien de Klant de voorwaarden van deze sectie schendt, gaat de Klant ermee akkoord om aan Odoo NV een extra vergoeding te betalen gelijk aan 300% van het toepasselijke tarief voor het werkelijke aantal Gebruikers." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:141 -msgid "Beide partijen erkennen dat, zoals gespecificeerd in de licentie van de Software en in de sectie :ref:`liability_nl` van deze Overeenkomst, Odoo NV niet aansprakelijk kan worden gesteld voor Bugs in de Software." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:147 -msgid "4.2 Beveiligingswaarschuwingendienst" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:144 +msgid "4 Diensten" msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:149 -msgid "Voor de duur van deze Overeenkomst verbindt Odoo NV zich ertoe om een “Beveiligingswaarschuwing” naar de Klant te sturen voor elke Bug in de beveiliging die wordt ontdekt in de Gedekte Versies van de Software, ten minste 2 weken voordat de Beveiligingswaarschuwing openbaar wordt gemaakt, tenzij de Bug reeds openbaar is gemaakt door een derde partij. Beveiligingswaarschuwingen bevatten een volledige beschrijving van de Bug, de oorzaak ervan, de mogelijke gevolgen ervan voor de systemen van de Klant en de bijbehorende oplossing voor elke Gedekte Versie." +msgid "4.1 Bugfixingdienst" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:151 +msgid "Voor de duur van deze Overeenkomst verbindt Odoo NV zich ertoe alle redelijke inspanningen te leveren om elke Bug van de Software en de Ondersteunde Extra Modules die door de klant via het juiste kanaal (doorgaans het websiteformulier of de telefoonnummers vermeld op https://odoo.com/help of, in geval van een samenwerking met een Odoo Partner, het door de partner verstrekte kanaal) te verhelpen en binnen de 2 werkdagen de behandeling van dergelijke door de Klant ingediende klachten aan te vatten." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:158 -msgid "De Klant begrijpt dat de Bug en de informatie in het Beveiligingswaarschuwing als Vertrouwelijke Informatie moeten worden behandeld, zoals beschreven in de sectie :ref:`confidentiality_nl`, gedurende de embargoperiode die voorafgaat aan de openbare bekendmaking." +msgid "Zodra de Bug verholpen is, zal een passende oplossing aan de Klant worden meegedeeld. Indien de Klant een Ondersteunde Versie gebruikt, zal hem niet worden gevraagd te upgraden naar een recentere Ondersteunde Versie van de Software als oplossing voor een Bug." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:163 +msgid "Wanneer een Bug verholpen is in een Ondersteunde Versie verbindt Odoo NV zich ertoe om de Bug in alle recentere Ondersteunde Versies van de Software te verhelpen." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:166 +msgid "Beide partijen erkennen dat, zoals gespecificeerd in de licentie van de Software en in de sectie :ref:`liability_nl` van deze Overeenkomst, Odoo NV niet aansprakelijk kan worden gesteld voor Bugs in de Software of in de Ondersteunde Extra Modules." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:172 +msgid "4.2 Veiligheidsupdatedienst" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:179 +msgid "Voor de duur van deze Overeenkomst verbingt Odoo NV zich ertoe een \"Veiligheidsadvies\" naar de Klant te sturen voor elke beveiligingsfout die wordt ontdekt in de Ondersteunde Versies van de Software (met uitzondering van de Extra Modules), ten minste 2 weken voordat het Veiligheidsadvies openbaar wordt gemaakt, tenzij de Bug reeds openbaar is gemaakt door een derde partij. Veiligheidsadviezen bevatten een volledige beschrijving van de Bug, de oorzaak ervan, de mogelijke gevolgen ervan voor de systemen van de Klant en de bijbehorende oplossing voor elke Ondersteunde Versie." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:187 +msgid "De Klant begrijpt dat de Bug en de informatie in het Veiligheidsadvies gedurende de embargoperiode die voorafgaat aan de bekendmaking moeten worden behandeld als Vertrouwelijke Informatie zoals beschreven in :ref:`confidentiality_nl`." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:195 +msgid "Cloudplatform" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:197 +msgid "Odoo NV verbindt zich ertoe om de beveiligingsoplossingen voor elke beveiligingsbug die wordt ontdekt in een versie van de Software die op het Cloudplatform wordt gehost, toe te passen op alle systemen onder zijn controle, zodra de oplossing beschikbaar is, zonder dat daarvoor enige handmatige actie van de Klant nodig is." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:205 msgid "4.3 Upgradediensten" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:171 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:210 msgid "Upgradedienst voor de Software" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:173 -msgid "Gedurende de looptijd van deze Overeenkomst kan de Klant via het juiste kanaal (doorgaans de upgradedienstwebsite van Odoo NV) upgradeaanvragen indienen om een database van de Software van een Gedekte Versie van de Software om te zetten naar een meer recente Gedekte Versie (de \"Doelversie\")." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:178 -msgid "Upgradeaanvragen moeten een volledige reservekopie van de database van de Klant en de bijbehorende gegevens omvatten (doorgaans verkregen via het Back-upmenu van de Software). Waar nodig met het oog om redenen van gegevensbeveiliging of regelgeving bevat de Upgradedienst een optionele tool om identificeerbare gegevens in een database te anonimiseren voordat de upgradeaanvraag wordt ingediend, evenals een tool om de geanonimiseerde gegevens na de upgrade te herstellen." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:186 -msgid "Deze dienst wordt verleend via een geautomatiseerd platform om de Klant in staat te stellen zonder toezicht te upgraden zodra een eerdere versie van de database van de Klant met succes werd geüpgraded voor een Gedekte Versie. De Klant kan opeenvolgende upgradeaanvragen voor een database indienen en gaat ermee akkoord om ten minste 1 upgradeaanvraag voor testdoeleinden in te dienen voordat hij de definitie upgradeaanvraag indient." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:193 -msgid "De Upgradedienst is beperkt tot de technische conversie en aanpassing van de database van de Klant om deze compatibel te maken met de Doelversie en de correctie van elke Bug die rechtstreeks wordt veroorzaakt door de upgradebewerking en die normaal niet voorkomt in de Doelversie." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:198 -msgid "Het is de exclusieve verantwoordelijkheid van de Klant om de geüpgradede database te controleren en te valideren teneinde Bugs te detecteren, om de impact van wijzigingen en nieuwe functies te analyseren die in de Doelversie zijn geïmplementeerd, om eventuele uitbreidingen van derden van de Software die vóór de upgrade in de database waren geïnstalleerd, om te zetten en aan te passen (behalve indien van toepassing zoals voorzien in sectie :ref:`upgrade_extra_nl`). De Klant kan meerdere upgradeaanvragen voor een database indienen totdat een aanvaardbaar resultaat wordt bereikt." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:210 -msgid "Upgradedienst voor extensies van derden" -msgstr "" - #: ../../content/legal/terms/i18n/enterprise_nl.rst:212 -msgid "Gedurende de duur van deze Overeenkomst kan de Klant naast de gewone Upgradediensten optionele upgradediensten voor uitbreidingsmodules van derden van de Software aanvragen. Deze optionele dienst is onderworpen aan extra kosten (zoals beschreven in :ref:`charges_nl`) en omvat de technische aanpassing van de modules van derden die geïnstalleerd zijn in de database van de Klant, en van de bijbehorende gegevens, om compatibel te zijn met de Doelversie. De Klant zal samen met de geüpgradede database een geüpgradede versie van alle geïnstalleerde modules van derden ontvangen." +msgid "Voor de duur van deze Overeenkomst kan de Klant via het juiste kanaal (doorgaans de upgradedienstwebsite van Odoo NV) upgradeaanvragen indienen om een database van eender welke Versie van de Software om te zetten naar een meer recente Ondersteunde Versie (de \"Doelversie\")." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:224 -msgid "5 Kosten en vergoedingen" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:217 +msgid "Voor het Cloudplatform worden upgradeaanvragen rechtstreeks via het controlpaneel van het Cloudplatform ingediend en vereisen ze geen gegevensupload. In geval van Self-Hosting moeten upgradeaanvragen een kopie van de database van de Klant en de bijbehorende gegevens bevatten (doorgaans verkregen via het Back-up menu van de Softare)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:229 -msgid "5.1 Standaardkosten" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:223 +msgid "Deze dienst wordt verleend via een geautomatiseerd platform om de Klant in staat te stellen zonder toezicht te upgraden zodra een eerdere versie van de database van de Klant met succes werd geüpgraded voor een bepaalde Ondersteunde Versie." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:231 -msgid "De standaardkosten voor het Odoo Enterprise-abonnement, de Bugfixingdienst, de Beveiligingswaarschuwingendienst en de Upgradedienst zijn gebaseerd op het aantal Gebruikers, de geïnstalleerde Apps, de Softwareversie die door de Klant wordt gebruikt en schriftelijk wordt gespecificeerd bij de ondertekening van de Overeenkomst." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:227 +msgid "De Upgradedienst is beperkt tot de technische conversie en aanpassing van de database van de Klant om deze compatibel te maken met de Doelversie, de correctie van elke Bug die rechtstreeks wordt veroorzaakt door de upgradebewerking en die normaal niet voorkomt in de Doelversie en de conversie van de broncode en gegevens van de Ondersteunde Extra Modules voor de Doelversie." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:237 -msgid "Wanneer de Klant tijdens de Looptijd meer Gebruikers of meer geïnstalleerde Apps heeft dan gespecificeerd op het moment van de ondertekening van deze Overeenkomst, gaat de Klant ermee akkoord om een extra vergoeding te betalen gelijk aan de toepasselijke catalogusprijs (aan het begin van de Looptijd) voor de bijkomende Gebruikers of Apps, voor de rest van de Looptijd." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:233 +msgid "Het is de exclusieve verantwoordelijkheid van de Klant om de geüpgradede database te controleren en te valideren teneinde Bugs te detecteren, om de impact van wijzigingen en nieuwe functies te analyseren die in de Doelversie zijn geïmplementeerd, om eventuele uitbreidingen van derden van de Software die vóór de upgrade in de database waren geïnstalleerd om te zetten en aan te passen (bijv. niet-ondersteunde extra modules). De Klant kan meerdere upgradeaanvragen voor een database indienen totdat een aanvaardbaar resultaat wordt bereikt." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:243 -msgid "Indien de Klant op het moment van de ondertekening van deze Overeenkomst een Gedekte Versie gebruikt die niet de meest recente is, kunnen de standaardkosten naar eigen goeddunken van Odoo NV met 50% worden verhoogd voor de duur van de eerste Looptijd om de extra onderhoudskosten te dekken." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:245 +msgid "4.4 Cloudhostingdiensten" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:247 +msgid "Voor de duur van deze Overeenkomst, indien de Klant ervoor kiest het Cloudplatform te gebruiken, verbindt Odoo SA zich ertoe ten minste de volgende diensten aan te bieden:" msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:251 -msgid "5.2 Verlengingskosten" +msgid "Keuze uit meerdere hostingregio's (minimaal 3: Europa, Amerika, Azië/Pacific)" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:252 +msgid "Hosting in Tier-III of gelijkwaardige datacenters, met 99,9 % netwerk-uptime" msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:253 -msgid "Indien, bij verlenging zoals beschreven in de sectie :ref:`term_nl`, de kosten gedurende de vorige Looptijd lager zijn dan de meest actuele geldende catalogusprijs, zullen de kosten met maximaal 7% stijgen." +msgid "Graad A SSL (HTTPS) versleuteling van communicatie" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:262 -msgid "5.3 Kosten voor Upgradediensten voor modules van derden" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:254 +msgid "Volledig geautomatiseerde, geverifieerde back-ups, gerepliceerd in meerdere regio's" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:264 -msgid "De extra kosten voor de Upgradedienst voor modules van derden bedragen EUR (€) 1000,00 (duizend euro) per 1000 Coderegels in de modules van derden, afgerond op de volgende duizend regels. Coderegels omvatten alle tekstregels in de broncode van die modules, ongeacht de programmeertaal (Python, Javascript enz.) of het gegevensformaat (XML, CSV enz.), met uitzondering van lege regels en commentaarregels." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:255 +msgid "Regelmatig getest herstelplan voor rampen" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:271 -msgid "Odoo NV behoudt zich het recht voor om een upgradeaanvraag onder de voor modules van derden onder de bovenstaande voorwaarden te weigeren indien de kwaliteit van de broncode van die modules te slecht is, of indien deze modules een interface vormen met software of systemen van derden. Het upgraden van dergelijke modules zal onderworpen zijn aan een afzonderlijke offerte, buiten deze Overeenkomst." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:257 +msgid "De details van de Cloudhostingdiensten worden beschreven op de Service Level Agreement-pagina op https://www.odoo.com/cloud-sla." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:281 -msgid "5.4 Belastingen" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:263 +msgid "4.5 Ondersteuningsdienst" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:283 -msgid "Alle vergoedingen en kosten zijn exclusief alle toepasselijke federale, provinciale, gewestelijke, lokale of andere overheidsbelastingen, kosten of heffingen (gezamenlijk \"Belastingen\"). De Klant is verantwoordelijk voor het betalen van alle Belastingen die verbonden zijn aan de aankopen die de Klant in het kader van deze Overeenkomst doet, behalve wanneer Odoo NV wettelijk verplicht is om Belastingen te betalen of te incasseren waarvoor de Klant verantwoordelijk is.arden:" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:266 +msgid "Toepassingsgebied" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:292 -msgid "6 Voorwaarden van de Diensten" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:268 +msgid "Voor de duur van deze Overeenkomst kan de klant gratis een onbeperkt aantal ondersteuningstickets openen, uitsluitend voor vragen over Bugs (zie :ref:`bugfix_nl`) of begeleiding met betrekking tot het gebruik van de standaardfuncties van de Software en de Ondersteunde Extra Modules." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:295 -msgid "6.1 Verplichtingen van de Klant" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:272 +msgid "Andere ondersteuningsaanvragen, zoals vragen over ontwikkelingen of aanpassingen, kunnen worden gedekt door de aankoop van een afzonderlijke serviceovereenkomst. Als het niet duidelijk is of een verzoek onder deze Overeenkomst valt, ligt het uiteindelijke besluit bij Odoo NV." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:297 -msgid "De Klant gaat ermee akkoord om:" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:278 +msgid "Beschikbaarheid" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:280 +msgid "Tickets kunnen worden ingediend via het websiteformulier of de telefoonnummers vermeld op https://www.odoo.com/help of, in geval van samenwerking met een Odoo Partner, het door de partner verstrekt kanaal, afhankelijk van de lokale openingstijden." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:288 +msgid "4.6 Werken met een Odoo Partner" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:290 +msgid "Voor bugfixing-, ondersteunings- en upgradediensten kan de Klant ofwel werken met een Odoo Partner als hoofdcontactpersoon, ofwel rechtstreeks met Odoo NV." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:293 +msgid "Als de Klant beslist met een Odoo Partner te werken, zal Odoo NV de diensten met betrekking tot de Ondersteunde Extra Modules uitbesteden aan de Odoo Partner, die de hoofdcontactpersoon van de klant wordt. De Odoo Partner kan namens de klant contact opnemen met Odoo NV voor tweede niveau ondersteuning met betrekking tot de standaardfuncties van de Software." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:299 -msgid "Odoo NV alle toepasselijke kosten voor de Diensten van deze Overeenkomst te betalen in overeenstemming met de betaalvoorwaarden gespecificeerd in de desbetreffende factuur;" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:302 -msgid "Odoo NV onmiddellijk op de hoogte te brengen wanneer het werkelijke aantal Gebruikers of zijn geïnstalleerde Apps de aantallen overschrijden de bij de ondertekening van de Overeenkomst gespecificeerde aantallen overschrijden en in dat geval de toepasselijke extra vergoeding betalen zoals beschreven in de sectie :ref:`charges_standard_nl`;" +msgid "Als de Klant beslist rechtstreeks met Odoo NV samen te werken, worden de diensten met betrekking tot de Ondersteunde Extra Modules geleverd *als en alleen als* de Klant wordt gehost op het Cloudplatform van Odoo." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:306 -msgid "alle nodige maatregelen te nemen om de ongewijzigde uitvoering te waarborgen van het deel van de Software dat de geldigheid van het gebruik van de Odoo Enterprise Edition bevestigt, zoals beschreven in :ref:`enterprise_access_nl`;" +msgid "5 Kosten en vergoedingen" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:309 -msgid "Odoo NV de nodige toegang verlenen om de geldigheid van het gebruik van de Odoo Enterprise Edition op verzoek te controleren (bv. indien blijkt dat de automatische validatie niet werkt voor de Klant);" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:311 +msgid "5.1 Standaardkosten" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:312 -msgid "1 speciale Klantencontactpersoon aan te wijzen voor de volledige duur van de Overeenkomst;" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:313 +msgid "De standaardkosten voor het Odoo Enterprise-abonnement en de diensten zijn gebaseerd op het aantal Gebruikers en het Abonnementsplan die door de klant wordt gebruikt en schriftelijk wordt gespecificeerd bij het afsluiten van de Overeenkomst." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:314 -msgid "alle redelijke maatregelen te nemen om de bestanden en databases van de Klant te beschermen en ervoor te zorgen dat de gegevens van de Klant veilig en beveiligd zijn, en daarbij te erkennen dat Odoo NV niet aansprakelijk kan worden gesteld voor enig gegevensverlies." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:318 +msgid "Wanneer de Klant tijdens de Looptijd van de Overeenkomst meer Gebruikers of meer functies gebruikt waarvoor een ander Abonnementsplan nodig is dan dat gespecifieerd bij het afsluiten van deze Overeenkomst, gaat de Klant ermee akkoord om een extra vergoeding te betalen gelijk aan het toepasselijke tarief (op het moment van de afwijking van het opgegeven aantal Gebruikers of Abonnementsplan) voor de bijkomende Gebruikers of het vereiste Abonnementsplan, voor de rest van de Looptijd." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:322 -msgid "6.2 Niet benaderen of aanwerven" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:325 +msgid "Daarnaast worden de diensten voor Ondersteunde Extra Modules in rekening gebracht op basis van het aantal coderegels in deze modules. Wanneer de Klant kiest voor het onderhoud van de Ondersteunde Extra Modules, bedraagt het tarief de maandelijkse vergoeding per 100 regels code (naar boven afgerond op honderdtallen), zoals schriftelijk gepreciseerd bij het afsluiten van de Overeenkomst. Coderegels worden geteld met het ``cloc`` commando van de Software en omvatten alle tekstregels in de broncode van die modules, ongeacht de programmeertaal (Python, Javascript, XML, enz.), met uitzondering van lege regels, commentaarregels en bestanden die niet worden geladen bij het installeren of uitvoeren van de Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:324 -msgid "Behalve wanneer de andere partij schriftelijk haar toestemming daartoe verleent, gaan elke partij, haar dochterondernemingen en vertegenwoordigers ermee akkoord om geen werknemer te benaderen of aan te werven van de andere partij die betrokken is bij de uitvoering of het gebruik van de Diensten volgens deze Overeenkomst, voor de duur van de Overeenkomst en voor een periode van 24 maanden vanaf de datum van beëindiging of afloop van deze Overeenkomst. In geval van een schending van de voorwaarden van deze sectie die leidt tot het ontslag van voornoemde werknemer gaat de inbreuk makende partij ermee akkoord om de andere partij een bedrag van EUR (€) 30 000,00 (dertigduizend euro) te betalen." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:335 +msgid "Wanneer de Klant een upgrade aanvraagt, kan Odoo NV voor elke Ondersteunde Extra Module die de afgelopen 12 maanden niet werd gedekt door een onderhoudsvergoeding, een eenmalige extra vergoeding aanrekenen voor elke ontbrekende maand dekking." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:339 -msgid "6.3 Publiciteit" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:342 +msgid "5.2 Verlengingskosten" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:341 -msgid "Behoudens andersluidende schriftelijke vermelding verleent elke partij de andere partij een niet-overdraagbare, niet-exclusieve, royaltyvrije, wereldwijde licentie om de naam, de logo's en handelsmerken van de andere partij te reproduceren en weer te geven, uitsluitend om naar de andere partij te verwijzen als een klant of leverancier, op websites, in persberichten en ander marketingmateriaal." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:344 +msgid "Indien, bij verlenging zoals beschreven in de sectie :ref:`term_nl`, de kosten gedurende de vorige Looptijd lager zijn dan de meest actuele geldende tarieven, zullen de kosten met maximaal 7% stijgen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:352 -msgid "6.4 Vertrouwelijkheid" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:351 +msgid "5.3 Belastingen" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:362 -msgid "Definitie van \"Vertrouwelijke informatie\":" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:355 -msgid "Alle informatie die door een partij (de \"Bekendmakende Partij\") aan de andere partij (de \"Ontvangende Partij\") wordt bekendgemaakt, hetzij mondeling of schriftelijk, en die als vertrouwelijk wordt aangemerkt of die redelijkerwijs als vertrouwelijk moet worden beschouwd gezien de aard van de informatie en de omstandigheden van de bekendmaking. In het bijzonder moet alle informatie met betrekking tot het bedrijf, zaken, producten, ontwikkelingen, handelsgeheimen, knowhow, personeel, klanten en leveranciers van beide partijen als vertrouwelijk worden beschouwd." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:353 +msgid "Alle vergoedingen en kosten zijn exclusief alle toepasselijke federale, provinciale, gewestelijke, lokale of andere overheidsbelastingen, vergoedingen of heffingen (gezamenlijk \"Belastingen\"). De Klant is verantwoordelijk voor het betalen van alle Belastingen die verbonden zijn aan de aankopen die de Klant in het kader van deze Overeenkomst doet, behalve wanneer Odoo NV wettelijk verplicht is om Belastingen te betalen of te heffen waarvoor de Klant verantwoordelijk is." msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:364 -msgid "Voor alle Vertrouwelijke Informatie die tijdens de Looptijd van deze Overeenkomst wordt ontvangen, zal de Ontvangende Partij dezelfde mate van zorg aanwenden die zij aanwendt om de vertrouwelijkheid van haar eigen gelijkaardige Vertrouwelijke Informatie te beschermen, maar op zijn minst redelijke zorg." +msgid "6 Voorwaarden van de Diensten" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:367 +msgid "6.1 Verplichtingen van de Klant" msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:369 -msgid "De Ontvangende Partij mag Vertrouwelijke Informatie van de Bekendmakende Partij bekendmaken voor zover ze wettelijk verplicht is om dit te doen, mits de Ontvangende Partij de Bekendmakende Partij vooraf in kennis stelt van de verplichte bekendmaking, voor zover toegestaan door de wet." +msgid "De Klant gaat ermee akkoord om:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:377 -msgid "6.5 Beëindiging" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:371 +msgid "Odoo NV alle toepasselijke kosten voor de Diensten van deze Overeenkomst te betalen in overeenstemming met de betalingsvoorwaarden bepaald bij het afsluiten van deze Overeenkomst;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:379 -msgid "In het geval dat een van beide Partijen een van de uit deze Overeenkomst voortvloeien verplichtingen niet nakomt en deze nalatigheid niet binnen 30 kalenderdagen na de schriftelijke kennisgeving van deze nalatigheid verholpen is, kan deze Overeenkomst onmiddellijk worden beëindigd door de niet in gebreke blijvende Partij." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:374 +msgid "Odoo NV onmiddellijk op de hoogte te brengen wanneer het werkelijke aantal Gebruikers de aantallen overschrijden die bij het afsluiten van de Overeenkomst werden bepaald, en in dat geval de toepasselijke extra vergoeding te betalen zoals beschreven in de sectie :ref:`charges_standard_nl`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:385 -msgid "Verder kan Odoo NV de Overeenkomst onmiddellijk beëindigen in het geval dat de Klant de toepasselijke vergoedingen voor de Diensten niet betaalt tegen de vervaldatum die wordt vermeld op de desbetreffende factuur." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:378 +msgid "alle nodige maatregelen te nemen om de ongewijzigde uitvoering te waarborgen van het deel van de Software dat de geldigheid van het gebruik van de Odoo Enterprise Edition bevestigt, zoals beschreven in :ref:`enterprise_access_nl`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:393 -msgid "Overlevende bepalingen:" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:381 +msgid "1 toegewijde Klantcontactpersoon aan te duiden voor de volledige duur van de Overeenkomst;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:390 -msgid "De secties \":ref:`confidentiality_nl`”, \":ref:`disclaimers_nl`”, \":ref:`liability_nl`” en \":ref:`general_provisions_nl`” zullen geldig blijven na beëindiging of afloop van deze Overeenkomst." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:383 +msgid "Odoo NV 30 dagen voor het veranderen van zijn hoofdcontactpersoon schriftelijk in kennis te stellen dat hij met een andere Odoo Partner of rechtstreeks met Odoo NV wenst samen te werken." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:398 -msgid "7 Garanties, afwijzingen van aansprakelijkheid, aansprakelijkheid" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:387 +msgid "Wanneer de Klant kiest voor het Cloudplatform, gaat de Klant ermee akkoord om:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:403 -msgid "7.1 Garanties" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:389 +msgid "alle redelijke maatregelen te nemen om zijn gebruikersaccount veilig te houden, onder meer door een sterk wachtwoord te kiezen en dit niet met anderen te delen;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:405 -msgid "Voor de duur van deze Overeenkomst verbindt Odoo NV zich ertoe om commercieel redelijke inspanningen aan te wenden om de Diensten uit te voeren in overeenstemming met de algemeen aanvaarde industrienormen op voorwaarde dat:" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:391 +msgid "een redelijk gebruik te maken van de Hostingdiensten, met uitsluiting van illegale of onrechtmatige activiteiten, en zich strikt te houden aan de regels gepreciseerd in het Beleid voor acceptabel gebruik, beschikbaar op https://odoo.com/acceptable-use." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:395 +msgid "Wanneer de Klant kiest voor de Self-Hosting optie, gaat de Klant ermee akkoord om:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:397 +msgid "alle redelijke maatregelen te nemen om de bestanden en databases van de Klant te beschermen en om ervoor te zorgen dat de gegevens van de Klant veilig zijn, waarbij wordt erkend dat Odoo NV niet aansprakelijk kan worden gesteld voor enig verlies van gegevens;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:400 +msgid "Odoo NV de nodige toegang te verlenen om op verzoek de geldigheid van het gebruik van de Odoo Enterprise Edition te controleren (bijv. als de automatische validatie voor de klant niet blijkt te werken)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:407 +msgid "6.2 Niet benaderen of aanwerven" msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:409 -msgid "de computersystemen van de Klant in goede bedrijfsstaat zijn en de Software geïnstalleerd is in een geschikte werkomgeving;" +msgid "Behalve wanneer de andere partij schriftelijk haar toestemming daartoe verleent, gaan elke partij, haar dochterondernemingen en vertegenwoordigers ermee akkoord om geen werknemers te benaderen of aan te werven van de andere partij die betrokken zijn bij de uitvoering of het gebruik van de Diensten volgens deze Overeenkomst, voor de duur van de Overeenkomst en voor een periode van 12 maanden na de datum van beëindiging of afloop van deze Overeenkomst. In geval van een schending van de voorwaarden van deze sectie die leidt tot het ontslag van voornoemde werknemer gaat de inbreukmakende partij ermee akkoord om de andere partij een bedrag van (€) 30 000,00 euro (dertigduizend euro) te betalen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:411 -msgid "de Klant passende probleemoplossingsen toegangsinformatie, zodat Odoo NV problemen kan identificeren, reproduceren en verhelpen;" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:423 +msgid "6.3 Publiciteit" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:413 -msgid "alle aan Odoo NV verschuldigde bedragen zijn betaald." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:425 +msgid "Behoudens andersluidende schriftelijke vermelding verleent elke partij de andere partij een niet-overdraagbare, niet-exclusieve, rechtenvrije, wereldwijde licentie om de naam, de logo's en handelsmerken van de andere partij te reproduceren en weer te geven, uitsluitend om naar de andere partij te verwijzen als een klant of leverancier, op websites, in persberichten en ander marketingmateriaal." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:415 -msgid "Het enige en exclusieve verhaal van de Klant en de enige verplichting van Odoo NV in geval van een inbreuk op deze garantie is dat Odoo NV de uitvoering van de Diensten zonder extra kosten hervat." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:435 +msgid "6.4 Vertrouwelijkheid" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:422 -msgid "7.2 Afwijzingen van aansprakelijkheid" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:424 -msgid "Behalve zoals uitdrukkelijk hierin wordt vermeld, geeft geen enkele partij enige garantie, uitdrukkelijk, impliciet, wettelijk of anderszins, en wijst elke partij nadrukkelijk alle impliciete garanties af, met inbegrip van enige impliciete garanties van verkoopbaarheid, geschiktheid voor een bepaald doel of niet-inbreuk, voor zover maximaal toegestaan door de toepasselijke wetgeving." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:430 -msgid "Odoo NV garandeert niet dat de Software voldoet aan alle lokale of internationale wet- of regelgeving." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_nl.rst:436 -msgid "7.3 Beperking van aansprakelijkheid" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:445 +msgid "Definitie van \"Vertrouwelijke informatie\":" msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:438 -msgid "Voor zover maximaal toegestaan door de wet, zal de totale aansprakelijkheid van elke partij samen met haar dochterondernemingen die voortvloeit uit of verband houdt met deze Overeenkomst niet meer bedragen dan 50% van het totale bedrag betaald door de Klant in het kader van deze Overeenkomst gedurende de 12 maanden onmiddellijk voorafgaand aan de datum van de gebeurtenis die aanleiding geeft tot dergelijke claim. Meerdere claims zullen deze beperking niet vergroten." +msgid "Alle informatie die door een partij (de \"Bekendmakende Partij\") aan de andere partij (de \"Ontvangende Partij\") wordt bekendgemaakt, hetzij mondeling of schriftelijk, en die als vertrouwelijk wordt aangemerkt of die redelijkerwijs als vertrouwelijk moet worden beschouwd gezien de aard van de informatie en de omstandigheden van de bekendmaking. In het bijzonder moet alle informatie met betrekking tot het bedrijf, zaken, producten, ontwikkelingen, handelsgeheimen, knowhow, personeel, klanten en leveranciers van beide partijen als vertrouwelijk worden beschouwd." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:446 -msgid "In geen geval zal een van de partijen of haar dochterondernemingen aansprakelijk zijn voor enige indirecte, speciale, exemplaire, incidentele of gevolgschade van welke aard dan ook, met inbegrip van maar niet beperkt tot verlies van inkomsten, winst, besparingen, verlies van zaken of ander financieel verlies, kosten van stilstand of vertraging, verloren of beschadigde gegevens, voortkomend uit of in verband met deze Overeenkomst, ongeacht de vorm van actie, hetzij in contract, onrechtmatige daad (met inbegrip van strikte nalatigheid) of enige andere wettelijke of billijke theorie, zelfs indien een partij of haar dochterondernemingen op de hoogte zijn gebracht van de mogelijkheid van dergelijke schade, of indien het verhaal van een partij of haar dochteronderneming anderszins haar essentiële doel voorbijschiet." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:447 +msgid "Voor alle Vertrouwelijke Informatie die tijdens de Looptijd van deze Overeenkomst wordt ontvangen, zal de Ontvangende Partij dezelfde mate van zorgvuldigheid aan de dag leggen die welke zij aanwendt om de vertrouwelijkheid van haar eigen gelijkaardige Vertrouwelijke Informatie te beschermen, doch niet minder dan een redelijke zorgvuldigheid." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:461 -msgid "7.4 Overmacht" +#: ../../content/legal/terms/i18n/enterprise_nl.rst:452 +msgid "De Ontvangende Partij mag Vertrouwelijke Informatie van de Bekendmakende Partij bekendmaken voor zover ze wettelijk verplicht is om dit te doen, mits de Ontvangende Partij de Bekendmakende Partij vooraf in kennis stelt van de verplichte bekendmaking, voor zover toegestaan door de wet." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:460 +msgid "6.5 Gegevensbescherming" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:466 +msgid "Definities" msgstr "" #: ../../content/legal/terms/i18n/enterprise_nl.rst:463 -msgid "Geen der partijen zal aansprakelijk zijn jegens de andere partij voor de vertraging in de uitvoering of het verzuim om een prestatie in het kader van deze Overeenkomst te verrichten wanneer dergelijk verzuim of dergelijke vertraging wordt veroorzaakt door overheidsbepalingen, brand, staking, oorlog, overstroming, ongeval, epidemie, embargo, volledige of gedeeltelijke toe- eigening van een fabriek of product door een regering of overheidsinstantie, of enige andere oorzaak of oorzaken, hetzij van gelijke of andere aard, buiten de redelijke controle van die partij, zolang dergelijke oorzaak of oorzaken bestaan." +msgid "\"Persoonsgegevens\", \"Verwerkingsverantwoordelijke\", \"Verwerken\" hebben dezelfde betekenis als in de Verordening (EU) 2016/679 en de Richtlijn 2002/58/EG en elke verordening of wetgeving die deze wijzigt of vervangt (hierna \"Gegevensbeschermingswetgeving\" genoemd)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:477 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:469 +msgid "Verwerken van persoonsgegevens" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:471 +msgid "De partijen erkennen dat de database van de Klant Persoonsgegevens kan bevatten, waarvoor de Klant de Verwerkingsverantwoordelijke is. Deze gegevens worden verwerkt door Odoo NV wanneer de Klant hiertoe opdracht geeft, door gebruik te maken van een van de Diensten waarvoor een database nodig is (bijv. de Cloudhostingdiensten of de Database Upgradediensten) of wanneer de Klant zijn of haar database of een deel daarvan overdraagt aan Odoo NV om welke reden dan ook die verband houdt met deze Overeenkomst." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:478 +msgid "Deze gegevensverwerking wordt uitgevoerd in overeenstemming met de Gegevensbeschermingswetgeving. In het bijzonder verbindt Odoo NV zich ertoe:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:481 +msgid "(a) de Persoonsgegevens enkel te verwerken wanneer en zoals opgedragen door de Klant, en met oog op de uitvoering van één van de Diensten in het kader van deze Overeenkomst, tenzij de wet dit vereist, in welk geval Odoo NV de Klant hiervan voorafgaand in kennis stelt, tenzij de wet dit verbiedt;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:485 +msgid "(b) ervoor te zorgen dat alle personen binnen Odoo NV die gemachtigd zijn om de Persoonsgegevens te verwerken, zich tot geheimhouding verplichten;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:487 +msgid "(c) passende technische en organisatorische maatregelen te nemen en te handhaven om de Persoonsgegevens te beschermen tegen ongeoorloofde of onwettige verwerking en tegen onopzettelijk verlies, vernietiging, beschadiging, diefstal, wijziging of openbaarmaking;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:490 +msgid "(d) elk verzoek om gegevensbescherming dat is ingediend bij Odoo NV met betrekking tot de database van de Klant onverwijld door te sturen naar de Klant;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:492 +msgid "(e) de Klant onverwijld op de hoogte te stellen wanneer zij kennis neemt en bevestiging krijgt van een onopzettelijke, ongeoorloofde of onwettige verwerking van, openbaarmaking van of toegang tot de Persoonsgegevens;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:495 +msgid "(f) de Klant te informeren indien de verwerkingsinstructies naar het oordeel van Odoo NV in strijd zijn met de toepasselijke Gegevensbeschermingswetgeving;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:497 +msgid "(g) aan de Klant alle informatie ter beschikking te stellen die nodig is om de naleving van de Gegevensbeschermingswetgeving aan te tonen en audits, met inbegrip van inspecties, die door de Klant worden uitgevoerd of opgedragen, toe te staan en er redelijkerwijs aan bij te dragen;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:501 +msgid "(h) alle kopieën van de database van de Klant die in het bezit zijn van Odoo NV definitief te verwijderen, of dergelijke gegevens terug te geven, naar keuze van de Klant, bij beëindiging van deze Overeenkomst, met inachtneming van de termijnen die in het `Privacybeleid `_ van Odoo NV zijn bepaald." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:506 +msgid "Met betrekking tot punten (d) tot (f) verbindt de klant zich ertoe Odoo NV te allen tijde te voorzien van nauwkeurige contactgegevens, die nodig zijn om de verantwoordelijke van de gegevensbescherming van de Klant in kennis te stellen." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:511 +msgid "Subverwerkers" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:513 +msgid "De Klant erkent en gaat ermee akkoord dat Odoo NV voor de levering van de Diensten een beroep kan doen op externe dienstverleners (Subverwerkers) om Persoonsgegevens te verwerken. Odoo NV verbindt zich ertoe alleen Subverwerkers te gebruiken in overeenstemming met de Gegevensbeschermingswetgeving. Dit gebruik zal het voorwerp zijn van een contract tussen Odoo NV en de Subverwerker dat daartoe garanties biedt. Het Privacybeleid van Odoo NV, beschikbaar op https://www.odoo.com/privacy biedt actuele informatie over de namen en doeleinden van Subverwerkers waarop Odoo NV momenteel een beroep doet in het kader van de uitvoering van de Diensten." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:524 +msgid "6.6 Beëindiging" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:526 +msgid "Indien een van de Partijen niet voldoet aan een van de uit deze Overeenkomst voortvloeiende verplichtingen en indien deze nalatigheid niet binnen 30 kalenderdagen na de schriftelijke kennisgeving van deze nalatigheid verholpen is, kan de niet in gebreke blijvende Partij deze Overeenkomst onmiddellijk beëindigen." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:532 +msgid "Bovendien kan Odoo NV de Overeenkomst onmiddellijk beëindigen in het geval dat de Klant de toepasselijke vergoedingen voor de Diensten niet betaalt binnen de 21 dagen na de vervaldatum die op de desbetreffende factuur vermeld wordt, en na minstens 2 herinneringen." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:541 +msgid "Overlevende bepalingen:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:538 +msgid "De secties \":ref:`confidentiality_nl`”, \":ref:`disclaimers_nl`”, \":ref:`liability_nl`” en \":ref:`general_provisions_nl`” blijven geldig na de beëindiging of het afloop van deze Overeenkomst." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:546 +msgid "7 Garanties, Uitsluitingen en Aansprakelijkheid" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:551 +msgid "7.1 Garanties" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:553 +msgid "Odoo NV bezit het auteursrecht of een gelijkwaardig recht [#cla_nl1]_ op 100 % van de code van de Software en bevestigt dat alle softwarebibliotheken die nodig zijn om de Software te gebruiken beschikbaar zijn onder een licentie die compatibel is met de licentie van de Software." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:558 +msgid "Voor de duur van deze Overeenkomst verbindt Odoo NV zich ertoe om commercieel redelijke inspanningen aan te wenden om de Diensten uit te voeren in overeenstemming met de algemeen aanvaarde industrienormen op voorwaarde dat:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:562 +msgid "de computersystemen van de Klant in goede bedrijfsstaat zijn en, in geval van Self-Hosting, de Software geïnstalleerd is in een geschikte werkomgeving;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:564 +msgid "de Klant passende probleemoplossingsen verstrekt en, in geval van Self-Hosting, Odoo NV de nodige toegang verleent opdat Odoo NV de problemen zou kunnen identificeren, reproduceren en verhelpen;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:567 +msgid "alle aan Odoo NV verschuldigde bedragen zijn betaald." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:569 +msgid "Het enige en exclusieve verhaal van de Klant en de enige verplichting van Odoo NV in geval van een inbreuk op deze garantie is dat Odoo NV de uitvoering van de Diensten zonder extra kosten hervat." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:573 +msgid "Externe bijdragen worden gedekt door een `Copyright License Agreement `_ die een permanente, gratis en onherroepelijke auteursrecht- en octrooilicentie aan Odoo NV verstrekt." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:580 +msgid "7.2 Uitsluiting van garantie" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:582 +msgid "Behoudens uitdrukkelijke andersluidende bepalingen, geeft geen enkele partij enige uitdrukkelijke, impliciete, wettelijke of andere garantie en wijst elke partij nadrukkelijk alle impliciete garanties van de hand, met inbegrip van enige impliciete garanties van verkoopbaarheid, geschiktheid voor een bepaald doel of niet-inbreuk, voor zover toegestaan door de toepasselijke wetgeving." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:588 +msgid "Odoo NV garandeert niet dat de Software voldoet aan alle lokale of internationale wetgeving of regelgeving." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:594 +msgid "7.3 Beperking van aansprakelijkheid" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:596 +msgid "Voor zover maximaal toegestaan door de wet, zal de totale aansprakelijkheid van elke partij samen met haar dochterondernemingen die voortvloeit uit of verband houdt met deze Overeenkomst niet meer bedragen dan 50% van het totale bedrag betaald door de Klant in het kader van deze Overeenkomst gedurende de 12 maanden onmiddellijk voorafgaand aan de datum van de gebeurtenis die aanleiding geeft tot dergelijke claim. Meerdere claims zullen deze beperking niet vergroten." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:604 +msgid "In geen geval zal een van de partijen of haar dochterondernemingen aansprakelijk zijn voor enige indirecte, bijzondere, exemplaire, incidentele of gevolgschade van welke aard dan ook, met inbegrip van, maar niet beperkt tot verlies van inkomsten, winst, besparingen, verlies van zaken of ander financieel verlies, kosten van stilstand of vertraging, verloren of beschadigde gegevens, voortkomend uit of in verband met deze Overeenkomst, ongeacht de vorm van actie, hetzij uit overeenkomst, hetzij uit onrechtmatige daad of anderszins, zelfs indien een partij of haar dochterondernemingen op de hoogte zijn gebracht van het risico van dergelijke schade, of indien het verhaal van een partij of haar dochterondernemingen anderszins haar wezenlijke doel voorbijschiet." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:618 +msgid "7.4 Overmacht" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:620 +msgid "Geen enkele partij zal aansprakelijk zijn jegens de andere partij voor de vertraging in de uitvoering of het verzuim om een prestatie in het kader van deze Overeenkomst te verrichten wanneer dergelijk verzuim of dergelijke vertraging wordt veroorzaakt door een geval van overmacht, zoals overheidsbepalingen, brand, staking, oorlog, overstroming, ongeval, epidemie, embargo, volledige of gedeeltelijke toe- eigening van een fabriek of product door een regering of overheidsinstantie, of enige andere oorzaak of oorzaken, hetzij van gelijke of andere aard, buiten de redelijke controle van die partij, zolang dergelijke oorzaak of oorzaken bestaan." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_nl.rst:634 msgid "8 Algemene bepalingen" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:482 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:639 msgid "8.1 Toepasselijk recht" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:484 -msgid "Beide partijen komen overeen dat de wetten van België van toepassing zijn in geval van geschillen die voortvloeien uit of verband houden met deze Overeenkomst, ongeacht de keuze of botsing van rechtsbeginselen. Voor zover een rechtszaak of gerechtelijke procedure in dit verband is toegestaan, komen beide partijen overeen om zich te onderwerpen aan de exclusieve bevoegdheid van de rechtbank van Nijvel (België) voor de beslechting van alle geschillen." +#: ../../content/legal/terms/i18n/enterprise_nl.rst:641 +msgid "Onderhavige Overeenkomst en alle orders van de Klant zijn onderworpen aan het Belgische recht. Elk geschil dat voortvloeit uit of verband houdt met deze Overeenkomst of een order van een Klant is onderworden aan de exclusieve bevoegdheid van de Ondernemingsrechtbank van Nivelles." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:494 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:649 msgid "8.2 Scheidbaarheid" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:496 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:651 msgid "Ingeval een of meerdere bepalingen van deze Overeenkomst of een toepassing daarvan in enig opzicht ongeldig, onwettig of niet-afdwingbaar is/zijn, zullen de geldigheid, wettigheid en afdwingbaarheid van de overige bepalingen van deze Overeenkomst en elke toepassing daarvan op geen enkele wijze worden beïnvloed of aangetast. Beide partijen verbinden zich ertoe om elke eventuele ongeldige, onwettige of niet-afdwingbare bepaling van deze Overeenkomst te vervangen door een geldige bepaling met dezelfde effecten en doelstellingen." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:508 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:662 msgid "9 Bijlage A: Odoo Enterprise Edition-licentie" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:512 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:666 msgid "De Odoo Enterprise Edition wordt in licentie gegeven onder de Odoo Enterprise Edition License v1.0, die als volgt wordt gedefinieerd:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_nl.rst:521 +#: ../../content/legal/terms/i18n/enterprise_nl.rst:675 msgid "Zie :ref:`odoo_enterprise_license`." msgstr "" +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:5 +msgid "Odoo Enterprise Subscription Agreement (PT)" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:9 +msgid "`Download PDF `_" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:11 +msgid "Esta é uma tradução em português do Contrato “Odoo Enterprise Subscription Agreement”. A tradução é fornecida com o intuito de facilitar a sua compreensão, mas não tem valor legal. A única referência oficial aos termos do Contrato “Odoo Enterprise Subscription Agreement” é a :ref:`versão original em inglês `." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:16 +msgid "Versão 10a - 2022-10-27" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:33 +msgid "Ao assinar os serviços do Odoo Enterprise (os \"Serviços\") fornecidos pela Odoo SA e suas afiliadas (coletivamente, \"Odoo SA\") em relação ao Odoo Enterprise Edition ou Odoo Community Edition (o \"Logiciel\"), hospedado nas plataformas de nuvem da Odoo SA (\"Cloud Platform\") ou no local (\"Hospedagem Própria\"), você (o \"Cliente\") concorda em estar vinculado aos seguintes termos e condições (o \"Contrato\")." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:42 +msgid "1 Vigência do Contrato" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:44 +msgid "A duração deste Contrato (a \"Vigência\") será especificada por escrito no ato da celebração deste Contrato, começando a partir da data de assinatura. O Contrato é automaticamente renovado por uma Vigência igual, a menos que qualquer uma das partes forneça um aviso por escrito de rescisão para a outra parte, no mínimo 30 dias antes do final da Vigência." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:52 +msgid "2 Definições" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:58 +msgid "Usuário" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:55 +msgid "Qualquer conta de usuário indicada como ativa no Software, com acesso ao modo de criação e/ou edição. Contas de usuário desativadas e contas usadas por pessoas externas (ou sistemas) que têm apenas acesso limitado ao Software por meio das instalações do portal (conhecidas como \"Usuários do Portal\") não são consideradas como Usuários." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:61 +msgid "Um \"Aplicativo\" (App) é um grupo especializado de recursos disponíveis para instalação no Software." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:67 +msgid "Parceiro Odoo" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:64 +msgid "Um Parceiro Odoo é uma empresa ou indivíduo terceirizado, escolhido pelo Cliente e que trabalha com o Cliente para seus serviços relacionados ao Odoo. O Cliente pode decidir a qualquer momento trabalhar com um Parceiro Odoo diferente ou trabalhar diretamente com a Odoo SA (sujeito a aviso prévio)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:74 +msgid "Módulo Extra" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:70 +msgid "Um Módulo Extra é um diretório de arquivos de código-fonte ou um conjunto de customizações baseadas em Python, criadas em uma base de dados (por exemplo, com o Odoo Studio), que adiciona recursos ou altera o comportamento padrão do Software. Pode ter sido desenvolvido pelo Cliente, pela Odoo SA, por um Parceiro Odoo em nome do Cliente ou por terceiros." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:78 +msgid "Módulo Extra Coberto" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:77 +msgid "Um Módulo Extra Coberto é um Módulo Extra pelo qual o Cliente escolhe pagar uma taxa de manutenção para obter serviços de suporte, atualização e correção de bugs." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:81 +msgid "É considerado Bug qualquer falha do Software ou de um Módulo Extra Coberto que resulte em uma parada completa, rastreamento de erro ou violação de segurança e não seja causada diretamente por uma instalação ou configuração defeituosa. A não conformidade com especificações ou requisitos será considerada como Bug, a critério da Odoo SA (normalmente, quando o Software não produz os resultados ou desempenho para o qual foi projetado ou quando um recurso específico do país não atende mais aos requisitos legais de contabilidade)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:91 +msgid "Versões Cobertas" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:89 +msgid "A menos que seja especificado, os Serviços fornecidos sob este Contrato são aplicáveis apenas às Versões Cobertas do Software, que incluem as 3 versões principais lançadas mais recentemente." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:95 +msgid "Plano de Assinatura" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:94 +msgid "Um Plano de Assinatura define um conjunto de Aplicativos, recursos e soluções de hospedagem cobertos por este Contrato e é definido por escrito na celebração deste Contrato." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:100 +msgid "3 Acesso ao Software" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:102 +msgid "O Cliente pode utilizar o Software hospedado na Cloud Platform, ou escolher a opção de Hospedagem Própria. A Cloud Platform é hospedada e totalmente gerenciada pela Odoo SA e acessada remotamente pelo Cliente. Com a opção de Hospedagem Própria, o Cliente hospeda o Software em sistemas de computador de sua escolha, que não estão sob o controle da Odoo SA." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:107 +msgid "Durante a vigência deste Contrato, a Odoo SA concede ao Cliente uma licença não exclusiva e intransferível para usar (executar, modificar, executar após modificação) o software Odoo Enterprise Edition, nos termos estabelecidos em :ref:`appendix_a_pt`." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:111 +msgid "O Cliente concorda em tomar todas as medidas necessárias para garantir a execução inalterada da parte do Software que verifica a validade de uso do Odoo Enterprise Edition e coleta estatísticas para esse fim, incluindo, entre outros, a execução de uma instância, o número de Usuários, os Aplicativos instalados e o número de linhas de código dos Módulos Extras Cobertos." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:116 +msgid "A Odoo SA compromete-se a não divulgar figuras individuais ou nomeadas a terceiros sem o consentimento do Cliente, e a tratar todos os dados recolhidos em conformidade com a sua Política de Privacidade oficial, publicada em https://www.odoo.com/privacy." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:120 +msgid "Após a expiração ou rescisão deste Contrato, esta licença é revogada imediatamente e o Cliente concorda em parar de usar o software Odoo Enterprise Edition e a Cloud Platform." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:123 +msgid "Se o Cliente violar os termos desta seção, o Cliente concorda em pagar à Odoo SA uma taxa extra igual a 300% do preço de tabela aplicável ao número real de Usuários." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:129 +msgid "4 Serviços" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:134 +msgid "4.1 Serviço de Correção de Bugs" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:136 +msgid "Durante a vigência deste Contrato, a Odoo SA se compromete a realizar todos os esforços razoáveis para corrigir qualquer Bug do Software e Módulos Extras Cobertos relatados pelo Cliente por meio de um canal apropriado (normalmente, o formulário da Web ou os números de telefone listados em http://www.odoo.com.help, ou, ao trabalhar com um parceiro Odoo, o canal fornecido pelo parceiro) e começar a lidar com essas solicitações do Cliente em 2 dias úteis." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:142 +msgid "Assim que o Bug for corrigido, uma solução apropriada será comunicada ao Cliente. Se o Cliente estiver usando uma Versão Coberta, ele não será solicitado a atualizar para uma Versão Coberta mais recente do Software como solução para um Bug." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:146 +msgid "Quando um Bug é corrigido em qualquer Versão Coberta, a Odoo SA se compromete a corrigir o Bug em todas as Versões Cobertas mais recentes do Software." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:149 +msgid "Ambas as partes reconhecem que, conforme especificado na licença do Software e na seção :ref:`liability_pt` deste Contrato, a Odoo SA não pode ser responsabilizada por Bugs no Software ou nos Módulos Extras Cobertos." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:154 +msgid "4.2 Serviço de Atualizações de Segurança" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:159 +msgid "Hospedagem Própria" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:161 +msgid "Durante a vigência deste Contrato, a Odoo SA se compromete a enviar um “Aviso de Segurança” ao Cliente para qualquer Bug de segurança descoberto nas Versões Cobertas do Software (isso exclui Módulos Extras), pelo menos 2 semanas antes de publicar o Comunicado de Segurança, a menos que o Bug já tenha sido divulgado publicamente por terceiros. Os Comunicados de Segurança incluem uma descrição completa do Bug, sua causa, seus possíveis impactos nos sistemas do Cliente e a solução correspondente para cada Versão Coberta." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:168 +msgid "O Cliente entende que o Bug e as informações do Comunicado de Segurança devem ser tratados como Informações Confidenciais conforme descrito em :ref:`confidentiality_pt` durante o período de embargo que precede a divulgação pública." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:177 +msgid "A Odoo SA se compromete a aplicar os reparos de segurança para qualquer Bug de segurança descoberto em uma versão do Software hospedada na Cloud Platform, em todos os sistemas sob seu controle, assim que o reparo estiver disponível, sem exigir nenhuma ação manual do Cliente." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:185 +msgid "4.3 Serviços de Atualização" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:190 +msgid "Serviço de Atualização para o Software" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:192 +msgid "Durante a vigência deste Contrato, o Cliente pode enviar solicitações de atualização por meio do canal apropriado (geralmente, o site do serviço de atualização da Odoo SA), a fim de converter uma base de dados do Software de qualquer versão do Software para uma Versão Coberta mais recente (a \"Versão de Destino\")." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:197 +msgid "Para a Cloud Platform, as solicitações de atualização são enviadas diretamente do painel de controle da Cloud Platform e não requerem nenhum upload de dados. Para Hospedagem Própria, as solicitações de atualização devem incluir uma cópia da base de dados do Cliente e os dados associados (normalmente obtidos no menu Backup do Software)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:202 +msgid "Este serviço é fornecido por meio de uma plataforma automatizada para permitir que o Cliente execute atualizações autônomas, uma vez que uma versão anterior da base de dados do Cliente tenha sido atualizada com sucesso para uma Versão Coberta." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:206 +msgid "O Serviço de Atualização é limitado à conversão técnica e adaptação da base de dados do Cliente para torná-lo compatível com a Versão de Destino, a correção de qualquer Bug causado diretamente pela operação de atualização e que não ocorre normalmente na Versão de Destino, e a conversão do código-fonte e dados dos Módulos Extras Cobertos para a Versão de Destino." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:212 +msgid "É responsabilidade do Cliente verificar e validar a base de dados atualizada para detectar Bugs, analisar o impacto de alterações e novos recursos implementados na Versão de Destino e converter e adaptar para a Versão de Destino quaisquer extensões de terceiros do Software que tenham sido instaladas na base de dados antes da atualização (por exemplo, Módulos Extras não cobertos). O Cliente pode fazer várias solicitações de atualização para uma base de dados, até que um resultado aceitável seja alcançado." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:223 +msgid "4.4 Serviços de Hospedagem na Nuvem" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:225 +msgid "Durante a vigência deste Contrato, quando o Cliente optar por usar a Cloud Platform, a Odoo SA se compromete a fornecer pelo menos os seguintes serviços:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:228 +msgid "Opções de várias regiões de hospedagem (mínimo 3: Europa, América, Ásia/Pacífico)" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:229 +msgid "Hospedagem em data centers Tier III ou equivalente, com 99,9% de tempo de atividade da rede" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:230 +msgid "Criptografia SSL (HTTPS) de comunicação classe A" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:231 +msgid "Backups totalmente automatizados e verificados, replicados em várias regiões" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:232 +msgid "Plano de recuperação de desastres, testado regularmente" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:234 +msgid "Os detalhes dos Serviços de Hospedagem na Nuvem são descritos na página do Acordo de Nível de Serviço (SLA) em https://www.odoo.com/cloud-sla." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:241 +msgid "4.5 Serviços de Suporte" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:244 +msgid "Escopo" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:246 +msgid "Durante a vigência deste Contrato, o Cliente pode abrir um número ilimitado de chamados de suporte gratuitamente, exclusivamente para questões relacionadas a Bugs (consulte :ref:`bugfix_pt`) ou orientação com relação ao uso dos recursos padrão do Software e Módulos Extras Cobertos." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:250 +msgid "Outras solicitações de assistência, como questões relacionadas a desenvolvimento ou customizações, podem ser cobertas por meio da compra de um contrato de serviço separado. Caso não esteja claro se uma solicitação é coberta por este Contrato, a decisão fica a critério da Odoo SA." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:256 +msgid "Disponibilidade" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:258 +msgid "Os chamados podem ser feitos por meio do formulário da web ou dos números de telefone listados em https://www.odoo.com/help, ou, ao trabalhar com um Parceiro Odoo, o canal fornecido pelo parceiro, sujeito ao horário de funcionamento local." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:268 +msgid "4.6 Trabalhando com um Parceiro Odoo" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:270 +msgid "Para correções de bugs, suporte e serviços de atualização, o cliente pode trabalhar com um parceiro Odoo como principal ponto de contato ou trabalhar diretamente com a Odoo SA." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:273 +msgid "Se o Cliente decidir trabalhar com um Parceiro Odoo, a Odoo SA subcontratará os serviços relacionados com os Módulos Extras Cobertos ao Parceiro Odoo, que se torna o principal ponto de contacto do Cliente. O Parceiro Odoo pode entrar em contato com a Odoo SA em nome do Cliente para obter assistência de segundo nível com relação aos recursos padrão do Software." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:278 +msgid "Se o Cliente decidir trabalhar diretamente com a Odoo SA, os serviços relacionados aos Módulos Extras Cobertos serão fornecidos somente se o Cliente estiver hospedado na Odoo Cloud Platform." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:286 +msgid "5 Preços e Taxas" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:291 +msgid "5.1 Preços Padrões" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:293 +msgid "Os preços padrões para a assinatura do Odoo Enterprise e os Serviços são baseados no número de Usuários e no Plano de Assinatura usado pelo Cliente e especificados por escrito na celebração do Contrato." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:297 +msgid "Se durante a Vigência, o Cliente tiver mais Usuários ou usar recursos que exijam outro Plano de Assinatura do que o especificado no momento da celebração deste Contrato, o Cliente concorda em pagar uma taxa extra equivalente ao preço de tabela aplicável (no momento do desvio do número especificado de Usuários ou Plano de Assinatura) para os Usuários adicionais ou o Plano de Assinatura necessário, pelo restante da Vigência." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:303 +msgid "Além disso, os serviços dos Módulos Extras Cobertos são cobrados com base no número de linhas de código nesses módulos. Quando o Cliente optar pela manutenção dos Módulos Extras Cobertos, a cobrança será mensal por 100 linhas de código (arredondadas para a próxima centena), conforme especificado por escrito na celebração do Contrato. As linhas de código serão contabilizadas com o comando ``cloc`` do Software, e incluirão todas as linhas de texto no código fonte desses módulos, independente da linguagem de programação (Python, Javascript, XML etc.), excluindo linhas em branco, linhas de comentário e arquivos que não são carregados durante a instalação ou execução do Software." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:312 +msgid "Quando o Cliente solicitar uma atualização, para cada Módulo Extra Coberto que não tenha sido coberto por uma taxa de manutenção nos últimos 12 meses, a Odoo SA poderá cobrar uma taxa extra única para cada mês de cobertura faltante." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:319 +msgid "5.2 Custos de Renovação" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:321 +msgid "Após a renovação, conforme previsto na seção :ref:`term_pt`, se os preços aplicados durante a Vigência anterior forem inferiores ao preço de tabela aplicável mais atual, tais preços aumentarão em até 7%." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:328 +msgid "5.3 Impostos" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:330 +msgid "Todas as taxas e preços não incluem quaisquer impostos, taxas ou encargos federais, provinciais, estaduais, locais ou outros aplicáveis (coletivamente, “Impostos”). O Cliente é responsável pelo pagamento de todos os Impostos associados às compras feitas pelo Cliente nos termos deste Contrato, exceto quando a Odoo SA for legalmente obrigada a pagar ou cobrar impostos pelos quais o Cliente é responsável." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:339 +msgid "6 Condições dos Serviços" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:342 +msgid "6.1 Obrigações do Cliente" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:344 +msgid "O Cliente concorda em:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:346 +msgid "pagar à Odoo SA quaisquer valores aplicáveis pelos Serviços do presente Contrato, de acordo com as condições de pagamento especificadas na assinatura deste contrato;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:348 +msgid "notificar imediatamente a Odoo SA quando seu número real de Usuários exceder o número especificado no ato da celebração do Contrato e, nesse caso, pagar a taxa adicional aplicável, conforme descrito na seção :ref:`charges_standard_pt`;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:351 +msgid "tomar todas as medidas necessárias para garantir a execução inalterada da parte do Software que verifica a validade do uso do Odoo Enterprise Edition, conforme descrito em :ref:`enterprise_access_pt`;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:354 +msgid "nomear 1 pessoa de contato dedicada ao Cliente durante toda a vigência do Contrato;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:355 +msgid "fornecer notificação por escrito à Odoo SA 30 dias antes de mudar seu ponto de contato principal para trabalhar com outro Parceiro Odoo ou para trabalhar diretamente com a Odoo SA." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:358 +msgid "Quando o Cliente opta por usar a Cloud Platform, o Cliente concorda ainda em:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:360 +msgid "tomar todas as medidas razoáveis para manter suas contas de usuário seguras, inclusive escolhendo uma senha forte e não compartilhando com ninguém;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:362 +msgid "fazer uso razoável dos Serviços de Hospedagem, renunciando quaisquer atividades ilegais ou abusivas, e observar estritamente as regras descritas na Política de Uso Aceitável publicada em https://www.odoo.com/acceptable-use." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:366 +msgid "Quando o cliente escolhe a opção de Hospedagem Própria, o cliente concorda ainda em:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:368 +msgid "tomar todas as medidas razoáveis para proteger os arquivos e bases de dados do Cliente e garantir que os dados do Cliente estejam seguros e protegidos, reconhecendo que a Odoo SA não pode ser responsabilizada por qualquer perda de dados;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:371 +msgid "conceder à Odoo SA o acesso necessário para verificar a validade do uso do Odoo Enterprise Edition mediante solicitação (por exemplo, se a validação automática for considerada inoperante para o Cliente)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:376 +msgid "6.2 Sem Aliciamento ou Contratações" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:378 +msgid "Exceto quando a outra parte der seu consentimento por escrito, cada parte, suas afiliadas e representantes concordam em não solicitar ou oferecer emprego a qualquer funcionário da outra parte que esteja envolvido na execução ou uso dos Serviços sob este Contrato, durante a vigência do Contrato e por um período de 12 meses a partir da data de rescisão ou vencimento deste Contrato. Em caso de descumprimento das condições desta seção que leve à demissão do referido funcionário para o efeito, a parte infratora obriga-se a pagar à outra parte um montante de 30 000,00 euros (€) (trinta mil euros)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:390 +msgid "6.3 Publicidade" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:392 +msgid "Exceto quando vetado através de notificação por escrito, cada parte concede à outra uma licença mundial intransferível, não exclusiva e isenta de royalties para reproduzir e exibir o nome, logotipos e marcas registradas da outra parte, exclusivamente para fins de referência à outra parte como um cliente ou fornecedor, em sites, press releases e outros materiais de marketing." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:401 +msgid "6.4 Confidencialidade" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:409 +msgid "Definição de “Informações Confidenciais”:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:404 +msgid "Todas as informações divulgadas por uma parte (a “Parte Divulgadora”) à outra parte (a “Parte Receptora”), oralmente ou por escrito, que seja designada como confidencial ou que razoavelmente deva ser entendida como confidencial, dada a natureza do informações e as circunstâncias da divulgação. Em particular, qualquer informação relacionada a negócios, assuntos, produtos, desenvolvimentos, segredos comerciais, know-how, pessoal, clientes e fornecedores de qualquer uma das partes deve ser considerada confidencial." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:411 +msgid "Para todas as Informações Confidenciais recebidas durante a Vigência deste Contrato, a Parte Receptora usará o mesmo grau de cuidado que usa para proteger a confidencialidade de suas próprias Informações Confidenciais semelhantes, mas não menos do que o cuidado razoável." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:415 +msgid "A Parte Receptora pode divulgar Informações Confidenciais da Parte Divulgadora na medida em que for obrigada por lei a fazê-lo, desde que a Parte Receptora notifique a Parte Divulgadora com antecedência sobre a divulgação obrigatória, na medida permitida por lei." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:422 +msgid "6.5 Proteção de Dados" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:427 +msgid "Definições" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:425 +msgid "\"Dados Pessoais\", \"Controlador\", \"Processamento\" têm os mesmos significados que no Regulamento (UE) 2016/679 e na Diretiva 2002/58/EC, e qualquer regulamento ou legislação que os altere ou substitua (doravante referido como \"Legislação de Proteção de Dados\")" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:430 +msgid "Processamento de Dados Pessoais" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:432 +msgid "As partes reconhecem que a base de dados do Cliente pode conter Dados Pessoais, dos quais o Cliente é o Controlador. Estes dados serão processados pela Odoo SA quando o Cliente assim o instruir, mediante a utilização de algum dos Serviços que necessitem de uma base de dados (e.g. os Serviços de Hospedagem na Nuvem ou o Serviço de Atualização da Base de Dados), ou se o Cliente transferir a sua base de dados ou parte da sua base de dados à Odoo SA por qualquer motivo relacionado a este Contrato." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:439 +msgid "Este processamento será realizado em conformidade com a Legislação de Proteção de Dados. Em particular, a Odoo SA compromete-se a:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:442 +msgid "(a) apenas processar os Dados Pessoais quando e conforme instruído pelo Cliente, e com a finalidade de executar um dos Serviços sob este Contrato, a menos que haja exigência por lei, caso em que a Odoo SA notificará o Cliente com antecedência, a não ser que a lei a proíba;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:445 +msgid "(b) garantir que todas as pessoas dentro da Odoo SA autorizadas a processar os Dados Pessoais se comprometam com a confidencialidade;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:447 +msgid "(c) implementar e manter medidas técnicas e organizacionais apropriadas para proteger os Dados Pessoais contra processamento não autorizado ou ilegal e contra perda, destruição, dano, roubo, alteração ou divulgação acidental;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:450 +msgid "(d) encaminhar prontamente ao Cliente qualquer solicitação de Proteção de Dados que tenha sido enviada à Odoo SA em relação à base de dados do Cliente;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:452 +msgid "(e) notificar o Cliente imediatamente ao tomar conhecimento e confirmar qualquer processamento acidental, não autorizado ou ilegal, divulgação ou acesso aos Dados Pessoais;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:454 +msgid "(f) notificar o Cliente se as instruções de processamento infringirem a Legislação de Proteção de Dados aplicável, na opinião da Odoo SA;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:456 +msgid "(g) disponibilizar ao Cliente todas as informações necessárias para demonstrar conformidade com a Legislação de Proteção de Dados, permitir e contribuir razoavelmente para auditorias, incluindo inspeções, conduzidas ou ordenadas pelo Cliente;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:459 +msgid "(h) excluir permanentemente todas as cópias da base de dados do Cliente em posse da Odoo SA, ou devolver tais dados, à escolha do Cliente, após a rescisão deste Contrato, sujeito aos atrasos especificados na `Política de Privacidade `_ da Odoo SA;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:464 +msgid "No que diz respeito às alíneas (d) a (f), o Cliente concorda em fornecer à Odoo SA informações de contato precisas em todos os momentos, conforme necessário para notificar o responsável pela Proteção de Dados do Cliente." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:469 +msgid "Subprocessadores" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:471 +msgid "O Cliente reconhece e concorda que, para fornecer os Serviços, a Odoo SA pode usar provedores de serviços terceirizados (Subprocessadores) para tratar Dados Pessoais. A Odoo SA compromete-se a usar apenas Subprocessadores em conformidade com a Legislação de Proteção de Dados. Esta utilização estará abrangida por um contrato entre a Odoo SA e o Subprocessador que dá garantias nesse sentido. A Política de Privacidade da Odoo SA, publicada em https://www.odoo.com/privacy, fornece informações atualizadas sobre os nomes e propósitos dos Subprocessadores atualmente em uso pela Odoo SA para a execução dos Serviços." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:483 +msgid "6.6 Cessão" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:485 +msgid "Caso qualquer uma das partes não cumpra qualquer uma de suas obrigações decorrentes deste Contrato, e se tal violação não for sanada dentro de 30 dias corridos a partir da notificação por escrito de tal violação, este Contrato poderá ser rescindido imediatamente pela parte não infratora." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:490 +msgid "Além disso, a Odoo SA pode rescindir o Contrato imediatamente caso o Cliente não pague as taxas aplicáveis pelos Serviços dentro de 21 dias após a data de vencimento especificada na fatura correspondente e após no mínimo 3 lembretes." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:497 +msgid "Cláusulas Subsistentes:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:495 +msgid "As seções \":ref:`confidentiality_pt`\", “:ref:`disclaimers_pt`\", “:ref:`liability_pt`\", e “:ref:`general_provisions_pt`\" subsistirão a qualquer rescisão ou expiração deste Contrato." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:502 +msgid "7 Garantias, Isenções de Responsabilidade, Limitação de Responsabilidade" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:507 +msgid "7.1 Garantias" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:509 +msgid "A Odoo SA detém os direitos autorais ou equivalente [#cla_pt1]_ de 100% do código do Software e confirma que todas as bibliotecas de software necessárias para usar o Software estão disponíveis sob uma licença compatível com a licença do Software." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:513 +msgid "Durante a vigência deste Contrato, a Odoo SA se compromete a realizar esforços comercialmente razoáveis para executar os Serviços de acordo com os padrões de indústria geralmente aceitos, desde que:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:517 +msgid "os sistemas computacionais do Cliente estejam em bom estado de funcionamento e, para o caso de Hospedagem Própria, o Software esteja instalado num ambiente operacional adequado;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:519 +msgid "o Cliente forneça informações adequadas de solução de problemas e, para o caso de Hospedagem Própria, qualquer acesso que a Odoo SA possa precisar para identificar, reproduzir e resolver problemas;" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:522 +msgid "todos os valores devidos à Odoo SA sejam pagos." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:524 +msgid "O único e exclusivo recurso do Cliente e a única obrigação da Odoo SA por qualquer violação desta garantia é que a Odoo SA retome a execução dos Serviços sem custo adicional." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:527 +msgid "As contribuições externas são cobertas por um `Contrato de Licença de Direitos Autorais `_ fornece uma licença permanente, gratuita e irrevogável de direitos autorais e patente para a Odoo SA." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:535 +msgid "7.2 Isenções de Responsabilidade" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:537 +msgid "Exceto conforme expressamente disposto neste documento, nenhuma das partes oferece qualquer garantia de qualquer tipo, seja expressa, implícita, estatutária ou de outra maneira, e cada parte se isenta especificamente de todas as garantias implícitas, incluindo qualquer garantia implícita de comercialização, adequação a uma finalidade específica ou não violação, na extensão máxima permitida pela lei aplicável." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:543 +msgid "A Odoo SA não garante que o Software esteja em conformidade com qualquer lei ou regulamentação local ou internacional." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:549 +msgid "7.3 Limitação de Responsabilidade" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:551 +msgid "Na extensão máxima permitida por lei, a responsabilidade agregada de cada parte juntamente com suas afiliadas, decorrente ou relacionada a este Contrato, não excederá 50% do valor total pago pelo Cliente sob este Contrato durante os 12 meses imediatamente anteriores à data do evento que deu origem a tal ação judicial. Reivindicações múltiplas não devem ampliar esta limitação." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:557 +msgid "Em nenhum caso, qualquer uma das partes ou suas afiliadas serão responsáveis por quaisquer danos indiretos, especiais, exemplares, incidentais ou consequentes de qualquer tipo, incluindo, mas não limitado a, perda de receita, lucros, economias, perda de negócios ou outras perdas financeiras, custos de paralisação ou atraso, dados perdidos ou corrompidos, decorrentes ou relacionados a este Contrato, independentemente da forma de ação, seja por contrato, ato ilícito ou não, mesmo que uma parte ou suas afiliadas tenham sido avisadas da possibilidade de tais danos, ou se o reparo de uma parte ou de suas afiliadas falhar em seu propósito essencial." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:569 +msgid "7.4 Força Maior" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:571 +msgid "Nenhuma das partes será responsável perante a outra parte pelo atraso em qualquer cumprimento ou falha em cumprir qualquer ação sob este Contrato quando tal falha ou atraso encontrar sua causa em um caso de *força maior*, como regulamentações governamentais, incêndio, greve, guerra, inundação, acidente, epidemia, embargo, apropriação total ou parcial de fábrica ou produto por qualquer governo ou autoridade pública, ou qualquer outra causa ou causas, de natureza semelhante ou diferente, fora do controle razoável de tal parte, desde que tal causa ou causas existam." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:582 +msgid "8 Disposições Gerais" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:587 +msgid "8.1 Jurisdição" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:589 +msgid "Este Contrato e todas as ordens do Cliente estarão sujeitos à lei belga. Qualquer disputa decorrente ou relacionada a este Contrato ou a qualquer ordem do Cliente estará sujeita à jurisdição exclusiva do Tribunal Comercial de Nivelles." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:596 +msgid "8.2 Independência das Disposições Contratuais" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:598 +msgid "No caso de qualquer uma ou mais das disposições deste Contrato ou qualquer aplicação do mesmo ser inválida, ilegal ou inexequível em qualquer aspecto, a validade, legalidade e aplicabilidade das demais disposições deste Contrato e qualquer aplicação do mesmo não serão de forma alguma afetadas ou prejudicadas. Ambas as partes se comprometem a substituir qualquer disposição inválida, ilegal ou inexequível deste Contrato por uma disposição válida com os mesmos efeitos e objetivos." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:608 +msgid "9 Anexo A: Licença do Odoo Enterprise Edition" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:610 +msgid "A versão Enterprise do Odoo tem a licença Odoo Enterprise Edition v1.0, que é definida da seguinte forma:" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:614 +msgid "Esta é uma tradução em português da \"Licença Odoo Enterprise Edition v1.0\". A tradução é fornecida com o intuito de facilitar a sua compreensão, mas não tem valor legal. A única referência oficial aos termos da \"Licença Odoo Enterprise Edition\" é a :ref:`versão original em inglês `" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:628 +msgid "Licença Odoo Enterprise Edition v1.0" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:630 +msgid "Este software e arquivos associados (o \"Software\") só podem ser usados (executados, modificados, executados após modificações) com uma Assinatura do Odoo Enterprise válida para o número correto de usuários." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:634 +msgid "Com um Acordo de Parceria válido com a Odoo S.A., as permissões acima também são concedidas, desde que o uso seja limitado a um ambiente de testes ou desenvolvimento." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:637 +msgid "Você pode desenvolver módulos Odoo com base no Software e distribuí-los sob a licença de sua escolha, desde que seja compatível com os termos da Licença Odoo Enterprise Edition (por exemplo: LGPL, MIT ou licenças proprietárias similares a esta)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:641 +msgid "Você pode usar módulos Odoo publicados sob qualquer licença junto com o Software, desde que a licença deles seja compatível com os termos da Licença Odoo Enterprise (incluindo, mas não se limitando a, qualquer módulo publicado na Odoo Apps Store em odoo.com/apps)." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:645 +msgid "É proibido publicar, distribuir, sublicenciar ou vender cópias do Software ou cópias modificadas do Software." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:648 +msgid "O aviso de direitos autorais acima e este aviso de permissão devem ser incluídos em todas as cópias ou partes substanciais do Software." +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:651 +msgid "O SOFTWARE É FORNECIDO \"COMO ESTÁ\", SEM GARANTIA DE QUALQUER TIPO, EXPRESSA OU IMPLÍCITA, INCLUINDO, MAS NÃO SE LIMITANDO A, GARANTIAS DE COMERCIALIZAÇÃO, ADEQUAÇÃO A UM PROPÓSITO ESPECÍFICO E NÃO VIOLAÇÃO. EM NENHUMA CIRCUNSTÂNCIA, OS AUTORES OU TITULARES DE DIREITOS AUTORAIS SERÃO RESPONSÁVEIS POR QUALQUER REIVINDICAÇÃO, DANOS OU OUTRA RESPONSABILIDADE, SEJA EM AÇÃO DE CONTRATO, DELITO OU DE OUTRA FORMA, DECORRENTE DE, OU EM CONEXÃO COM O SOFTWARE OU O USO OU OUTRAS TRANSAÇÕES NO SOFTWARE." +msgstr "" + #: ../../content/legal/terms/i18n/partnership_es.rst:5 msgid "Odoo Partnership Agreement (ES)" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:8 +#: ../../content/legal/terms/i18n/partnership_es.rst:9 +msgid "`Download PDF `_" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:11 msgid "Esta es una traducción al español del \"Odoo Partnership Agreement\". Esta traducción se proporciona con la esperanza de que facilitará la comprensión, pero no tiene valor legal. La única referencia oficial de los términos y condiciones del \"Odoo Partnership Agreement\" es :ref:`la versión original en inglés `." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:23 -msgid "Versión 8a - 2019-08-09" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:25 -#: ../../content/legal/terms/i18n/partnership_fr.rst:22 -msgid "ENTRE:" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:26 -msgid "Odoo S.A., una empresa que tiene su sede social en Chaussée de Namur, 40, 1367 Grand-Rosière," -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:27 -msgid "Bélgica, y sus filiales (en adelante denominados conjuntamente “ODOO”)" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:28 -msgid "Y:" -msgstr "" - #: ../../content/legal/terms/i18n/partnership_es.rst:29 -msgid "_____________________________________________, una empresa que tiene su domicilio social en" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:30 -#: ../../content/legal/terms/i18n/partnership_fr.rst:27 -#: ../../content/legal/terms/partnership.rst:22 -msgid "_____________________________________________________________________________________." +msgid "Versión 11 - 2023-05-19" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:31 -msgid "(en adelante denominado “EL COLABORADOR”)" +#: ../../content/legal/terms/i18n/partnership_fr.rst:27 +msgid "ENTRE:" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:32 +msgid "Odoo S.A., una empresa que tiene su sede social en Chaussée de Namur, 40, 1367 Grand-Rosière," msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:33 -msgid "ODOO y EL COLABORADOR se denominan individualmente “Parte” y conjuntamente “las Partes”." +msgid "Bélgica, y sus filiales (en adelante denominados conjuntamente “ODOO”)" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:34 +msgid "Y:" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:35 +msgid "_____________________________________________, una empresa que tiene su domicilio social en" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:36 -msgid "1 Objeto" +#: ../../content/legal/terms/i18n/partnership_fr.rst:32 +#: ../../content/legal/terms/partnership.rst:28 +msgid "_____________________________________________________________________________________." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:37 -msgid "El presente contrato tiene por objeto regular las condiciones bajo las cuales ODOO presta servicios a EL COLABORADOR, acceso al software Odoo Enterprise Edition, y bajo las cuales EL COLABORADOR cumple con las obligaciones establecidas a continuación." +msgid "(en adelante denominado “EL COLABORADOR”)" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:41 +#: ../../content/legal/terms/i18n/partnership_es.rst:39 +msgid "ODOO y EL COLABORADOR se denominan individualmente “Parte” y conjuntamente “las Partes”." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:42 +msgid "1 Objeto" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:43 +msgid "El presente Contrato tiene por objeto regular las condiciones bajo las cuales ODOO presta servicios a EL COLABORADOR, acceso al software Odoo Enterprise Edition, y bajo las cuales EL COLABORADOR cumple con las obligaciones establecidas a continuación." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:47 msgid "Por la presente ODOO nombra a EL COLABORADOR, y EL COLABORADOR acepta ser nombrado, socio no exclusivo para promover y vender “Odoo Enterprise Edition” a los clientes." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:44 +#: ../../content/legal/terms/i18n/partnership_es.rst:50 msgid "EL COLABORADOR se compromete a hacer su mejor esfuerzo para vender contratos de Odoo Enterprise a sus clientes. En apoyo a esta afirmación, EL COLABORADOR dará prioridad a la comercialización de la versión “Odoo Enterprise Edition” a clientes potenciales y clientes. EL COLABORADOR siempre tiene la posibilidad de vender servicios con otras versiones del software, como “Odoo Community Edition”, en caso de ser necesario." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:51 +#: ../../content/legal/terms/i18n/partnership_es.rst:57 msgid "2 Duración del Contrato" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:52 +#: ../../content/legal/terms/i18n/partnership_es.rst:58 msgid "La duración de este contrato será de un año (\"la Duración\") a partir de la fecha de la firma. Se renueva automáticamente por una duración igual, a menos que cualquiera de las partes notifique por escrito a la otra parte su terminación como mínimo 30 días antes del final de la duración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:57 +#: ../../content/legal/terms/i18n/partnership_es.rst:63 msgid "3 Acceso a Odoo Enterprise Edition" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:60 +#: ../../content/legal/terms/i18n/partnership_es.rst:66 msgid "3.1 Acceso a la plataforma del proyecto" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:61 +#: ../../content/legal/terms/i18n/partnership_es.rst:67 msgid "Para ayudar a EL COLABORADOR a promover Odoo Enterprise Edition, ODOO otorga a EL COLABORADOR acceso a su repositorio de código del proyecto para todas las “Aplicaciones Odoo Enterprise Edition”, en los términos establecidos en :ref:`appendix_p_a_es` y las condiciones restringidas del presente Contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:66 +#: ../../content/legal/terms/i18n/partnership_es.rst:72 msgid "Además, ODOO otorga a EL COLABORADOR acceso gratuito a la plataforma ODOO.SH con fines de prueba y desarrollo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:73 +#: ../../content/legal/terms/i18n/partnership_es.rst:75 +msgid "EL COLABORADOR no tiene permitido bloquear, restringir o limitar de ninguna manera el acceso y uso de la Licencia Odoo Enterprise Edition por parte del cliente, sin consulta previa y autorización por escrito de ODOO." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:82 msgid "3.2 Restricciones" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:74 +#: ../../content/legal/terms/i18n/partnership_es.rst:83 msgid "EL COLABORADOR se compromete a mantener la confidencialidad del código fuente de las aplicaciones Odoo Enterprise Edition entre su personal. El acceso al código fuente de Odoo Enterprise Edition para los clientes se rige por el Contrato de suscripción de Odoo Enterprise. EL COLABORADOR se compromete a NO redistribuir este código a terceros sin el permiso por escrito de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:80 +#: ../../content/legal/terms/i18n/partnership_es.rst:89 msgid "PARTNER se compromete a no ofrecer servicios en Odoo Enterprise Edition a clientes que no estén cubiertos por una suscripción de Odoo Enterprise, incluso durante la fase de implementación." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:83 +#: ../../content/legal/terms/i18n/partnership_es.rst:92 msgid "A pesar de lo anterior, EL COLABORADOR se compromete a preservar por completo la integridad del código de Odoo Enterprise Edition necesario para verificar la validez del uso de Odoo Enterprise Edition y para recopilar estadísticas necesarias para este fin." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:89 +#: ../../content/legal/terms/i18n/partnership_es.rst:98 msgid "4 Servicios de colaboración" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:92 +#: ../../content/legal/terms/i18n/partnership_es.rst:101 msgid "4.1 Niveles de colaboración" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:93 +#: ../../content/legal/terms/i18n/partnership_es.rst:102 msgid "El programa de socios de Odoo consta de dos tipos de asociaciones y cuatro niveles; \"Learning Partners\" es para empresas que desean todo lo necesario para comenzar a implementar Odoo, sin visibilidad como socio oficial hasta que obtengan la experiencia requerida; \"Official Partners\" es para empresas que desean la visibilidad como Ready, Silver y Gold, según su experiencia con Odoo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:99 -msgid "El nivel de colaboración otorgado a EL COLABORADOR depende de los ingresos anuales de Odoo Enterprise generados para ODOO (en términos de Usuarios de Odoo Enterprise vendidos). Las renovaciones de los contratos existentes no cuentan para el número de Usuarios vendidos, pero EL COLABORADOR sigue recibiendo una comisión por estos contratos, tal como se indica en la sección :ref:`benefits_es`.." +#: ../../content/legal/terms/i18n/partnership_es.rst:108 +msgid "El nivel de colaboración otorgado a EL COLABORADOR depende de los *nuevos usuarios netos de Odoo Enterprise vendidos* en los últimos 12 meses, el número de recursos certificados y la Tasa de Retención de clientes. Los *nuevos usuarios netos de Odoo Enterprise vendidos* incluyen nuevos clientes, ventas adicionales a clientes existentes, reducciones en ventas a clientes existentes y la pérdida de clientes. Las renovaciones de contratos existentes no se cuentan como parte del número de usuarios vendidos, pero EL COLABORADOR aún recibe una comisión por estos contratos según se establece en la sección :ref:`benefits_es`." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:105 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 msgid "La tabla siguiente resume los requisitos para cada nivel de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:108 -#: ../../content/legal/terms/i18n/partnership_es.rst:144 -#: ../../content/legal/terms/i18n/partnership_fr.rst:104 -#: ../../content/legal/terms/i18n/partnership_fr.rst:140 -#: ../../content/legal/terms/partnership.rst:98 -#: ../../content/legal/terms/partnership.rst:134 +#: ../../content/legal/terms/i18n/partnership_es.rst:119 +msgid "La *Tasa de Retención* de clientes se calcula dividiendo el número total de clientes de Odoo Enterprise adquiridos por EL COLABORADOR en los últimos 3 años que están actualmente activos, entre el número total de clientes de Odoo Enterprise adquiridos por EL COLABORADOR en los últimos 3 años." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:124 +#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_fr.rst:120 +#: ../../content/legal/terms/i18n/partnership_fr.rst:153 +#: ../../content/legal/terms/partnership.rst:112 +#: ../../content/legal/terms/partnership.rst:144 msgid "Learning Partner" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:108 -#: ../../content/legal/terms/i18n/partnership_es.rst:144 -#: ../../content/legal/terms/i18n/partnership_fr.rst:104 -#: ../../content/legal/terms/i18n/partnership_fr.rst:140 -#: ../../content/legal/terms/partnership.rst:98 -#: ../../content/legal/terms/partnership.rst:134 +#: ../../content/legal/terms/i18n/partnership_es.rst:124 +#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_fr.rst:120 +#: ../../content/legal/terms/i18n/partnership_fr.rst:153 +#: ../../content/legal/terms/partnership.rst:112 +#: ../../content/legal/terms/partnership.rst:144 msgid "Official: Ready" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:108 -#: ../../content/legal/terms/i18n/partnership_es.rst:144 -#: ../../content/legal/terms/i18n/partnership_fr.rst:104 -#: ../../content/legal/terms/i18n/partnership_fr.rst:140 -#: ../../content/legal/terms/partnership.rst:98 -#: ../../content/legal/terms/partnership.rst:134 +#: ../../content/legal/terms/i18n/partnership_es.rst:124 +#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_fr.rst:120 +#: ../../content/legal/terms/i18n/partnership_fr.rst:153 +#: ../../content/legal/terms/partnership.rst:112 +#: ../../content/legal/terms/partnership.rst:144 msgid "Official: Silver" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:108 -#: ../../content/legal/terms/i18n/partnership_es.rst:144 -#: ../../content/legal/terms/i18n/partnership_fr.rst:104 -#: ../../content/legal/terms/i18n/partnership_fr.rst:140 -#: ../../content/legal/terms/partnership.rst:98 -#: ../../content/legal/terms/partnership.rst:134 +#: ../../content/legal/terms/i18n/partnership_es.rst:124 +#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_fr.rst:120 +#: ../../content/legal/terms/i18n/partnership_fr.rst:153 +#: ../../content/legal/terms/partnership.rst:112 +#: ../../content/legal/terms/partnership.rst:144 msgid "Official: Gold" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:110 -msgid "Usuarios de Odoo Enterprise anuales vendidos" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:110 -#: ../../content/legal/terms/i18n/partnership_es.rst:112 -#: ../../content/legal/terms/i18n/partnership_fr.rst:106 -#: ../../content/legal/terms/i18n/partnership_fr.rst:108 -#: ../../content/legal/terms/partnership.rst:100 -#: ../../content/legal/terms/partnership.rst:102 -msgid "0" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:110 -#: ../../content/legal/terms/i18n/partnership_fr.rst:106 -#: ../../content/legal/terms/partnership.rst:100 -msgid "10" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:110 -msgid "50" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:110 -msgid "150" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:112 -msgid "Número de empleados certificados en al menos uno de las 3 últimas versiones de Odoo" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:112 -#: ../../content/legal/terms/i18n/partnership_fr.rst:108 -#: ../../content/legal/terms/partnership.rst:102 -msgid "1" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:112 -#: ../../content/legal/terms/i18n/partnership_fr.rst:108 -#: ../../content/legal/terms/partnership.rst:102 -msgid "2" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:112 -#: ../../content/legal/terms/i18n/partnership_fr.rst:108 -#: ../../content/legal/terms/partnership.rst:102 -msgid "3" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:115 -msgid "Tasa de retención mínima" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:115 -#: ../../content/legal/terms/i18n/partnership_es.rst:115 -#: ../../content/legal/terms/i18n/partnership_fr.rst:111 -#: ../../content/legal/terms/i18n/partnership_fr.rst:111 -#: ../../content/legal/terms/partnership.rst:105 -#: ../../content/legal/terms/partnership.rst:105 -msgid "n/a" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:115 -#: ../../content/legal/terms/i18n/partnership_fr.rst:111 -#: ../../content/legal/terms/partnership.rst:105 -msgid "70%" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:115 -#: ../../content/legal/terms/i18n/partnership_fr.rst:111 -#: ../../content/legal/terms/partnership.rst:105 -msgid "80%" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:118 -msgid "La Tasa de Retención se define como la relación entre el número de contratos de Odoo Enterprise que están actualmente activos y la cantidad de contratos de Odoo Enterprise que han estado activos en algún momento en los últimos 12 meses." -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:122 -msgid "Las certificaciones son personales, por lo que cuando un miembro certificado del personal deja la empresa, EL COLABORADOR debe notificarlo a ODOO para que actualice la cantidad de recursos certificados activos para el contrato de colaboración." +#: ../../content/legal/terms/i18n/partnership_es.rst:126 +msgid "Nuevos Usuarios netos de Odoo Enterprise vendidos anualmente" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:126 -msgid "ODOO revisará trimestralmente el nivel de colaboración de EL COLABORADOR y lo ajustará al nivel más alto para el cual se cumplan los 3 requisitos." +#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_fr.rst:122 +#: ../../content/legal/terms/i18n/partnership_fr.rst:125 +#: ../../content/legal/terms/partnership.rst:114 +#: ../../content/legal/terms/partnership.rst:116 +msgid "0" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_fr.rst:122 +#: ../../content/legal/terms/partnership.rst:114 +msgid "10" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:126 +msgid "50" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_fr.rst:122 +#: ../../content/legal/terms/partnership.rst:114 +msgid "300" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:129 -msgid "Sin embargo, los \"Official Partners\" pueden actualizarse automáticamente a un nivel superior una vez que alcancen los 3 requisitos para ese nivel de colaboración." +msgid "Número de empleados certificados en al menos uno de las 3 últimas versiones de Odoo" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_fr.rst:125 +#: ../../content/legal/terms/partnership.rst:116 +msgid "1" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_fr.rst:125 +#: ../../content/legal/terms/partnership.rst:116 +msgid "3" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_fr.rst:125 +#: ../../content/legal/terms/partnership.rst:116 +msgid "6" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:132 +msgid "Tasa de Retención mínima" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_fr.rst:128 +#: ../../content/legal/terms/partnership.rst:119 +msgid "n/a" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_fr.rst:128 +#: ../../content/legal/terms/partnership.rst:119 +msgid "70%" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_fr.rst:128 +#: ../../content/legal/terms/partnership.rst:119 +msgid "80%" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:135 +msgid "Las certificaciones son personales, por lo que cuando un miembro certificado del personal deja la empresa, EL COLABORADOR debe notificarlo a ODOO para que actualice la cantidad de recursos certificados activos para el contrato de colaboración." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:139 +msgid "ODOO revisará trimestralmente el nivel de colaboración de EL COLABORADOR y lo ajustará al nivel más alto para el cual se cumplan los 3 requisitos." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:142 +msgid "Sin embargo, los \"Official Partners\" pueden actualizarse automáticamente a un nivel superior una vez que alcancen los 3 requisitos para ese nivel de colaboración." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:148 msgid "4.2 Ventajas" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:137 +#: ../../content/legal/terms/i18n/partnership_es.rst:150 msgid "En la tabla siguiente se describen los detalles de las ventajas para cada nivel de colaboración:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:146 +#: ../../content/legal/terms/i18n/partnership_es.rst:159 msgid "**Reconocimiento**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:148 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 msgid "Visibilidad en odoo.com" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:148 -#: ../../content/legal/terms/i18n/partnership_es.rst:177 -#: ../../content/legal/terms/i18n/partnership_es.rst:184 -#: ../../content/legal/terms/partnership.rst:138 -#: ../../content/legal/terms/partnership.rst:168 -#: ../../content/legal/terms/partnership.rst:175 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:190 +#: ../../content/legal/terms/i18n/partnership_es.rst:197 +#: ../../content/legal/terms/partnership.rst:148 +#: ../../content/legal/terms/partnership.rst:178 +#: ../../content/legal/terms/partnership.rst:185 msgid "No" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:148 -#: ../../content/legal/terms/i18n/partnership_fr.rst:144 -#: ../../content/legal/terms/partnership.rst:138 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_fr.rst:157 +#: ../../content/legal/terms/partnership.rst:148 msgid "\"Ready Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:148 -#: ../../content/legal/terms/i18n/partnership_fr.rst:144 -#: ../../content/legal/terms/partnership.rst:138 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_fr.rst:157 +#: ../../content/legal/terms/partnership.rst:148 msgid "\"Silver Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:148 -#: ../../content/legal/terms/i18n/partnership_fr.rst:144 -#: ../../content/legal/terms/partnership.rst:138 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_fr.rst:157 +#: ../../content/legal/terms/partnership.rst:148 msgid "\"Gold Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:150 +#: ../../content/legal/terms/i18n/partnership_es.rst:163 msgid "Derechos de uso de la marca registrada “Odoo” y logotipos" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:150 -#: ../../content/legal/terms/i18n/partnership_es.rst:150 -#: ../../content/legal/terms/i18n/partnership_es.rst:150 -#: ../../content/legal/terms/i18n/partnership_es.rst:150 -#: ../../content/legal/terms/i18n/partnership_es.rst:155 -#: ../../content/legal/terms/i18n/partnership_es.rst:155 -#: ../../content/legal/terms/i18n/partnership_es.rst:155 -#: ../../content/legal/terms/i18n/partnership_es.rst:155 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 -#: ../../content/legal/terms/i18n/partnership_es.rst:161 -#: ../../content/legal/terms/i18n/partnership_es.rst:161 -#: ../../content/legal/terms/i18n/partnership_es.rst:161 -#: ../../content/legal/terms/i18n/partnership_es.rst:161 -#: ../../content/legal/terms/i18n/partnership_es.rst:164 -#: ../../content/legal/terms/i18n/partnership_es.rst:164 -#: ../../content/legal/terms/i18n/partnership_es.rst:164 -#: ../../content/legal/terms/i18n/partnership_es.rst:164 -#: ../../content/legal/terms/i18n/partnership_es.rst:167 -#: ../../content/legal/terms/i18n/partnership_es.rst:167 -#: ../../content/legal/terms/i18n/partnership_es.rst:167 -#: ../../content/legal/terms/i18n/partnership_es.rst:167 +#: ../../content/legal/terms/i18n/partnership_es.rst:163 +#: ../../content/legal/terms/i18n/partnership_es.rst:168 +#: ../../content/legal/terms/i18n/partnership_es.rst:170 +#: ../../content/legal/terms/i18n/partnership_es.rst:174 #: ../../content/legal/terms/i18n/partnership_es.rst:177 -#: ../../content/legal/terms/i18n/partnership_es.rst:177 -#: ../../content/legal/terms/i18n/partnership_es.rst:177 -#: ../../content/legal/terms/i18n/partnership_es.rst:182 -#: ../../content/legal/terms/i18n/partnership_es.rst:182 -#: ../../content/legal/terms/i18n/partnership_es.rst:182 -#: ../../content/legal/terms/i18n/partnership_es.rst:182 -#: ../../content/legal/terms/i18n/partnership_es.rst:184 -#: ../../content/legal/terms/i18n/partnership_es.rst:184 -#: ../../content/legal/terms/i18n/partnership_es.rst:184 +#: ../../content/legal/terms/i18n/partnership_es.rst:180 +#: ../../content/legal/terms/i18n/partnership_es.rst:190 +#: ../../content/legal/terms/i18n/partnership_es.rst:195 +#: ../../content/legal/terms/i18n/partnership_es.rst:197 msgid "Sí" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:153 +#: ../../content/legal/terms/i18n/partnership_es.rst:166 msgid "**Ventajas de la formación**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:155 +#: ../../content/legal/terms/i18n/partnership_es.rst:168 msgid "Coaching de ventas y webinars" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:170 msgid "Acceso a la base de conocimiento Odoo" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:159 +#: ../../content/legal/terms/i18n/partnership_es.rst:172 msgid "**Ventajas del software**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:174 msgid "Acceso al código fuente de Odoo Enterprise y repositorio Github" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:164 +#: ../../content/legal/terms/i18n/partnership_es.rst:177 msgid "Código de extensión de prueba de Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:167 +#: ../../content/legal/terms/i18n/partnership_es.rst:180 msgid "Acceso a Odoo.sh con fines de prueba y desarrollo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:170 +#: ../../content/legal/terms/i18n/partnership_es.rst:183 msgid "**Ventajas de las ventas**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:172 +#: ../../content/legal/terms/i18n/partnership_es.rst:185 msgid "Comisión por la plataforma Odoo SH [#s1]_" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:172 -#: ../../content/legal/terms/i18n/partnership_es.rst:175 -#: ../../content/legal/terms/i18n/partnership_es.rst:175 -#: ../../content/legal/terms/i18n/partnership_fr.rst:166 -#: ../../content/legal/terms/i18n/partnership_fr.rst:169 -#: ../../content/legal/terms/i18n/partnership_fr.rst:169 -#: ../../content/legal/terms/partnership.rst:161 -#: ../../content/legal/terms/partnership.rst:163 -#: ../../content/legal/terms/partnership.rst:163 +#: ../../content/legal/terms/i18n/partnership_es.rst:185 +#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_fr.rst:179 +#: ../../content/legal/terms/i18n/partnership_fr.rst:182 +#: ../../content/legal/terms/partnership.rst:171 +#: ../../content/legal/terms/partnership.rst:173 msgid "10%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:172 -#: ../../content/legal/terms/i18n/partnership_es.rst:172 -#: ../../content/legal/terms/i18n/partnership_es.rst:172 -#: ../../content/legal/terms/i18n/partnership_fr.rst:166 -#: ../../content/legal/terms/i18n/partnership_fr.rst:166 -#: ../../content/legal/terms/i18n/partnership_fr.rst:166 -#: ../../content/legal/terms/partnership.rst:161 -#: ../../content/legal/terms/partnership.rst:161 -#: ../../content/legal/terms/partnership.rst:161 -msgid "100%" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:175 -msgid "Comisión por Odoo Enterprise" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:175 -#: ../../content/legal/terms/i18n/partnership_fr.rst:169 -#: ../../content/legal/terms/partnership.rst:163 -msgid "15%" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:175 -#: ../../content/legal/terms/i18n/partnership_fr.rst:169 -#: ../../content/legal/terms/partnership.rst:163 -msgid "20%" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:177 -msgid "Acceso a un gestor de cuentas especializado y Partner Dashboard" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:180 -msgid "**Ventajas de marketing**" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:182 -msgid "Material de marketing" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:184 -msgid "Evento de EL COLABORADOR - Asistencia y promoción de ODOO" +#: ../../content/legal/terms/i18n/partnership_es.rst:185 +#: ../../content/legal/terms/i18n/partnership_fr.rst:179 +#: ../../content/legal/terms/partnership.rst:171 +msgid "50%" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:188 -msgid "hasta un máximo de 150€ (o 180 $) de comisión mensual por suscripción" +msgid "Comisión por Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:191 -msgid "4.3 Reconocimiento de socios" +#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_fr.rst:182 +#: ../../content/legal/terms/partnership.rst:173 +msgid "15%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:192 -msgid "ODOO promocionará EL COLABORADOR como socio oficial en el sitio web oficial (odoo.com)." +#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_fr.rst:182 +#: ../../content/legal/terms/partnership.rst:173 +msgid "20%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:194 -msgid "ODOO concede a EL COLABORADOR, de forma no exclusiva, el derecho a usar y reproducir el logotipo de socio de ODOO del nivel de colaboración correspondiente y el nombre “Odoo” en relación con este contrato de colaboración." +#: ../../content/legal/terms/i18n/partnership_es.rst:190 +msgid "Acceso a un gestor de cuentas especializado y Partner Dashboard" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:198 -msgid "Cada Parte se compromete a respetar todos los derechos de la otra Parte en todos los elementos mencionados en el párrafo anterior y, más concretamente, cada Parte debe abstenerse de causar cualquier analogía o crear confusión entre sus respectivas compañías en el público general, por cualquier motivo y por cualquier medio." +#: ../../content/legal/terms/i18n/partnership_es.rst:193 +msgid "**Ventajas de marketing**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:204 -msgid "4.4 Ventajas de la formación" +#: ../../content/legal/terms/i18n/partnership_es.rst:195 +msgid "Material de marketing" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:197 +msgid "Evento de EL COLABORADOR - Asistencia y promoción de ODOO" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:201 +msgid "hasta un máximo de 150€ (o $180) de comisión mensual por suscripción, o 1440€ (o $1728) de comisión anual por suscripción." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:205 -msgid "EL COLABORADOR tiene acceso a la base de conocimiento de ODOO durante la duración de este Contrato. La base de conocimiento de ODOO es una plataforma electrónica en línea que contiene un conjunto de documentos comerciales, funcionales y de marketing para ayudar a EL COLABORADOR a adquirir y aprovechar el conocimiento de Odoo, hacer crecer su negocio, atraer más clientes y crear conciencia de marca." +msgid "4.3 Reconocimiento de socios" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:211 -msgid "EL COLABORADOR podrá acceder al coaching comercial facilitado por su gestor de cuentas especializado, designado por ODOO." +#: ../../content/legal/terms/i18n/partnership_es.rst:206 +msgid "ODOO promocionará EL COLABORADOR como socio oficial en el sitio web oficial (odoo.com)." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:214 -msgid "EL COLABORADOR también tiene la opción de comprar servicios de soporte o de formación suscribiéndose a un Success Pack de Odoo, por una tarifa adicional." +#: ../../content/legal/terms/i18n/partnership_es.rst:208 +msgid "ODOO concede a EL COLABORADOR, de forma no exclusiva, el derecho a usar y reproducir el logotipo de socio de ODOO del nivel de colaboración correspondiente y el nombre “Odoo” en relación con este contrato de colaboración." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:212 +msgid "Cada Parte se compromete a respetar todos los derechos de la otra Parte en todos los elementos mencionados en el párrafo anterior y, más concretamente, cada Parte debe abstenerse de causar cualquier analogía o crear confusión entre sus respectivas compañías en el público general, por cualquier motivo y por cualquier medio." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:218 -msgid "4.5 Comisiones por los servicios de Odoo vendidos por EL COLABORADOR" +msgid "4.4 Ventajas de la formación" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:219 -msgid "Para los servicios ODOO comprados por un cliente a través de EL COLABORADOR, y siempre que el PARTNER mantenga una relación contractual con el cliente correspondiente, EL COLABORADOR ecibirá una comisión de acuerdo con la tabla de la sección :ref:`benefits_es` y su nivel de asociación en la fecha de la factura del cliente." +msgid "EL COLABORADOR tiene acceso a la base de conocimiento de ODOO durante la duración de este Contrato. La base de conocimiento de ODOO es una plataforma electrónica en línea que contiene un conjunto de documentos comerciales, funcionales y de marketing para ayudar a EL COLABORADOR a adquirir y aprovechar el conocimiento de Odoo, hacer crecer su negocio, atraer más clientes y crear conciencia de marca." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:226 -msgid "5 Tarifas" +#: ../../content/legal/terms/i18n/partnership_es.rst:225 +msgid "EL COLABORADOR podrá acceder al coaching comercial facilitado por su gestor de cuentas especializado, designado por ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:227 -msgid "EL COLABORADOR se compromete a pagar la tarifa de la colaboración al recibir la factura anual enviada por ODOO. La tarifa se especificará por escrito al momento de la firma de este contracto." +#: ../../content/legal/terms/i18n/partnership_es.rst:228 +msgid "EL COLABORADOR también tiene la opción de comprar servicios de soporte o de formación suscribiéndose a un Success Pack de Odoo, por una tarifa adicional." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:230 -msgid "EL COLABORADOR reconoce que la tarifa de colaboración mencionadas anteriormente no son reembolsables." +#: ../../content/legal/terms/i18n/partnership_es.rst:232 +msgid "4.5 Comisiones por los servicios de Odoo vendidos por EL COLABORADOR" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:233 -msgid "6 Resolución" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:234 -msgid "En el caso de que cualquiera de las Partes no cumpla con cualquiera de sus obligaciones que se derivan de este documento, y si tal incumplimiento no se ha rectificado en un período de 30 días naturales a partir de la notificación por escrito de dicho incumplimiento, la Parte que no incumplió sus obligaciones puede rescindir este contrato inmediatamente." -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:241 -msgid "Disposiciones subsistentes:" +msgid "Para los servicios ODOO comprados por un cliente a través de EL COLABORADOR, y siempre que el PARTNER mantenga una relación contractual con el cliente correspondiente, EL COLABORADOR ecibirá una comisión de acuerdo con la tabla de la sección :ref:`benefits_es` y su nivel de asociación en la fecha de la factura del cliente." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:240 -msgid "Las secciones « :ref:`restrictions_es` », « :ref:`p_liability_es` », y « :ref:`gov_law_es` » mantendrán su vigencia tras cualquier resolución o expiración de este contrato." +msgid "5 Tarifas" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:241 +msgid "EL COLABORADOR se compromete a pagar la tarifa de la colaboración al recibir la factura anual enviada por ODOO. La tarifa se especificará por escrito al momento de la firma de este contracto." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:244 -msgid "6.1 Consecuencia de la resolución" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:249 -msgid "En el momento de la resolución de este contrato, EL COLABORADOR:" +msgid "EL COLABORADOR reconoce que la tarifa de colaboración mencionadas anteriormente no son reembolsables." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:246 -msgid "no deberá utilizar más los materiales y/o la marca Odoo ni reclamar la existencia de ninguna colaboración o relación con ODOO;" +msgid "Todos los honorarios y cargos son exclusivos de todos los impuestos, tarifas o cargos gubernamentales, federales, provinciales, estatales, locales u otros aplicables (en conjunto, \"Impuestos\"). EL COLABORADOR es responsable de pagar todos los Impuestos asociados a las compras realizadas por EL COLABORADOR bajo este Contrato, excepto cuando ODOO esté legalmente obligado a pagar o recaudar Impuestos de los cuales EL COLABORADOR es responsable." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:248 -msgid "deberá cumplir con sus obligaciones durante cualquier período de aviso previo a dicha resolución;" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:249 -msgid "ya no podrá usar Odoo Enterprise para fines de desarrollo, prueba o producción" +#: ../../content/legal/terms/i18n/partnership_es.rst:253 +msgid "6 Resolución" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:254 -msgid "7 Responsabilidad e indemnizaciones" +msgid "En el caso de que cualquiera de las Partes no cumpla con cualquiera de sus obligaciones que se derivan de este documento, y si tal incumplimiento no se ha rectificado en un período de 30 días naturales a partir de la notificación por escrito de dicho incumplimiento, la Parte que no incumplió sus obligaciones puede rescindir este contrato inmediatamente." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:255 -msgid "Ambas Partes están vinculadas por una obligación de medios aquí descrita." +#: ../../content/legal/terms/i18n/partnership_es.rst:261 +msgid "Disposiciones subsistentes:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:257 -msgid "En la medida máxima permitida por la ley, la responsabilidad de ODOO por cualquier reclamo, pérdida, daño o gasto derivado de cualquier manera o bajo cualquier circunstancia del presente contrato se limitará a los daños directos demostrados, pero en ningún caso excederá por todos los eventos o series de eventos relacionados que ocasionen daños la cantidad total de las tarifas pagadas por EL COLABORADOR en el transcurso de los seis (6) meses inmediatamente anteriores a la fecha del evento que dio lugar a dicha reclamación." +#: ../../content/legal/terms/i18n/partnership_es.rst:260 +msgid "Las secciones « :ref:`restrictions_es` », « :ref:`p_liability_es` », y « :ref:`gov_law_es` » mantendrán su vigencia tras cualquier resolución o expiración de este contrato." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:264 -msgid "En ningún caso ODOO será responsable de ningún daño indirecto o consecuente, incluyendo, entre otros, reclamaciones de clientes o terceros, pérdidas de ingresos, ganancias, ahorros, pérdidas de negocios y otras pérdidas financieras, costos de paralización y retraso, datos perdidos o dañados derivados o relacionados con el cumplimiento de sus obligaciones en virtud de este contrato." +msgid "6.1 Consecuencia de la resolución" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:269 -msgid "EL COLABORADOR reconoce que no tiene ninguna expectativa y que no ha recibido garantías de recuperar ninguna inversión realizada en la ejecución de este contrato y el programa de socios de Odoo o de obtener ninguna cantidad anticipada de ganancias en virtud de este contrato." +msgid "En el momento de la resolución de este contrato, EL COLABORADOR:" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:266 +msgid "no deberá utilizar más los materiales y/o la marca Odoo ni reclamar la existencia de ninguna colaboración o relación con ODOO;" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:268 +msgid "deberá cumplir con sus obligaciones durante cualquier período de aviso previo a dicha resolución;" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:269 +msgid "ya no podrá usar Odoo Enterprise para fines de desarrollo, prueba o producción" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:274 +msgid "7 Responsabilidad e indemnizaciones" msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:275 +msgid "Ambas Partes están vinculadas por una obligación de medios aquí descrita." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:277 +msgid "En la medida máxima permitida por la ley, la responsabilidad de cada Parte por cualquier reclamo, pérdida, daño o gasto derivado de cualquier manera o bajo cualquier circunstancia del presente contrato se limitará a los daños directos demostrados, pero en ningún caso excederá por todos los eventos o series de eventos relacionados que ocasionen daños la cantidad total de las tarifas pagadas por EL COLABORADOR en el transcurso de los seis (6) meses inmediatamente anteriores a la fecha del evento que dio lugar a dicha reclamación." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:284 +msgid "En ningún caso cada Parte será responsable de ningún daño indirecto o consecuente, incluyendo, entre otros, pero no limitándose a, reclamaciones de clientes o terceros, pérdidas de ingresos, ganancias, ahorros, pérdidas de negocios y otras pérdidas financieras, costos de paralización y retraso, datos perdidos o dañados derivados o relacionados con el cumplimiento de sus obligaciones en virtud de este Contrato." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:290 +msgid "EL COLABORADOR reconoce que no tiene ninguna expectativa y que no ha recibido garantías de recuperar ninguna inversión realizada en la ejecución de este contrato y el programa de socios de Odoo o de obtener ninguna cantidad anticipada de ganancias en virtud de este contrato." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_es.rst:296 msgid "8 Imagen de marca" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:276 +#: ../../content/legal/terms/i18n/partnership_es.rst:297 msgid "La marca \"Odoo\" (incluida la palabra y sus representaciones visuales y logotipos) es exclusiva propiedad de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:279 +#: ../../content/legal/terms/i18n/partnership_es.rst:300 msgid "ODOO autoriza a PARTNER a usar la marca \"Odoo\" para promocionar sus productos y servicios, solo por la Duración del Contrato, siempre que:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:282 +#: ../../content/legal/terms/i18n/partnership_es.rst:303 msgid "no hay confusión posible de que el servicio sea proporcionado por PARTNER, no por ODOO;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:283 +#: ../../content/legal/terms/i18n/partnership_es.rst:304 msgid "PARTNER no use la palabra \"Odoo\" en el nombre de su compañía, nombre de producto, nombre de dominio y no registrar ninguna marca que la incluya." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:286 +#: ../../content/legal/terms/i18n/partnership_es.rst:307 msgid "Ambas Partes se abstendrán de dañar de ninguna manera la imagen de marca y la reputación de la otra Parte en el cumplimiento de este contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:289 +#: ../../content/legal/terms/i18n/partnership_es.rst:310 msgid "El incumplimiento de las disposiciones de esta sección será causa de resolución de este Contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:293 +#: ../../content/legal/terms/i18n/partnership_es.rst:314 msgid "8.1 Publicidad" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:294 +#: ../../content/legal/terms/i18n/partnership_es.rst:315 msgid "EL COLABORADOR concede a ODOO el derecho no exclusivo de utilizar el nombre y las marcas comerciales de EL COLABORADOR en comunicados de prensa, promociones u otros anuncios públicos. En concreto, EL COLABORADOR acepta que se le mencione, y que el logotipo y la marca comercial de EL COLABORADOR se use solo para este fin, en la lista oficial de socios de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:302 +#: ../../content/legal/terms/i18n/partnership_es.rst:323 msgid "8.2 No captación o contratación" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:303 +#: ../../content/legal/terms/i18n/partnership_es.rst:324 msgid "Excepto cuando la otra Parte dé su consentimiento por escrito, cada Parte, sus afiliados y representantes acuerdan no captar u ofrecer empleo a ningún empleado de la otra Parte que participe en la realización o uso de los servicios de este contrato, durante la duración de este contrato y por un período de 24 meses a partir de la fecha de resolución o expiración de este contrato. En caso de cualquier incumplimiento de las condiciones de esta sección que conduzca al despido de dicho empleado con este objetivo, la Parte incumplidora se compromete a pagar a la otra parte la cantidad de 30 000,00 EUR (€) (treinta mil euros)." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:314 +#: ../../content/legal/terms/i18n/partnership_es.rst:335 msgid "8.3 Contratistas independientes" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:315 +#: ../../content/legal/terms/i18n/partnership_es.rst:336 msgid "Las Partes son contratistas independientes, y este contrato no debe interpretarse como la configuración de cualquier Parte como socia, empresa conjunta o fiduciaria de la otra, como la creación de otra forma de asociación legal que exigiría responsabilidad a una Parte por la acción o la falta de acción de la otra, o como la prestación a cada Parte del derecho, poder o autoridad (expresa o implícita) para crear cualquier deber u obligación de la otra." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:325 +#: ../../content/legal/terms/i18n/partnership_es.rst:346 msgid "9 Ley y jurisdicción aplicables" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:326 +#: ../../content/legal/terms/i18n/partnership_es.rst:347 msgid "Este contrato se rige y se interpreta de acuerdo con las leyes de Bélgica. Todas las disputas que surjan en relación con este contrato para las que no se pueda encontrar una solución amistosa serán resueltas definitivamente en los Tribunales de Bélgica en Nivelles." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:346 -#: ../../content/legal/terms/i18n/partnership_es.rst:None +#: ../../content/legal/terms/i18n/partnership_es.rst:-1 +#: ../../content/legal/terms/i18n/partnership_es.rst:367 msgid "Firmas" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:348 +#: ../../content/legal/terms/i18n/partnership_es.rst:369 msgid "Por ODOO," msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:348 +#: ../../content/legal/terms/i18n/partnership_es.rst:369 msgid "Por EL COLABORADOR" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:356 +#: ../../content/legal/terms/i18n/partnership_es.rst:377 msgid "|vnegspace| |hspace| Por ODOO, |hspace| Por EL COLABORADOR, |vspace|" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:364 +#: ../../content/legal/terms/i18n/partnership_es.rst:385 msgid "10 Anexo A: Licencia Odoo Enterprise Edition" msgstr "" @@ -3579,505 +4468,485 @@ msgstr "" msgid "Odoo Partnership Agreement (FR)" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:8 +#: ../../content/legal/terms/i18n/partnership_fr.rst:9 +msgid "`Download PDF `_" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:11 msgid "Ceci est une traduction en français du contrat “Odoo Partnership Agreement”. Cette traduction est fournie dans l’espoir qu’elle facilitera sa compréhension, mais elle n'a aucune valeur légale. La seule référence officielle des termes du contrat “Odoo Partnership Agreement” est la :ref:`version originale en anglais `." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:20 -#: ../../content/legal/terms/partnership.rst:15 -msgid "Version 9b - 2021-01-12" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:23 -msgid "Odoo S.A., une entreprise dont le siège social se situe Chaussée de Namur, 40," -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:24 -msgid "1367 Grand-Rosière, Belgique, et ses filialies (désignées collectivement « ODOO »)" -msgstr "" - #: ../../content/legal/terms/i18n/partnership_fr.rst:25 -msgid "ET:" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:26 -msgid "_____________________________________________, une entreprise dont le siège social se situe à" +#: ../../content/legal/terms/partnership.rst:21 +msgid "Version 11 - 2023-05-19" msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:28 -msgid "(ci-après dénommée « PARTENAIRE »)" +msgid "Odoo S.A., une entreprise dont le siège social se situe Chaussée de Namur, 40," +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:29 +msgid "1367 Grand-Rosière, Belgique, et ses filialies (désignées collectivement « ODOO »)" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:30 +msgid "ET:" msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:31 -msgid "ODOO et PARTENAIRE sont désignées individuellement par le terme « Partie » et collectivement par le terme « les Parties »." +msgid "_____________________________________________, une entreprise dont le siège social se situe à" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:35 -msgid "1 Objectif" +#: ../../content/legal/terms/i18n/partnership_fr.rst:33 +msgid "(ci-après dénommée « PARTENAIRE »)" msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:36 -msgid "L’objectif de ce Contrat est de présenter les conditions auxquelles ODOO fournit des services au PARTENAIRE et l’accès au logiciel Odoo Enterprise Edition, et en vertu desquelles le PARTENAIRE se plie aux obligations énoncées ci-après." +msgid "ODOO et PARTENAIRE sont désignées individuellement par le terme « Partie » et collectivement par le terme « les Parties »." msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:40 +msgid "1 Objectif" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:41 +msgid "L’objectif de ce Contrat est de présenter les conditions auxquelles ODOO fournit des services au PARTENAIRE et l’accès au logiciel Odoo Enterprise Edition, et en vertu desquelles le PARTENAIRE se plie aux obligations énoncées ci-après." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:45 msgid "Par le présent accord, ODOO désigne le PARTENAIRE, désignation acceptée par le PARTENAIRE, comme partenaire non exclusif pour promouvoir et vendre « Odoo Enterprise Edition » à des clients." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:43 +#: ../../content/legal/terms/i18n/partnership_fr.rst:48 msgid "Le PARTENAIRE s’engage à faire tous les efforts possibles pour vendre des contrats Odoo Enterprise à ses clients. Pour étayer ces efforts, le PARTENAIRE commercialisera en priorité la version « Odoo Enterprise Edition » aux prospects et clients. Si nécessaire, le PARTENAIRE peut vendre des services sur d’autres versions du logiciel, comme « Odoo Community Edition »." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:49 +#: ../../content/legal/terms/i18n/partnership_fr.rst:54 msgid "2 Durée du Contrat" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:50 +#: ../../content/legal/terms/i18n/partnership_fr.rst:55 msgid "Ce Contrat restera en vigueur pendant un an (la « Durée ») à compter de la date de la signature. Il est automatiquement renouvelé pour une Durée équivalente, à moins qu’une partie transmette à l’autre partie une dénonciation écrite au moins 30 jours avant la fin de la Durée." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:56 +#: ../../content/legal/terms/i18n/partnership_fr.rst:61 msgid "3 Accès à Odoo Enterprise Edition" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:59 +#: ../../content/legal/terms/i18n/partnership_fr.rst:64 msgid "3.1 Accès à la plate-forme projet" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:60 +#: ../../content/legal/terms/i18n/partnership_fr.rst:65 msgid "Pour aider le PARTENAIRE à promouvoir Odoo Enterprise Edition, ODOO octroie au PARTENAIRE l’accès à son dépôt de code pour toutes les « Apps Odoo Enterprise Edition » sous les conditions présentées dans :ref:`appendix_p_a_fr` et les conditions reprises dans ce Contrat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:64 +#: ../../content/legal/terms/i18n/partnership_fr.rst:69 msgid "ODOO accorde aussi au PARTENAIRE un accès gratuit à la plate-forme ODOO.SH, exclusivement dans un but de test et de développement." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:70 -#: ../../content/legal/terms/partnership.rst:64 +#: ../../content/legal/terms/i18n/partnership_fr.rst:75 +#: ../../content/legal/terms/partnership.rst:70 msgid "3.2 Restrictions" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:71 +#: ../../content/legal/terms/i18n/partnership_fr.rst:76 msgid "Le PARTENAIRE s’engage à maintenir la confidentialité du code source des Apps Odoo Enterprise Edition au sein de son personnel. L’accès au code source d’Odoo Enterprise Edition pour les clients est régi par l'Odoo Enterprise Subscription Agreement. Le PARTENAIRE s'engage à ne PAS redistribuer ce code à un tiers sans l’autorisation écrite d’ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:76 +#: ../../content/legal/terms/i18n/partnership_fr.rst:81 msgid "Le PARTENAIRE s'engage à n'offrir des services relatifs à Odoo Enterprise Edition qu'aux clients qui disposent d'un contrat Odoo Enterprise valide, et ce même pendant la phase d'implémentation." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:79 +#: ../../content/legal/terms/i18n/partnership_fr.rst:84 msgid "Nonobstant ce qui précède, le PARTENAIRE s’engage à préserver totalement l’intégrité du code d’Odoo Enterprise Edition requis pour vérifier la validité de l’utilisation d’Odoo Enterprise Edition et recueillir les données statistiques nécessaires à cette fin." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:84 +#: ../../content/legal/terms/i18n/partnership_fr.rst:88 +msgid "Le PARTENAIRE n'est pas autorisé à bloquer, restreindre ou limiter d'aucune manière l'accès et l'usage de la licence Odoo Enterprise Edition pour les clients, sauf en cas de consultation préalable et accord écrit d'ODOO." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:93 msgid "4 Services du partenariat" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:87 +#: ../../content/legal/terms/i18n/partnership_fr.rst:96 msgid "4.1 Niveaux de partenariat" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:88 +#: ../../content/legal/terms/i18n/partnership_fr.rst:97 msgid "Le programme partenaire d’Odoo consiste en deux types de partenariat et quatre niveaux. Le type “Learning Partners” est prévu les sociétés souhaitent démarrer la mise en oeuvre d'Odoo, mais sans la visibilité d'un partenaire officiel, en attendant d'acquérir l'expérience requise; tandis qu' \"Official Partners\" est prévu pour les sociétés qui veulent la visibilité en tant que partenaire Ready, Silver ou Gold, suivant leur niveau d'expérience." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:94 -msgid "Le niveau de partenariat accordé au PARTENAIRE dépend des nouvelles recettes annuelles Odoo Enterprise générées par le PARTENAIRE pour ODOO (en terme du nombre de nouveaux utilisateur Odoo Enterprise vendus), du nombre de ressources internes certifiées, et du taux de rétention de clients. Les renouvellements de contrats existants n’entrent pas en ligne de compte pour le nombre de nouveaux utilisateurs vendus, mais le PARTENAIRE reçoit tout de même une commission sur ces contrats, comme indiqué dans la section :ref:`benefits_fr`." +#: ../../content/legal/terms/i18n/partnership_fr.rst:103 +msgid "Le niveau de partenariat accordé au PARTENAIRE dépend du *nombre net de nouveaux utilisateurs Odoo Enterprise vendus* au cours des 12 derniers mois, du nombre de ressources internes certifiées, et du Taux de Rétention de clients. Le *nombre net de nouveaux utilisateurs Odoo Enterprise vendus* comprend les nouveaux clients, les ventes supplémentaires aux clients existants, les ventes réduites aux clients existants ainsi que la perte de clients." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:101 +#: ../../content/legal/terms/i18n/partnership_fr.rst:109 +msgid "Les renouvellements des contrats existants ne sont pas pris en compte dans le nombre d'utilisateurs vendus, mais le PARTENAIRE reçoit toujours une commission sur ces contrats, comme indiqué à la section :ref:`benefits_fr`." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:113 msgid "Le tableau ci-dessous résume les exigences pour chaque niveau de partenariat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:106 -msgid "Nouveaux utilisateurs Odoo Enterprise vendus" +#: ../../content/legal/terms/i18n/partnership_fr.rst:115 +msgid "Le *Taux de Rétention* de clients est calculé en divisant le nombre total de clients Odoo Enterprise acquis par le PARTENAIRE au cours des 3 dernières années et actuellement actifs par le nombre total de clients Odoo Enterprise acquis par le PARTENAIRE au cours des 3 dernières années." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:106 -#: ../../content/legal/terms/partnership.rst:100 +#: ../../content/legal/terms/i18n/partnership_fr.rst:122 +msgid "Nouveaux utilisateurs net Odoo Enterprise vendus annuellement" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:122 +#: ../../content/legal/terms/partnership.rst:114 msgid "75" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:106 -#: ../../content/legal/terms/partnership.rst:100 -msgid "200" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:108 +#: ../../content/legal/terms/i18n/partnership_fr.rst:125 msgid "Nombre d'employés certifiés sur au moins une des 3 dernières version d'Odoo" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:111 +#: ../../content/legal/terms/i18n/partnership_fr.rst:128 msgid "Taux de Rétention minimum" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:114 -msgid "Le Taux de Rétention est défini comme le rapport entre le nombre de contrats Odoo Enterprise qui sont toujours en cours, et le nombre de contrats Odoo Enterprise qui ont été actifs à un moment au cours des 12 derniers mois." -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:118 +#: ../../content/legal/terms/i18n/partnership_fr.rst:131 msgid "Les certifications sont personnelles, donc lorsqu’un membre du personnel quitte ou rejoint l’entreprise, le PARTENAIRE doit en informer ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:121 +#: ../../content/legal/terms/i18n/partnership_fr.rst:134 msgid "Le niveau de partenariat du PARTENAIRE sera revu trimestriellement par ODOO, et ajusté au plus haut niveau pour lequel les 3 exigences sont atteintes." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:124 +#: ../../content/legal/terms/i18n/partnership_fr.rst:137 msgid "Cependant les \"Official Partners\" pourront monter de niveau de partenariat dès qu’ils répondent aux 3 exigences pour ce niveau." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:131 +#: ../../content/legal/terms/i18n/partnership_fr.rst:144 msgid "4.2 Avantages" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:133 +#: ../../content/legal/terms/i18n/partnership_fr.rst:146 msgid "Les avantages de chaque niveau de partenariat sont détaillés dans le tableau ci-dessous :" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:142 +#: ../../content/legal/terms/i18n/partnership_fr.rst:155 msgid "**Reconnaissance**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:144 +#: ../../content/legal/terms/i18n/partnership_fr.rst:157 msgid "Visibilité sur odoo.com" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:144 -#: ../../content/legal/terms/i18n/partnership_fr.rst:174 -#: ../../content/legal/terms/i18n/partnership_fr.rst:181 +#: ../../content/legal/terms/i18n/partnership_fr.rst:157 +#: ../../content/legal/terms/i18n/partnership_fr.rst:187 +#: ../../content/legal/terms/i18n/partnership_fr.rst:194 msgid "Non" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:146 +#: ../../content/legal/terms/i18n/partnership_fr.rst:159 msgid "Droit d’utiliser la marque déposée et les logos" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:146 -#: ../../content/legal/terms/i18n/partnership_fr.rst:146 -#: ../../content/legal/terms/i18n/partnership_fr.rst:146 -#: ../../content/legal/terms/i18n/partnership_fr.rst:146 -#: ../../content/legal/terms/i18n/partnership_fr.rst:151 -#: ../../content/legal/terms/i18n/partnership_fr.rst:151 -#: ../../content/legal/terms/i18n/partnership_fr.rst:151 -#: ../../content/legal/terms/i18n/partnership_fr.rst:151 -#: ../../content/legal/terms/i18n/partnership_fr.rst:153 -#: ../../content/legal/terms/i18n/partnership_fr.rst:153 -#: ../../content/legal/terms/i18n/partnership_fr.rst:153 -#: ../../content/legal/terms/i18n/partnership_fr.rst:153 -#: ../../content/legal/terms/i18n/partnership_fr.rst:157 -#: ../../content/legal/terms/i18n/partnership_fr.rst:157 -#: ../../content/legal/terms/i18n/partnership_fr.rst:157 -#: ../../content/legal/terms/i18n/partnership_fr.rst:157 #: ../../content/legal/terms/i18n/partnership_fr.rst:159 -#: ../../content/legal/terms/i18n/partnership_fr.rst:159 -#: ../../content/legal/terms/i18n/partnership_fr.rst:159 -#: ../../content/legal/terms/i18n/partnership_fr.rst:159 -#: ../../content/legal/terms/i18n/partnership_fr.rst:161 -#: ../../content/legal/terms/i18n/partnership_fr.rst:161 -#: ../../content/legal/terms/i18n/partnership_fr.rst:161 -#: ../../content/legal/terms/i18n/partnership_fr.rst:161 +#: ../../content/legal/terms/i18n/partnership_fr.rst:164 +#: ../../content/legal/terms/i18n/partnership_fr.rst:166 +#: ../../content/legal/terms/i18n/partnership_fr.rst:170 +#: ../../content/legal/terms/i18n/partnership_fr.rst:172 #: ../../content/legal/terms/i18n/partnership_fr.rst:174 -#: ../../content/legal/terms/i18n/partnership_fr.rst:174 -#: ../../content/legal/terms/i18n/partnership_fr.rst:174 -#: ../../content/legal/terms/i18n/partnership_fr.rst:179 -#: ../../content/legal/terms/i18n/partnership_fr.rst:179 -#: ../../content/legal/terms/i18n/partnership_fr.rst:179 -#: ../../content/legal/terms/i18n/partnership_fr.rst:179 -#: ../../content/legal/terms/i18n/partnership_fr.rst:181 -#: ../../content/legal/terms/i18n/partnership_fr.rst:181 -#: ../../content/legal/terms/i18n/partnership_fr.rst:181 +#: ../../content/legal/terms/i18n/partnership_fr.rst:187 +#: ../../content/legal/terms/i18n/partnership_fr.rst:192 +#: ../../content/legal/terms/i18n/partnership_fr.rst:194 msgid "Oui" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:149 +#: ../../content/legal/terms/i18n/partnership_fr.rst:162 msgid "**Avantages formation**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:151 +#: ../../content/legal/terms/i18n/partnership_fr.rst:164 msgid "Coaching Vente & Webinars" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:153 +#: ../../content/legal/terms/i18n/partnership_fr.rst:166 msgid "Accès à la base de connaissances Odoo" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:155 +#: ../../content/legal/terms/i18n/partnership_fr.rst:168 msgid "**Avantages logiciel**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:157 +#: ../../content/legal/terms/i18n/partnership_fr.rst:170 msgid "Accès au code source Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:159 +#: ../../content/legal/terms/i18n/partnership_fr.rst:172 msgid "Code extension d'essai Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:161 +#: ../../content/legal/terms/i18n/partnership_fr.rst:174 msgid "Accès à Odoo.SH dans un but de test ou de développement" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:164 +#: ../../content/legal/terms/i18n/partnership_fr.rst:177 msgid "**Avantages Ventes**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:166 +#: ../../content/legal/terms/i18n/partnership_fr.rst:179 msgid "Commission sur la plateforme Odoo SH [#s1f]_" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:169 +#: ../../content/legal/terms/i18n/partnership_fr.rst:182 msgid "Commission sur Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:171 +#: ../../content/legal/terms/i18n/partnership_fr.rst:184 msgid "Commission sur la Maintenance de Modules Supplémentaires" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:171 -#: ../../content/legal/terms/i18n/partnership_fr.rst:171 -#: ../../content/legal/terms/i18n/partnership_fr.rst:171 -#: ../../content/legal/terms/i18n/partnership_fr.rst:171 -#: ../../content/legal/terms/partnership.rst:165 -#: ../../content/legal/terms/partnership.rst:165 -#: ../../content/legal/terms/partnership.rst:165 -#: ../../content/legal/terms/partnership.rst:165 +#: ../../content/legal/terms/i18n/partnership_fr.rst:184 +#: ../../content/legal/terms/partnership.rst:175 msgid "82%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:174 +#: ../../content/legal/terms/i18n/partnership_fr.rst:187 msgid "Accès à un Account Manager dédié et au Tableau de Bord Partenaire" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:177 +#: ../../content/legal/terms/i18n/partnership_fr.rst:190 msgid "**Avantages marketing**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:179 +#: ../../content/legal/terms/i18n/partnership_fr.rst:192 msgid "Accès au matériel de marketing" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:181 +#: ../../content/legal/terms/i18n/partnership_fr.rst:194 msgid "Événement PARTENAIRE - ODOO support & promotion" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:185 -msgid "jusqu'à un maximum de 150€ (ou 180$) de commission mensuelle par contrat Odoo.SH." -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:189 -msgid "4.3 Reconnaissance du partenaire" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:190 -msgid "ODOO promouvra les \"Official Partners\" dans la liste des partenaires Odoo sur odoo.com." -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:192 -msgid "ODOO octroie au PARTENAIRE, sur une base non exclusive, le droit d’utiliser et de reproduire le logo partenaire d’ODOO du niveau de partenariat correspondant et le nom « Odoo » en relation avec ce Contrat de partenariat." -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:196 -msgid "Chacune des Parties s’engage à respecter les droits de l’autre Partie pour tous les éléments repris dans le paragraphe précédent et s’abstiendra plus particulièrement de créer des analogies ou une confusion entre leurs entreprises respectives dans l’esprit du grand public, pour quelque raison et par quelque moyen que ce soit." +#: ../../content/legal/terms/i18n/partnership_fr.rst:198 +msgid "jusqu'à un maximum de 150€ (ou $180) de commission mensuelle par contrat Odoo.SH, ou 1440€ (ou $1728) de commission annuelle par contrat Odoo.SH." msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:202 -msgid "4.4 Avantages formation" +msgid "4.3 Reconnaissance du partenaire" msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:203 -msgid "Le PARTENAIRE a accès à la base de connaissances d’ODOO pour toute la durée de ce Contrat. La base de connaissance d’ODOO est une plateforme en ligne reprenant une série de documents commerciaux, marketing et de documentation sur les fonctionnalités, pour aider le PARTENAIRE à engranger et exploiter des connaissances Odoo, étendre son entreprise, attirer davantage de clients et augmenter la visibilité de sa marque." +msgid "ODOO promouvra les \"Official Partners\" dans la liste des partenaires Odoo sur odoo.com." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:205 +msgid "ODOO octroie au PARTENAIRE, sur une base non exclusive, le droit d’utiliser et de reproduire le logo partenaire d’ODOO du niveau de partenariat correspondant et le nom « Odoo » en relation avec ce Contrat de partenariat." msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:209 -msgid "Le PARTENAIRE aura accès à un coaching commercial fourni par son Account Manager dédié désigné par ODOO." +msgid "Chacune des Parties s’engage à respecter les droits de l’autre Partie pour tous les éléments repris dans le paragraphe précédent et s’abstiendra plus particulièrement de créer des analogies ou une confusion entre leurs entreprises respectives dans l’esprit du grand public, pour quelque raison et par quelque moyen que ce soit." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:212 -msgid "Le PARTENAIRE a également la possibilité d'acheter des services de support ou de formation en souscrivant à un Odoo Success Pack, moyennant un supplément." +#: ../../content/legal/terms/i18n/partnership_fr.rst:215 +msgid "4.4 Avantages formation" msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:216 -msgid "4.5 Commissions sur les Services Odoo vendus par le PARTENAIRE" -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_fr.rst:217 -msgid "Pour les services ODOO achetés par un client par le biais du PARTENAIRE, et pour autant que le PARTENAIRE maintienne une relation contractuelle avec ce client, le PARTENAIRE recevra une commission en fonction du tableau de la section :ref:`benefits_fr` et du niveau de partenariat à la date de la facture client correspondante." +msgid "Le PARTENAIRE a accès à la base de connaissances d’ODOO pour toute la durée de ce Contrat. La base de connaissance d’ODOO est une plateforme en ligne reprenant une série de documents commerciaux, marketing et de documentation sur les fonctionnalités, pour aider le PARTENAIRE à engranger et exploiter des connaissances Odoo, étendre son entreprise, attirer davantage de clients et augmenter la visibilité de sa marque." msgstr "" #: ../../content/legal/terms/i18n/partnership_fr.rst:222 +msgid "Le PARTENAIRE aura accès à un coaching commercial fourni par son Account Manager dédié désigné par ODOO." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:225 +msgid "Le PARTENAIRE a également la possibilité d'acheter des services de support ou de formation en souscrivant à un Odoo Success Pack, moyennant un supplément." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:229 +msgid "4.5 Commissions sur les Services Odoo vendus par le PARTENAIRE" +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:230 +msgid "Pour les services ODOO achetés par un client par le biais du PARTENAIRE, et pour autant que le PARTENAIRE maintienne une relation contractuelle avec ce client, le PARTENAIRE recevra une commission en fonction du tableau de la section :ref:`benefits_fr` et du niveau de partenariat à la date de la facture client correspondante." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:235 msgid "Une fois par mois, le PARTENAIRE recevra un bon de commande pour la commission due pour le mois précédent. Sur base de ce bon de commande, le PARTENAIRE facturera ODOO, et sera payé dans un délai de 15 jours suivant la réception de cette facture." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:226 -#: ../../content/legal/terms/partnership.rst:218 +#: ../../content/legal/terms/i18n/partnership_fr.rst:239 +#: ../../content/legal/terms/partnership.rst:229 msgid "**Maintenance of Covered Extra Modules**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:228 +#: ../../content/legal/terms/i18n/partnership_fr.rst:241 msgid "Le PARTENAIRE comprend et accepte que lorsqu'un client choisit de Collaborer avec le PARTENAIRE, ODOO lui déléguera la Maintenance des Modules Supplémentaires Couverts [#pcom_fr1]_, et qu'il deviendra le point de contact principal du client." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:232 +#: ../../content/legal/terms/i18n/partnership_fr.rst:245 msgid "Le PARTENAIRE ne recevra de commission pour la Maintenance des Modules Supplémentaires Couverts que pour autant que le client ne signale pas à ODOO sa volonté d'arrêter de Collaborer avec le PARTENAIRE." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:237 +#: ../../content/legal/terms/i18n/partnership_fr.rst:250 msgid "“Collaborer avec un Partenaire Odoo” et “Modules Supplémentaires Couverts” sont définis dans le contrat \"Odoo Enterprise Subscription Agreement\" entre ODOO et le client." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:242 +#: ../../content/legal/terms/i18n/partnership_fr.rst:255 msgid "5 Frais" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:243 +#: ../../content/legal/terms/i18n/partnership_fr.rst:256 msgid "Le PARTENAIRE s’engage à payer les frais annuels de Partenariat à la réception de la facture annuelle envoyée par ODOO. Ces frais seront spécifiés par écrit au moment de la signature de ce Contrat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:247 +#: ../../content/legal/terms/i18n/partnership_fr.rst:260 msgid "Le PARTENAIRE accepte que les frais de partenariat susmentionnés ne soient pas remboursables." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:251 +#: ../../content/legal/terms/i18n/partnership_fr.rst:262 +msgid "Tous les frais et tarifs sont indiqués hors taxes, frais et charges fédérales, provinciales, locales ou autres taxes gouvernementales applicables (collectivement, les \"Taxes\"). Le PARTENAIRE est responsable du paiement de toutes les Taxes liées aux achats effectués par le PARTENAIRE en vertu de ce Contrat, sauf lorsque ODOO est légalement tenu de payer ou de percevoir les Taxes dont le PARTENAIRE est responsable." +msgstr "" + +#: ../../content/legal/terms/i18n/partnership_fr.rst:269 msgid "6 Résiliation" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:252 +#: ../../content/legal/terms/i18n/partnership_fr.rst:270 msgid "Dans le cas où l’une des Parties ne remplirait pas l’une des obligations mentionnées ici et qu’un tel manquement ne serait remédié dans les 30 jours calendrier suivant la communication écrite d’un tel manquement, la Partie non fautive peut mettre un terme immédiat à ce Contrat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:258 +#: ../../content/legal/terms/i18n/partnership_fr.rst:276 msgid "Maintien des dispositions:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:257 +#: ../../content/legal/terms/i18n/partnership_fr.rst:275 msgid "Les sections « :ref:`restrictions_fr` », « :ref:`p_liability_fr` », et « :ref:`gov_law_fr` » seront maintenues après expiration ou résiliation de ce Contrat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:261 +#: ../../content/legal/terms/i18n/partnership_fr.rst:279 msgid "6.1 Conséquences de la résiliation" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:267 +#: ../../content/legal/terms/i18n/partnership_fr.rst:285 msgid "À l’expiration ou la résiliation de ce Contrat, le PARTENAIRE :" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:263 +#: ../../content/legal/terms/i18n/partnership_fr.rst:281 msgid "n’utilisera plus le matériel et le nom de marque d’Odoo et ses marques déposées, et ne revendiquera plus l’existence d’un partenariat ou d’une relation quelconque avec ODOO ;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:265 +#: ../../content/legal/terms/i18n/partnership_fr.rst:283 msgid "respectera ses engagements pendant toute période de préavis précédant une telle résiliation ;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:266 +#: ../../content/legal/terms/i18n/partnership_fr.rst:284 msgid "ne pourra plus utiliser Odoo Enterprise, que ce soit à des fins de développement, de test ou de production." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:272 +#: ../../content/legal/terms/i18n/partnership_fr.rst:290 msgid "7 Responsabilité et Indemnités" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:273 +#: ../../content/legal/terms/i18n/partnership_fr.rst:291 msgid "Les deux Parties sont liées par l’obligation de moyens ci-après." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:275 -msgid "Dans les limites autorisées par la loi, la responsabilité d’ODOO pour quelque réclamation, perte, dommage ou dépense que ce soit découlant de n’importe quelle cause et survenant de quelque manière que ce soit dans le cadre de ce Contrat sera limitée aux dommages directs prouvés, mais ne dépassera en aucun cas, pour tous les événements ou séries d’événements connexes entraînant des dommages, le montant total des frais payés par le PARTENAIRE au cours de six (6) mois précédant immédiatement la date de l’événement donnant naissance à une telle plainte." +#: ../../content/legal/terms/i18n/partnership_fr.rst:293 +msgid "Dans les limites autorisées par la loi, la responsabilité de chaque Partie pour quelque réclamation, perte, dommage ou dépense que ce soit découlant de n’importe quelle cause et survenant de quelque manière que ce soit dans le cadre de ce Contrat sera limitée aux dommages directs prouvés, mais ne dépassera en aucun cas, pour tous les événements ou séries d’événements connexes entraînant des dommages, le montant total des frais payés par le PARTENAIRE au cours de six (6) mois précédant immédiatement la date de l’événement donnant naissance à une telle plainte." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:282 -msgid "En aucun cas, ODOO ne sera responsable pour tout dommage indirect ou consécutif, y compris, mais sans s’y restreindre, aux plaintes, pertes de revenu, de recettes, d’économies, d’entreprise ou autre perte financière, coûts d’arrêt ou de retard, pertes de données ou données corrompues de tiers ou de clients résultant de ou en lien avec l’exécution de ses obligations dans le cadre de ce Contrat." +#: ../../content/legal/terms/i18n/partnership_fr.rst:300 +msgid "En aucun cas chaque Partie ne sera responsable pour tout dommage indirect ou consécutif, y compris, mais sans s’y restreindre, aux plaintes, pertes de revenu, de recettes, d’économies, d’entreprise ou autre perte financière, coûts d’arrêt ou de retard, pertes de données ou données corrompues de tiers ou de clients résultant de ou en lien avec l’exécution de ses obligations dans le cadre de ce Contrat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:288 +#: ../../content/legal/terms/i18n/partnership_fr.rst:306 msgid "Le PARTENAIRE comprend qu’il n’a aucune attente et n’a reçu aucune assurance qu’un investissement effectué dans l’exécution de ce Contrat et du Programme de partenariat d’Odoo sera récupéré ou recouvert ou qu’il obtiendra un quelconque montant de bénéfices anticipé en vertu de ce Contrat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:294 +#: ../../content/legal/terms/i18n/partnership_fr.rst:312 msgid "8 Image de marque" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:296 +#: ../../content/legal/terms/i18n/partnership_fr.rst:314 msgid "La marque \"Odoo\" (y compris le nom et ses représentations visuelles et logos) est la propriété exclusive d'ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:299 +#: ../../content/legal/terms/i18n/partnership_fr.rst:317 msgid "ODOO autorise le PARTENAIRE à utiliser la marque \"Odoo\" pour promouvoir ses produits et services, pour la Durée de ce Contrat seulement, et tant que les conditions suivantes sont remplies:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:302 +#: ../../content/legal/terms/i18n/partnership_fr.rst:320 msgid "Aucune confusion n'est possible sur le fait que les services sont fournis par le PARTENAIRE, et non par ODOO;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:304 +#: ../../content/legal/terms/i18n/partnership_fr.rst:322 msgid "Le PARTENAIRE n'utilise pas la marque \"Odoo\" dans un nom d'entreprise, un nom de produit, ou un nom de domaine, et ne dépose aucune marque qui la contienne." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:307 +#: ../../content/legal/terms/i18n/partnership_fr.rst:325 msgid "Les Parties s’abstiendront de nuire à l’image de marque et à la réputation de l’autre Partie de quelque façon que ce soit, dans l’exécution de ce Contrat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:310 +#: ../../content/legal/terms/i18n/partnership_fr.rst:328 msgid "Le non-respect des dispositions de cette section sera une cause de résiliation du Contrat." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:314 +#: ../../content/legal/terms/i18n/partnership_fr.rst:332 msgid "8.1 Publicité" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:315 +#: ../../content/legal/terms/i18n/partnership_fr.rst:333 msgid "Le PARTENAIRE octroie à ODOO un droit non exclusif d’utilisation du nom ou de la marque déposée du PARTENAIRE dans des communiqués de presse, annonces publicitaires ou autres annonces publiques." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:318 +#: ../../content/legal/terms/i18n/partnership_fr.rst:336 msgid "Le PARTENAIRE accepte en particulier d’être mentionné dans la liste officielle des partenaires ODOO et que son logo ou sa marque déposée soient utilisés à cette fin uniquement." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:322 +#: ../../content/legal/terms/i18n/partnership_fr.rst:340 msgid "8.2 Pas de candidature ou d’engagement" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:324 +#: ../../content/legal/terms/i18n/partnership_fr.rst:342 msgid "À moins que l’autre Partie ne donne son consentement écrit, chaque Partie, ses filiales et ses représentants acceptent de ne pas solliciter ou proposer un emploi à un travailleur de l’autre Partie impliqué dans l’exécution ou l’utilisation des Services repris dans ce Contrat, pour toute la durée de l’accord et une période de 12 mois suivant la date de résiliation ou d’expiration de ce Contrat. En cas de non-respect des conditions de cette section qui mène à la résiliation dudit travailleur à cet effet, la Partie fautive accepte de payer à l’autre Partie la somme de 30 000,00 (trente mille) euros (€)." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:333 +#: ../../content/legal/terms/i18n/partnership_fr.rst:351 msgid "8.3 Contracteurs indépendants" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:334 +#: ../../content/legal/terms/i18n/partnership_fr.rst:352 msgid "Les Parties sont des contracteurs indépendants et ce Contrat ne sera pas interprété comme constituant une Partie comme partenaire, joint-venture ou fiduciaire de l’autre ni créant tout autre forme d’association légale qui imposerait à l’une des Parties la responsabilité pour l’action ou l’inaction de l’autre ou fournissant à l’une des Parties le droit, le pouvoir ou l’autorité (expresse ou implicite) de créer quelque devoir ou obligation que ce soit." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:343 +#: ../../content/legal/terms/i18n/partnership_fr.rst:361 msgid "9 Loi applicable et compétence" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:344 +#: ../../content/legal/terms/i18n/partnership_fr.rst:362 msgid "Ce Contrat sera gouverné par et interprété en accord avec la loi belge. Tout litige naissant en lien avec le Contrat et pour lequel aucun règlement à l’amiable ne peut être trouvé sera finalement réglé par les Tribunaux de Belgique à Nivelles." msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:364 -#: ../../content/legal/terms/i18n/partnership_fr.rst:None -#: ../../content/legal/terms/partnership.rst:354 -#: ../../content/legal/terms/partnership.rst:None +#: ../../content/legal/terms/i18n/partnership_fr.rst:-1 +#: ../../content/legal/terms/i18n/partnership_fr.rst:382 +#: ../../content/legal/terms/partnership.rst:-1 +#: ../../content/legal/terms/partnership.rst:370 msgid "Signatures" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:366 +#: ../../content/legal/terms/i18n/partnership_fr.rst:384 msgid "Pour ODOO," msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:366 +#: ../../content/legal/terms/i18n/partnership_fr.rst:384 msgid "Pour le PARTENAIRE," msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:374 +#: ../../content/legal/terms/i18n/partnership_fr.rst:392 msgid "|vnegspace| |hspace| Pour ODOO, |hspace| Pour le PARTENAIRE, |vspace|" msgstr "" -#: ../../content/legal/terms/i18n/partnership_fr.rst:384 +#: ../../content/legal/terms/i18n/partnership_fr.rst:402 msgid "10 Annexe A : Licence Odoo Enterprise Edition" msgstr "" @@ -4085,55 +4954,59 @@ msgstr "" msgid "Conditions Générales de Vente" msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:7 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:9 +msgid "`Download PDF `_" +msgstr "" + +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:11 msgid "Dernière modification: 20 octobre 2021." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:9 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:13 msgid "Ces conditions régissent la vente de produits et services entre Odoo S.A. et ses filiales (collectivement, \"Odoo S.A.\") et le client. Des conditions supplémentaires peuvent s'appliquer pour d'autres services offerts par Odoo S.A. (par exemple, l'Odoo Enterprise Subscription Agreement). Si ces conditions supplémentaires entrent en contradiction avec les Conditions Générales de Vente, les conditions supplémentaires prévaudront." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:16 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:20 msgid "Veuillez lire ces conditions attentivement avant de faire une commande auprès d'Odoo S.A. En commandant auprès d'Odoo S.A., le client marque son accord avec les présentes conditions." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:20 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:24 msgid "Le client renonce explicitement à ses propres conditions générales, même dans le cas où celles-ci seraient postérieures aux présentes conditions générales. Toute dérogation doit, pour être valable, être convenue de manière expresse, préalable et par écrit. Les présentes conditions sont une prolongation du contrat signé entre parties et font en tant que telles partie intégrante de la relation contractuelle entre parties." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:27 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:31 msgid "Toutes les offres, tarifs ou listes de prix d’Odoo S.A. s’entendent, sauf stipulation contraire, sans engagement. Sauf stipulation contraire, toutes les factures sont payables à Odoo S.A. au comptant, au moment de la livraison. L'endroit de paiement est le siège social de Odoo S.A. peut envoyer des factures pour des marchandises déjà livrées même avant la livraison complète des marchandises. Le Client ne peut en aucun cas compenser une quelconque créance sur Odoo S.A. avec son obligation de paiement, sauf stipulation contraire." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:35 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:39 msgid "Si la facture n’est pas payée à son échéance, elle sera, à titre d’indemnité forfaitaire, majorée de 15% et majorée d'autres indemnités, éventuellement dues pour tout préjudice, à démontrer par Odoo S.A.. Le non-paiement de tout ou partie d’une facture à son échéance rend immédiatement exigibles toutes sommes ou toutes factures dues non-encore échue. En cas de non-paiement d’une facture, Odoo S.A.  a le droit de rompre toutes les conventions de vente qui restent encore à exécuter." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:43 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:47 msgid "Si le Client est autorisé à effectuer des paiements à terme, l’absence de paiement d’un seul terme entraînera de plein droit et sans mise en demeure l’exigibilité de toute la dette, nonobstant toute indemnité supplémentaire." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:47 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:51 msgid "Certains pays appliquent une retenue à la source sur le montant de la facture, conformément à leur législation interne. La retenue à la source sera réglée par le client, auprès de l'administration fiscale. En aucun cas, Odoo S.A. ne sera impliquée dans les coûts liés à la législation du pays. Le montant de la facture est donc dû à Odoo S.A. dans son intégralité et n’inclus pas les coûts relatifs à la législation du pays où se trouve le client. Pour les clients implantés dans plusieurs pays, les prix applicables seront toujours basés sur l'implantation géographique ayant la liste de prix la plus élevée, sauf stipulation contraire par écrit au moment de la commande." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:57 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:61 msgid "Odoo S.A. s'engage à faire ses meilleurs efforts en vue de fournir en temps utile des services performants. Toutefois, aucune de ses obligations ne peut être considérée comme étant une obligation de résultat. Odoo S.A. ne peut, en aucun cas, être appelée en garantie par le client dans le cadre de demandes en dommages et intérêts formulée par le consommateur final à l'encontre du client." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:63 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:67 msgid "Dans la limite autorisée par la loi, la responsabilité globale de chaque partie, ainsi que de ses filiales ne dépassera pas 50% du montant total réglé par le Client en vertu des présentes conditions au cours des 12 mois précédant la date de l'événement donnant lieu à une telle réclamation. Des réclamations multiples n'augmenteront pas cette limite." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:69 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:73 msgid "Toute réclamation doit, pour être recevable, être notifiée à Odoo S.A., à son siège social, par courrier recommandé dans les 8 jours suivant la livraison des marchandises ou la prestation des services." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:73 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:77 msgid "Odoo S.A. se réserve le droit de modifier ces conditions à n'importe quel moment et sans notification préalable. Le client est soumis aux conditions en application au moment de son acceptation de ces conditions." msgstr "" -#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:77 +#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:81 msgid "Tout litige résultant de la présente convention ressort de l’application du droit belge et est de la compétence des Tribunaux de l’arrondissement du siège social d’Odoo S.A. hormis le droit d’Odoo S.A. de porter le litige devant une autre juridiction compétente." msgstr "" @@ -4165,452 +5038,443 @@ msgstr "" msgid "In addition, Odoo S.A. is not obligated to provide any maintenance, technical or other support for the Service." msgstr "" -#: ../../content/legal/terms/partnership.rst:17 -msgid "BETWEEN:" +#: ../../content/legal/terms/partnership.rst:5 +msgid "Odoo Partnership Agreement" msgstr "" -#: ../../content/legal/terms/partnership.rst:18 -msgid "Odoo S.A., having its registered office at Chaussée de Namur, 40, 1367 Grand-Rosière," -msgstr "" - -#: ../../content/legal/terms/partnership.rst:19 -msgid "Belgium, and its affiliates (collectively referred to as “ODOO”)" -msgstr "" - -#: ../../content/legal/terms/partnership.rst:20 -msgid "AND:" -msgstr "" - -#: ../../content/legal/terms/partnership.rst:21 -msgid "_____________________________________________, a company having its registered office at" +#: ../../content/legal/terms/partnership.rst:9 +msgid "`Download PDF <../../odoo_partnership_agreement.pdf>`_" msgstr "" #: ../../content/legal/terms/partnership.rst:23 -msgid "(hereinafter referred to as “PARTNER”)" +msgid "BETWEEN:" +msgstr "" + +#: ../../content/legal/terms/partnership.rst:24 +msgid "Odoo S.A., having its registered office at Chaussée de Namur, 40, 1367 Grand-Rosière," msgstr "" #: ../../content/legal/terms/partnership.rst:25 -msgid "ODOO and PARTNER are individually referred to as a \"Party\" and collectively referred to as \"the Parties\"." +msgid "Belgium, and its affiliates (collectively referred to as “ODOO”)" +msgstr "" + +#: ../../content/legal/terms/partnership.rst:26 +msgid "AND:" +msgstr "" + +#: ../../content/legal/terms/partnership.rst:27 +msgid "_____________________________________________, a company having its registered office at" msgstr "" #: ../../content/legal/terms/partnership.rst:29 +msgid "(hereinafter referred to as “PARTNER”)" +msgstr "" + +#: ../../content/legal/terms/partnership.rst:31 +msgid "ODOO and PARTNER are individually referred to as a \"Party\" and collectively referred to as \"the Parties\"." +msgstr "" + +#: ../../content/legal/terms/partnership.rst:35 msgid "1 Purpose" msgstr "" -#: ../../content/legal/terms/partnership.rst:30 +#: ../../content/legal/terms/partnership.rst:36 msgid "The purpose of this agreement is to set forth the conditions under which ODOO provides services to PARTNER, access to the Odoo Enterprise Edition software, and under which PARTNER complies with the obligations set out hereafter." msgstr "" -#: ../../content/legal/terms/partnership.rst:34 +#: ../../content/legal/terms/partnership.rst:40 msgid "ODOO hereby appoints PARTNER, and PARTNER hereby accepts the appointment, to be a non-exclusive partner promoting and selling \"Odoo Enterprise Edition\" to customers." msgstr "" -#: ../../content/legal/terms/partnership.rst:37 +#: ../../content/legal/terms/partnership.rst:43 msgid "PARTNER commits to doing its best effort to sell Odoo Enterprise contracts to its clients. To support that, PARTNER will market in priority the \"Odoo Enterprise Edition\" version to prospects and customers. PARTNER still has the option to sell services on other versions of the software, like \"Odoo Community Edition\", should it be needed." msgstr "" -#: ../../content/legal/terms/partnership.rst:43 +#: ../../content/legal/terms/partnership.rst:49 msgid "2 Term of the Agreement" msgstr "" -#: ../../content/legal/terms/partnership.rst:44 +#: ../../content/legal/terms/partnership.rst:50 msgid "The duration of this Agreement (the “Term”) shall be one year beginning on the date of the signature. It is automatically renewed for an equal Term unless either party provides written notice of termination minimum 30 days before the end of the Term to the other party." msgstr "" -#: ../../content/legal/terms/partnership.rst:50 +#: ../../content/legal/terms/partnership.rst:56 msgid "3 Access to Odoo Enterprise Edition" msgstr "" -#: ../../content/legal/terms/partnership.rst:53 +#: ../../content/legal/terms/partnership.rst:59 msgid "3.1 Project platform access" msgstr "" -#: ../../content/legal/terms/partnership.rst:54 +#: ../../content/legal/terms/partnership.rst:60 msgid "To help PARTNER promote Odoo Enterprise Edition, ODOO grants PARTNER access to its project code repository for all \"Odoo Enterprise Edition\" Apps, under the terms set forth in :ref:`appendix_p_a` and the conditions restricted under this Agreement." msgstr "" -#: ../../content/legal/terms/partnership.rst:58 +#: ../../content/legal/terms/partnership.rst:64 msgid "In addition, ODOO grants PARTNER free access to the ODOO.SH platform for testing and development purposes." msgstr "" -#: ../../content/legal/terms/partnership.rst:65 +#: ../../content/legal/terms/partnership.rst:71 msgid "PARTNER commits to keeping confidentiality of the source code of Odoo Enterprise Edition Apps within its staff. Access to the source code of Odoo Enterprise Edition for customers is governed by the Odoo Enterprise Subscription Agreement. PARTNER agrees to NOT redistribute this code to third parties without the written permission of ODOO." msgstr "" -#: ../../content/legal/terms/partnership.rst:70 +#: ../../content/legal/terms/partnership.rst:76 msgid "PARTNER commits to not offer services on Odoo Enterprise Edition to customers who are not covered by an Odoo Enterprise subscription, even during the implementation phase." msgstr "" -#: ../../content/legal/terms/partnership.rst:73 +#: ../../content/legal/terms/partnership.rst:79 msgid "Notwithstanding the above, PARTNER commits to wholly preserve the integrity of the Odoo Enterprise Edition code that is required to verify the validity of usage of Odoo Enterprise Edition and to collect statistics that are needed for that purpose." msgstr "" -#: ../../content/legal/terms/partnership.rst:79 +#: ../../content/legal/terms/partnership.rst:83 +msgid "PARTNER is not allowed to block, restrict or limit in any way the customer's access and use of the Odoo Enterprise Edition License, without prior consultation and written authorisation from ODOO." +msgstr "" + +#: ../../content/legal/terms/partnership.rst:88 msgid "4 Partnership Services" msgstr "" -#: ../../content/legal/terms/partnership.rst:82 +#: ../../content/legal/terms/partnership.rst:91 msgid "4.1 Partnership levels" msgstr "" -#: ../../content/legal/terms/partnership.rst:83 +#: ../../content/legal/terms/partnership.rst:92 msgid "The Odoo partner program consists of two types of partnerships and four levels; “Learning Partners” is for companies who want everything necessary to start implementing Odoo, without visibility as an official partner until they get the required experience; “Official Partners” is for companies who want the visibility as Ready, Silver, and Gold, according to their experience with Odoo." msgstr "" -#: ../../content/legal/terms/partnership.rst:89 -msgid "Partnership level granted to PARTNER depends on the annual new Odoo Enterprise revenue generated for ODOO (in terms of Odoo Enterprise Users sold), the number of certified resources and the customer Retention Rate. Renewals of existing contracts do not count towards the number of Users Sold, but PARTNER still gets a commission on these contracts as stated in section :ref:`benefits`." -msgstr "" - -#: ../../content/legal/terms/partnership.rst:95 -msgid "The table below summarizes the requirements that have to be met for each partnership level." -msgstr "" - -#: ../../content/legal/terms/partnership.rst:100 -msgid "Annual New Odoo Enterprise Users Sold" -msgstr "" - -#: ../../content/legal/terms/partnership.rst:102 -msgid "Number of Certified Employees on at least one of the 3 last Odoo versions" +#: ../../content/legal/terms/partnership.rst:98 +msgid "Partnership level granted to PARTNER depends on the *net new Odoo Enterprise users sold* in the last 12 months, the number of certified resources and the customer Retention Rate. The *net new Odoo Enterprise users sold* includes new customers, upsells on existing customer, downsells on existing customers, and customer churn. Renewals of existing contracts do not count towards the number of Users Sold, but PARTNER still gets a commission on these contracts as stated in section :ref:`benefits`." msgstr "" #: ../../content/legal/terms/partnership.rst:105 +msgid "The table below summarizes the requirements that have to be met for each partnership level." +msgstr "" + +#: ../../content/legal/terms/partnership.rst:107 +msgid "The customer *Retention Rate* is calculated by dividing the total number of Odoo Enterprise customers acquired by PARTNER in the last 3 years that are currently active by the total number of Odoo Enterprise customers acquired by PARTNER in the last 3 years." +msgstr "" + +#: ../../content/legal/terms/partnership.rst:114 +msgid "Annual Net New Odoo Enterprise Users Sold" +msgstr "" + +#: ../../content/legal/terms/partnership.rst:116 +msgid "Number of Certified Employees on at least one of the 3 last Odoo versions" +msgstr "" + +#: ../../content/legal/terms/partnership.rst:119 msgid "Minimum Retention Rate" msgstr "" -#: ../../content/legal/terms/partnership.rst:108 -msgid "The Retention Rate is defined as the ratio between the number of Odoo Enterprise contracts that are currently active, and the number of Odoo Enterprise contracts that have been active at some point in the last 12 months" -msgstr "" - -#: ../../content/legal/terms/partnership.rst:112 +#: ../../content/legal/terms/partnership.rst:122 msgid "Certifications are personal, so when a certified staff member leaves or joins the company, PARTNER must notify ODOO." msgstr "" -#: ../../content/legal/terms/partnership.rst:115 +#: ../../content/legal/terms/partnership.rst:125 msgid "PARTNER's partnership level will be reviewed quarterly by ODOO, and adjusted to the highest level for which the 3 requirements are met." msgstr "" -#: ../../content/legal/terms/partnership.rst:118 +#: ../../content/legal/terms/partnership.rst:128 msgid "However, \"Official Partners\" may be upgraded automatically to a higher level once they reach the 3 requirements for that higher partnership level." msgstr "" -#: ../../content/legal/terms/partnership.rst:125 +#: ../../content/legal/terms/partnership.rst:135 msgid "4.2 Benefits" msgstr "" -#: ../../content/legal/terms/partnership.rst:127 +#: ../../content/legal/terms/partnership.rst:137 msgid "The details of the benefits for each level of the partnership are described in the table below:" msgstr "" -#: ../../content/legal/terms/partnership.rst:136 +#: ../../content/legal/terms/partnership.rst:146 msgid "**Recognition**" msgstr "" -#: ../../content/legal/terms/partnership.rst:138 +#: ../../content/legal/terms/partnership.rst:148 msgid "Visibility on odoo.com" msgstr "" -#: ../../content/legal/terms/partnership.rst:140 +#: ../../content/legal/terms/partnership.rst:150 msgid "Right to use \"Odoo\" trademark and Partner Logo" msgstr "" -#: ../../content/legal/terms/partnership.rst:140 -#: ../../content/legal/terms/partnership.rst:140 -#: ../../content/legal/terms/partnership.rst:140 -#: ../../content/legal/terms/partnership.rst:140 -#: ../../content/legal/terms/partnership.rst:145 -#: ../../content/legal/terms/partnership.rst:145 -#: ../../content/legal/terms/partnership.rst:145 -#: ../../content/legal/terms/partnership.rst:145 -#: ../../content/legal/terms/partnership.rst:147 -#: ../../content/legal/terms/partnership.rst:147 -#: ../../content/legal/terms/partnership.rst:147 -#: ../../content/legal/terms/partnership.rst:147 -#: ../../content/legal/terms/partnership.rst:151 -#: ../../content/legal/terms/partnership.rst:151 -#: ../../content/legal/terms/partnership.rst:151 -#: ../../content/legal/terms/partnership.rst:151 -#: ../../content/legal/terms/partnership.rst:154 -#: ../../content/legal/terms/partnership.rst:154 -#: ../../content/legal/terms/partnership.rst:154 -#: ../../content/legal/terms/partnership.rst:154 -#: ../../content/legal/terms/partnership.rst:156 -#: ../../content/legal/terms/partnership.rst:156 -#: ../../content/legal/terms/partnership.rst:156 -#: ../../content/legal/terms/partnership.rst:156 -#: ../../content/legal/terms/partnership.rst:168 -#: ../../content/legal/terms/partnership.rst:168 -#: ../../content/legal/terms/partnership.rst:168 -#: ../../content/legal/terms/partnership.rst:173 -#: ../../content/legal/terms/partnership.rst:173 -#: ../../content/legal/terms/partnership.rst:173 -#: ../../content/legal/terms/partnership.rst:173 -#: ../../content/legal/terms/partnership.rst:175 -#: ../../content/legal/terms/partnership.rst:175 -#: ../../content/legal/terms/partnership.rst:175 +#: ../../content/legal/terms/partnership.rst:150 +#: ../../content/legal/terms/partnership.rst:155 +#: ../../content/legal/terms/partnership.rst:157 +#: ../../content/legal/terms/partnership.rst:161 +#: ../../content/legal/terms/partnership.rst:164 +#: ../../content/legal/terms/partnership.rst:166 +#: ../../content/legal/terms/partnership.rst:178 +#: ../../content/legal/terms/partnership.rst:183 +#: ../../content/legal/terms/partnership.rst:185 msgid "Yes" msgstr "" -#: ../../content/legal/terms/partnership.rst:143 +#: ../../content/legal/terms/partnership.rst:153 msgid "**Training benefits**" msgstr "" -#: ../../content/legal/terms/partnership.rst:145 +#: ../../content/legal/terms/partnership.rst:155 msgid "Sales Coaching & Webinars" msgstr "" -#: ../../content/legal/terms/partnership.rst:147 +#: ../../content/legal/terms/partnership.rst:157 msgid "Access to Odoo Knowledge Base" msgstr "" -#: ../../content/legal/terms/partnership.rst:149 +#: ../../content/legal/terms/partnership.rst:159 msgid "**Software benefits**" msgstr "" -#: ../../content/legal/terms/partnership.rst:151 +#: ../../content/legal/terms/partnership.rst:161 msgid "Access to Odoo Enterprise source code and Github repository" msgstr "" -#: ../../content/legal/terms/partnership.rst:154 +#: ../../content/legal/terms/partnership.rst:164 msgid "Odoo Enterprise trial extension code" msgstr "" -#: ../../content/legal/terms/partnership.rst:156 +#: ../../content/legal/terms/partnership.rst:166 msgid "Access to Odoo.sh for testing and development purposes" msgstr "" -#: ../../content/legal/terms/partnership.rst:159 +#: ../../content/legal/terms/partnership.rst:169 msgid "**Sales benefits**" msgstr "" -#: ../../content/legal/terms/partnership.rst:161 +#: ../../content/legal/terms/partnership.rst:171 msgid "Commission on Odoo SH platform [#s1]_" msgstr "" -#: ../../content/legal/terms/partnership.rst:163 +#: ../../content/legal/terms/partnership.rst:173 msgid "Commission on Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/partnership.rst:165 +#: ../../content/legal/terms/partnership.rst:175 msgid "Commission on Maintenance of Extra Modules" msgstr "" -#: ../../content/legal/terms/partnership.rst:168 +#: ../../content/legal/terms/partnership.rst:178 msgid "Dedicated Account Manager & Partner Dashboard" msgstr "" -#: ../../content/legal/terms/partnership.rst:171 +#: ../../content/legal/terms/partnership.rst:181 msgid "**Marketing benefits**" msgstr "" -#: ../../content/legal/terms/partnership.rst:173 +#: ../../content/legal/terms/partnership.rst:183 msgid "Access to marketing material" msgstr "" -#: ../../content/legal/terms/partnership.rst:175 +#: ../../content/legal/terms/partnership.rst:185 msgid "PARTNER Event - ODOO support & Promotion" msgstr "" -#: ../../content/legal/terms/partnership.rst:179 -msgid "up to a maximum of 150€ (or 180$) of monthly commission per subscription" +#: ../../content/legal/terms/partnership.rst:189 +msgid "up to a maximum of 150€ (or $180) of monthly commission per subscription, or 1440€ (or $1728) of yearly commission per subscription" msgstr "" -#: ../../content/legal/terms/partnership.rst:183 +#: ../../content/legal/terms/partnership.rst:194 msgid "4.3 Partner Recognition" msgstr "" -#: ../../content/legal/terms/partnership.rst:184 +#: ../../content/legal/terms/partnership.rst:195 msgid "ODOO will promote \"Official Partners\" on the Odoo Partners list on odoo.com." msgstr "" -#: ../../content/legal/terms/partnership.rst:186 +#: ../../content/legal/terms/partnership.rst:197 msgid "ODOO grants PARTNER, on a non-exclusive basis, the right to use and reproduce the ODOO Partner logo of the corresponding partnership level, and the \"Odoo\" name in relation to this partnership agreement." msgstr "" -#: ../../content/legal/terms/partnership.rst:190 +#: ../../content/legal/terms/partnership.rst:201 msgid "Each Party undertakes to respect all the rights of the other Party in all the items referred to in the previous paragraph and, more particularly, each Party shall refrain from causing any analogy or creating any confusion between their respective company in the mind of the general public." msgstr "" -#: ../../content/legal/terms/partnership.rst:195 +#: ../../content/legal/terms/partnership.rst:206 msgid "4.4 Training Benefits" msgstr "" -#: ../../content/legal/terms/partnership.rst:196 +#: ../../content/legal/terms/partnership.rst:207 msgid "PARTNER has access to the ODOO knowledge base for the duration of this Agreement. The ODOO knowledge base is an online e-platform containing a set of commercial, marketing and functional documents, to help PARTNER acquire and leverage Odoo knowledge, grow its business, attract more customers, and build brand awareness." msgstr "" -#: ../../content/legal/terms/partnership.rst:201 +#: ../../content/legal/terms/partnership.rst:212 msgid "PARTNER will have access to commercial coaching provided by their dedicated Account Manager, as appointed by ODOO." msgstr "" -#: ../../content/legal/terms/partnership.rst:204 +#: ../../content/legal/terms/partnership.rst:215 msgid "PARTNER also has the option to purchase support services or training by subscribing to an Odoo Success Pack, for an extra fee." msgstr "" -#: ../../content/legal/terms/partnership.rst:208 +#: ../../content/legal/terms/partnership.rst:219 msgid "4.5 Commissions on Odoo Services sold by PARTNER" msgstr "" -#: ../../content/legal/terms/partnership.rst:209 +#: ../../content/legal/terms/partnership.rst:220 msgid "For ODOO services purchased by a customer through PARTNER, and as long as PARTNER maintains a contractual relationship with the corresponding customer, PARTNER shall receive a commission according to the table of section :ref:`benefits` and their Partnership level at the date of the customer invoice." msgstr "" -#: ../../content/legal/terms/partnership.rst:214 +#: ../../content/legal/terms/partnership.rst:225 msgid "Once a month, PARTNER will receive a purchase order with the commission due for the preceding month. Based on this purchase order, PARTNER shall invoice ODOO, and will be paid within 15 days upon receipt of the invoice." msgstr "" -#: ../../content/legal/terms/partnership.rst:220 +#: ../../content/legal/terms/partnership.rst:231 msgid "PARTNER acknowledges and agrees that when a customer decides to Work with PARTNER [#pcom1]_ , ODOO will delegate the Maintenance of Covered Extra Modules to PARTNER, who becomes the main point of contact of the customer." msgstr "" -#: ../../content/legal/terms/partnership.rst:224 +#: ../../content/legal/terms/partnership.rst:235 msgid "PARTNER shall only receive the commission for the Maintenance of Covered Extra Modules as long as the customer does not notify ODOO that they want to stop Working with PARTNER." msgstr "" -#: ../../content/legal/terms/partnership.rst:227 +#: ../../content/legal/terms/partnership.rst:238 msgid "“Working with an Odoo Partner” and “Covered Extra Modules” are defined in the Odoo Enterprise Subscription Agreement between ODOO and customers." msgstr "" -#: ../../content/legal/terms/partnership.rst:231 +#: ../../content/legal/terms/partnership.rst:242 msgid "5 Fees" msgstr "" -#: ../../content/legal/terms/partnership.rst:232 +#: ../../content/legal/terms/partnership.rst:243 msgid "PARTNER agrees to pay the Partnership Annual Fee upon receipt of the annual invoice sent by ODOO. The fee will be specified in writing at the time of signature of this agreement." msgstr "" -#: ../../content/legal/terms/partnership.rst:236 +#: ../../content/legal/terms/partnership.rst:247 msgid "PARTNER acknowledges that the above-mentioned Partnership fee is not refundable." msgstr "" -#: ../../content/legal/terms/partnership.rst:240 +#: ../../content/legal/terms/partnership.rst:249 +msgid "All fees and charges are exclusive of all applicable federal, provincial, state, local or other governmental taxes, fees or charges (collectively, “Taxes”). PARTNER is responsible for paying all Taxes associated with purchases made by PARTNER under this Agreement, except when ODOO is legally obliged to pay or collect Taxes for which PARTNER is responsible." +msgstr "" + +#: ../../content/legal/terms/partnership.rst:256 msgid "6 Termination" msgstr "" -#: ../../content/legal/terms/partnership.rst:241 +#: ../../content/legal/terms/partnership.rst:257 msgid "In the event that either Party fails to fulfill any of its obligations arising herein, and if such a breach has not been remedied within 30 calendar days from the written notice of such breach, this Agreement may be terminated immediately by the non-breaching Party." msgstr "" -#: ../../content/legal/terms/partnership.rst:246 +#: ../../content/legal/terms/partnership.rst:262 msgid "The sections \":ref:`restrictions`”, “:ref:`p_liability`”, and “:ref:`gov_law`” will survive any termination or expiration of this Agreement." msgstr "" -#: ../../content/legal/terms/partnership.rst:250 +#: ../../content/legal/terms/partnership.rst:266 msgid "6.1 Consequence of termination" msgstr "" -#: ../../content/legal/terms/partnership.rst:255 +#: ../../content/legal/terms/partnership.rst:271 msgid "On expiry or termination of this Agreement, PARTNER:" msgstr "" -#: ../../content/legal/terms/partnership.rst:252 +#: ../../content/legal/terms/partnership.rst:268 msgid "shall not use anymore the materials and the Odoo brand name, trademarks and logos or claim the existence of any partnership or relationship with ODOO ;" msgstr "" -#: ../../content/legal/terms/partnership.rst:254 +#: ../../content/legal/terms/partnership.rst:270 msgid "shall comply with its obligations during any notice period prior to such termination ;" msgstr "" -#: ../../content/legal/terms/partnership.rst:255 +#: ../../content/legal/terms/partnership.rst:271 msgid "may not use Odoo Enterprise anymore, for development, test or production purpose" msgstr "" -#: ../../content/legal/terms/partnership.rst:260 +#: ../../content/legal/terms/partnership.rst:276 msgid "7 Liability and Indemnities" msgstr "" -#: ../../content/legal/terms/partnership.rst:261 +#: ../../content/legal/terms/partnership.rst:277 msgid "Both Parties are bound by a best endeavours obligation hereunder." msgstr "" -#: ../../content/legal/terms/partnership.rst:263 -msgid "To the maximum extent permitted by law, ODOO’s liability for any and all claims, losses, damages or expenses from any cause whatsoever and howsoever arising under this Agreement will be limited to the direct damages proved, but will in no event exceed for all damage-causing event or series of connected events causing damages the total amount for the fees paid by PARTNER in the course of the six (6) months immediately preceding the date of the event giving rise to such claim." -msgstr "" - -#: ../../content/legal/terms/partnership.rst:269 -msgid "In no event will ODOO be liable for any indirect or consequential damages, including but not limited third parties or customer claims, loss of revenue, profits, savings, loss of business or other financial loss, costs of standstill or delay, lost or corrupted data arising out of or in connection with the performance of its obligations under this Agreement." -msgstr "" - -#: ../../content/legal/terms/partnership.rst:274 -msgid "PARTNER acknowledges that he has no expectations and has received no assurances that any investment made in execution of this Agreement and the Odoo Partnership Program will be recovered or recouped or that he shall obtain any anticipated amount of profits by virtue of this Agreement." -msgstr "" - -#: ../../content/legal/terms/partnership.rst:280 -msgid "8 Brand Image" -msgstr "" - -#: ../../content/legal/terms/partnership.rst:282 -msgid "The \"Odoo\" mark (including the word mark and its visual representations and logos) is the exclusive property of ODOO." +#: ../../content/legal/terms/partnership.rst:279 +msgid "To the maximum extent permitted by law, the liability of each Party for any and all claims, losses, damages or expenses from any cause whatsoever and howsoever arising under this Agreement will be limited to the direct damages proved, but will in no event exceed for all damage-causing event or series of connected events causing damages the total amount for the fees paid by PARTNER in the course of the six (6) months immediately preceding the date of the event giving rise to such claim." msgstr "" #: ../../content/legal/terms/partnership.rst:285 +msgid "In no event will each Party be liable for any indirect or consequential damages, including but not limited third parties or customer claims, loss of revenue, profits, savings, loss of business or other financial loss, costs of standstill or delay, lost or corrupted data arising out of or in connection with the performance of its obligations under this Agreement." +msgstr "" + +#: ../../content/legal/terms/partnership.rst:290 +msgid "PARTNER acknowledges that he has no expectations and has received no assurances that any investment made in execution of this Agreement and the Odoo Partnership Program will be recovered or recouped or that he shall obtain any anticipated amount of profits by virtue of this Agreement." +msgstr "" + +#: ../../content/legal/terms/partnership.rst:296 +msgid "8 Brand Image" +msgstr "" + +#: ../../content/legal/terms/partnership.rst:298 +msgid "The \"Odoo\" mark (including the word mark and its visual representations and logos) is the exclusive property of ODOO." +msgstr "" + +#: ../../content/legal/terms/partnership.rst:301 msgid "ODOO authorizes PARTNER to use the \"Odoo\" mark to promote its products and services, for the duration of this agreement only, as long as:" msgstr "" -#: ../../content/legal/terms/partnership.rst:288 +#: ../../content/legal/terms/partnership.rst:304 msgid "There is no possible confusion that the service is provided by PARTNER, not ODOO;" msgstr "" -#: ../../content/legal/terms/partnership.rst:289 +#: ../../content/legal/terms/partnership.rst:305 msgid "PARTNER does not use the word “Odoo” in their company name, product name, domain name, and does not register any trademark that includes it." msgstr "" -#: ../../content/legal/terms/partnership.rst:292 +#: ../../content/legal/terms/partnership.rst:308 msgid "Both Parties shall refrain from harming the brand image and reputation of the other Party, in any way whatsoever, in the performance of this Agreement." msgstr "" -#: ../../content/legal/terms/partnership.rst:295 +#: ../../content/legal/terms/partnership.rst:311 msgid "Non-compliance with the provisions of this section shall be a cause for termination of this Agreement." msgstr "" -#: ../../content/legal/terms/partnership.rst:299 +#: ../../content/legal/terms/partnership.rst:315 msgid "8.1 Publicity" msgstr "" -#: ../../content/legal/terms/partnership.rst:300 -msgid "PARTNER grants ODOO the nonexclusive right to use PARTNER's name or trademarks in press releases, advertisements or other public announcements." +#: ../../content/legal/terms/partnership.rst:316 +msgid "PARTNER grants ODOO the non-exclusive right to use PARTNER's name or trademarks in press releases, advertisements or other public announcements." msgstr "" -#: ../../content/legal/terms/partnership.rst:303 +#: ../../content/legal/terms/partnership.rst:319 msgid "In particular, PARTNER accepts to be mentioned in the official list of Odoo Partners on odoo.com, and that PARTNER's logo and trademarks may be used for this purpose only." msgstr "" -#: ../../content/legal/terms/partnership.rst:310 +#: ../../content/legal/terms/partnership.rst:326 msgid "8.2 No Soliciting or Hiring" msgstr "" -#: ../../content/legal/terms/partnership.rst:312 +#: ../../content/legal/terms/partnership.rst:328 msgid "Except where the other Party gives its consent in writing, each Party, its affiliates and representatives agree not to solicit or offer employment to any employee of the other Party who is involved in performing or using the Services under this Agreement, for the duration of the Agreement and for a period of 12 months from the date of termination or expiration of this Agreement. In case of any breach of the conditions of this section that leads to the termination of said employee toward that end, the breaching Party agrees to pay the other Party an amount of EUR (€) 30 000.00 (thirty thousand euros)." msgstr "" -#: ../../content/legal/terms/partnership.rst:322 +#: ../../content/legal/terms/partnership.rst:338 msgid "8.3 Independent Contractors" msgstr "" -#: ../../content/legal/terms/partnership.rst:323 +#: ../../content/legal/terms/partnership.rst:339 msgid "The Parties are independent contractors, and this Agreement shall not be construed as constituting either Party as a partner, joint venture or fiduciary of the other, as creating any other form of a legal association that would impose liability on one Party for the act or failure to act of the other or as providing either Party with the right, power or authority (express or implied) to create any duty or obligation of the other." msgstr "" -#: ../../content/legal/terms/partnership.rst:333 +#: ../../content/legal/terms/partnership.rst:349 msgid "9 Governing Law and Jurisdiction" msgstr "" -#: ../../content/legal/terms/partnership.rst:334 +#: ../../content/legal/terms/partnership.rst:350 msgid "This Agreement will be governed by and construed in accordance with the laws of Belgium. All disputes arising in connection with the Agreement for which no amicable settlement can be found shall be finally settled by the Courts of Belgium in Nivelles." msgstr "" -#: ../../content/legal/terms/partnership.rst:356 +#: ../../content/legal/terms/partnership.rst:372 msgid "For ODOO," msgstr "" -#: ../../content/legal/terms/partnership.rst:356 +#: ../../content/legal/terms/partnership.rst:372 msgid "For PARTNER" msgstr "" -#: ../../content/legal/terms/partnership.rst:364 +#: ../../content/legal/terms/partnership.rst:380 msgid "|vnegspace| |hspace| For ODOO, |hspace| For PARTNER, |vspace|" msgstr "" -#: ../../content/legal/terms/partnership.rst:372 +#: ../../content/legal/terms/partnership.rst:388 msgid "10 Appendix A: Odoo Enterprise Edition License" msgstr "" @@ -4618,50 +5482,54 @@ msgstr "" msgid "General Terms of Sale" msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:7 +#: ../../content/legal/terms/terms_of_sale.rst:9 +msgid "`Download PDF `_" +msgstr "" + +#: ../../content/legal/terms/terms_of_sale.rst:11 msgid "Last revision: October 20, 2021." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:9 +#: ../../content/legal/terms/terms_of_sale.rst:13 msgid "These General Terms of Sale govern the sale of products and services by Odoo S.A. and its affiliates (collectively, \"Odoo S.A.\") to the client. Additional terms may apply for services provided by Odoo S.A. (for example, the Enterprise Subscription Agreement). If these additional terms are inconsistent with the General Terms of Sale, the additional terms will prevail over these General Terms of Sale." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:16 +#: ../../content/legal/terms/terms_of_sale.rst:20 msgid "Please read these terms carefully before placing an order with Odoo S.A. By accepting an order with Odoo S.A., the client marks his acceptance with these terms." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:20 +#: ../../content/legal/terms/terms_of_sale.rst:24 msgid "The client explicitly waives its own standard terms and conditions, even if these were drawn up after these standard terms and conditions of sale. In order to be valid, any derogation must be expressly agreed to in advance in writing." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:25 +#: ../../content/legal/terms/terms_of_sale.rst:29 msgid "Our invoices are payable within 21 working days, unless another payment timeframe is indicated on either the invoice or the order. In the event of non-payment by the due date, Odoo S.A. reserves the right to request a fixed interest payment amounting to 15% of the sum remaining due. Odoo S.A. will be authorised to suspend any provision of services without prior warning in the event of late payment." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:32 +#: ../../content/legal/terms/terms_of_sale.rst:36 msgid "If a payment is still outstanding more than sixty (60) days after the due payment date, Odoo S.A. reserves the right to call on the services of a debt recovery company. All legal expenses will be payable by the client." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:36 +#: ../../content/legal/terms/terms_of_sale.rst:40 msgid "Certain countries apply withholding at source on the amount of invoices, in accordance with their internal legislation. Any withholding at source will be paid by the client to the tax authorities. Under no circumstances can Odoo S.A. become involved in costs related to a country's legislation. The amount of the invoice will therefore be due to Odoo S.A. in its entirety and does not include any costs relating to the legislation of the country in which the client is located. For clients with a global presence, the applicable pricing is always based on the client location with the highest price list, unless otherwise specified in writing at the time of purchase." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:46 +#: ../../content/legal/terms/terms_of_sale.rst:50 msgid "Odoo S.A. undertakes to do its best to supply services in due time in accordance with the agreed timeframes. However, none of its obligations can be considered as being an obligation to achieve results. Odoo S.A. cannot, under any circumstances, be required by the client to appear as a third party in the context of any claim for damages filed against the client by an end consumer." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:52 +#: ../../content/legal/terms/terms_of_sale.rst:56 msgid "In order for it to be admissible, Odoo S.A. must be notified of any claim by means of a letter sent by recorded delivery to its registered office within 8 days of the delivery of the goods or the provision of the services." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:56 +#: ../../content/legal/terms/terms_of_sale.rst:60 msgid "To the maximum extent permitted by law, the aggregate liability of each party together with its affiliates arising will not exceed 50% of the total amount paid by the Customer under these terms during the 12 months immediately preceding the date of the event giving rise to such claim. Multiple claims shall not enlarge this limitation." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:62 +#: ../../content/legal/terms/terms_of_sale.rst:66 msgid "Odoo S.A. reserves the right to modify these terms at any time without prior notice. The client will be subject to the terms in force at the time of acceptation of those terms." msgstr "" -#: ../../content/legal/terms/terms_of_sale.rst:66 +#: ../../content/legal/terms/terms_of_sale.rst:70 msgid "All our contractual relations will be governed exclusively by Belgian law. Moreover, any dispute that may arise will be subject exclusively to the jurisdiction of the courts of the Nivelles arrondissement (Belgium)." msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 5bc2b7940..e1b9c92e0 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -60,7 +60,7 @@ msgstr "" msgid "When clicked, a drop-down menu of settings will appear." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:None +#: ../../content/applications/marketing/events/event_essentials.rst:-1 msgid "Overview of events setting with the kanban view in Odoo Events." msgstr "" @@ -136,7 +136,7 @@ msgstr "" msgid "If selling tickets isn't necessary for the event, a simple :guilabel:`Registration` button will be displayed on the event's page by default." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:None +#: ../../content/applications/marketing/events/event_essentials.rst:-1 msgid "View of the ticket tab in Odoo Events." msgstr "" @@ -156,7 +156,7 @@ msgstr "" msgid "In the last column, determine the :guilabel:`Trigger` which controls how and when the communication is sent. For this action, choose between: :guilabel:`Before the event`, :guilabel:`After each registration`, or :guilabel:`After the event`." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:None +#: ../../content/applications/marketing/events/event_essentials.rst:-1 msgid "View of the communication tab in Odoo Events." msgstr "" @@ -184,7 +184,7 @@ msgstr "" msgid "There are two :guilabel:`Question Types` to choose from: :guilabel:`Selection` and :guilabel:`Text Input`. The :guilabel:`Selection` type, allows attendees to select an answer from pre-configured options, which are entered in the :guilabel:`Answers` tab below. The :guilabel:`Text Input` type allows attendees to write in their own answer to the question in a text box." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:None +#: ../../content/applications/marketing/events/event_essentials.rst:-1 msgid "View of an event form, open the questions tab, and add a question." msgstr "" @@ -204,7 +204,7 @@ msgstr "" msgid "Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These options provide various formatting options to ensure vital internal information is organzied for event staff to review." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:None +#: ../../content/applications/marketing/events/event_essentials.rst:-1 msgid "View of the Notes tab in Odoo Events." msgstr "" @@ -240,7 +240,7 @@ msgstr "" msgid "Once an option from this menu is selected (e.g. :guilabel:`Applicant`, :guilabel:`Contact`, :guilabel:`Event Registration`, :guilabel:`Lead/Opportunity`, etc.), Odoo will send the invitation to all recipients who match that initial rule. Additional rules can be added to narrow down the target recipients, by clicking :guilabel:`Add Filter`." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:None +#: ../../content/applications/marketing/events/event_essentials.rst:-1 msgid "View of the add filter button beneath the recipients field in Odoo Events." msgstr "" @@ -264,7 +264,7 @@ msgstr "" msgid "In the :guilabel:`Mail Body` tab, there are a number of pre-configured message templates to choose from. Select the desired template, and modify every element of its design details with Odoo's drag-and-drop web builder, located on the right sidebar." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:None +#: ../../content/applications/marketing/events/event_essentials.rst:-1 msgid "View of the drag and drop building blocks used to customize event invite emails." msgstr "" @@ -336,7 +336,7 @@ msgstr "" msgid "No matter the route, an event page can only be published from the front end. In the upper right corner of the event page on the website, toggle the switch from the red :guilabel:`Unpublished` status to the green :guilabel:`Published` status. Doing so instantly makes the event page accessible to the public on the website." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:None +#: ../../content/applications/marketing/events/event_essentials.rst:-1 msgid "View of a website page and the option to publish the event in Odoo Events." msgstr "" @@ -369,7 +369,7 @@ msgstr "" msgid "If these options are *not* enabled, a default :guilabel:`Register` button will be available for free registrations." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:None +#: ../../content/applications/marketing/events/sell_tickets.rst:-1 msgid "View of the settings page for Odoo Events." msgstr "" @@ -381,7 +381,7 @@ msgstr "" msgid "In the :guilabel:`Sales` application, choose a previously-created Event Registration (as if it were a product), and add it as a product line. Upon adding the registration, a pop-up appears, which allows for the selection of a specific event (and ticket tier). That specific event ticket is then attached to the sales order." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:None +#: ../../content/applications/marketing/events/sell_tickets.rst:-1 msgid "View of a sales order and option to choose the specific event in Odoo Events." msgstr "" @@ -393,11 +393,11 @@ msgstr "" msgid "Clicking the :guilabel:`Sales Smart Button` reveals a page with all the sales orders related to that event." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:None +#: ../../content/applications/marketing/events/sell_tickets.rst:-1 msgid "View of an event's form and the sales smart button in Odoo Events." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:None +#: ../../content/applications/marketing/events/sell_tickets.rst:-1 msgid "View of an event form highlighting the column product under the tickets tab in Odoo\n" "Events." msgstr "" @@ -414,7 +414,7 @@ msgstr "" msgid "The completed purchase is automatically produced in a :guilabel:`Sales Order`, which can be easily accessed in the back end of the database." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:None +#: ../../content/applications/marketing/events/sell_tickets.rst:-1 msgid "View of website transaction for Odoo Events." msgstr "" @@ -466,7 +466,7 @@ msgstr "" msgid "The :guilabel:`Agenda` link takes the attendee to a page with all the talks for the event, but in a calendar/time-slot format." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:None +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 msgid "View of the published website and the talks, talk proposals, and agenda in Odoo Events" msgstr "" @@ -482,7 +482,7 @@ msgstr "" msgid "All talks (Proposals, Confirmed, Announced, etc.) are accessible via the :guilabel:`Tracks` smart button on the event form." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:None +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 msgid "View of the talks' proposals page emphasizing the column proposal in Odoo Events." msgstr "" @@ -498,7 +498,7 @@ msgstr "" msgid "Without publishing a talk, attendees will never be able to access it." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:None +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 msgid "View of the website page to publish a proposed talk for Odoo Events." msgstr "" @@ -514,7 +514,7 @@ msgstr "" msgid "When an attendee arrives at the event, they will be marked as attending (:guilabel:`Confirmed Attendance`), and the status of that attendee will change to :guilabel:`Attended.`" msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:None +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 msgid "Overview of events with the kanban view in Odoo Events." msgstr "" @@ -522,7 +522,7 @@ msgstr "" msgid "When analyzing an :guilabel:`Attendees list`, Odoo provides different ways to view the information. Each view option presents the same information, but in a slightly different layout. To change the view, click on the icons in the upper right hand of the screen." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:None +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 msgid "Various view options on the attendees list page." msgstr "" @@ -562,7 +562,7 @@ msgstr "" msgid "From here, event badges can be sent manually, by selecting :guilabel:`Send By Email`. The :guilabel:`Attendee` can also be marked as :guilabel:`Attended`, or the registration can be canceled altogether via the :guilabel:`Cancel Registration` button." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:None +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 msgid "View of an attendee form emphasizing the send by email and cancel registration in Odoo\n" "Events." msgstr "" @@ -583,7 +583,7 @@ msgstr "" msgid "On the :guilabel:`Lead Generation Rule` page, every configured :guilabel:`Lead Generation Rule` can be found, along with pertinent data related to those rules." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:None +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 msgid "How the Lead Generation Rule page looks in Odoo Events." msgstr "" @@ -591,7 +591,7 @@ msgstr "" msgid "To create a new :guilabel:`Lead Generation Rule`, click :guilabel:`Create`, and fill out the :guilabel:`Lead Generation Rule` form." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:None +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 msgid "How the Lead Generation Rule template looks in Odoo Events." msgstr "" @@ -614,6 +614,7 @@ msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:11 #: ../../content/applications/marketing/sms_marketing.rst:11 +#: ../../content/applications/marketing/social_marketing.rst:11 msgid "`Odoo Tutorials: Marketing `_" msgstr "" @@ -633,7 +634,7 @@ msgstr "" msgid "Consider the following example:" msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1 msgid "An example of a marketing automation campaign in Odoo." msgstr "" @@ -645,7 +646,7 @@ msgstr "" msgid "Beneath the filter nodes, Odoo will display how many records in the database fall into the previously-specified criteria filter. In this example, there are 18 records in the database that match the criteria." msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1 msgid "Lead generation filters used to refine records on marketing automation campaigns in Odoo." msgstr "" @@ -657,7 +658,7 @@ msgstr "" msgid ":guilabel:`Records` represent a real-time number. Therefore, while the workflow is running, changes in opportunity records (deletions, additions, adjustments) may occur. This means there will be real-time updates to the number of :guilabel:`Records`, but such updates do *not* change the number of :guilabel:`Participants`, as the metric *will not* exclude opportunities that have already been set as :guilabel:`Participants` before - Odoo will just add new ones. That's why the number of :guilabel:`Records` can be different from the number of :guilabel:`Participants` from time to time." msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1 msgid "Difference between real-time record count and total participants on a markeing campaign." msgstr "" @@ -685,7 +686,7 @@ msgstr "" msgid ":guilabel:`Success` represents the number of times the searching for participants - who match the criteria filter(s) of that activity - was performed successfully, in relation to the total number of participants. If a participant does *not* match the conditions, it will be added to :guilabel:`Rejected`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1 msgid "Overview showing participants who do or do not match filtering criteria on an activity." msgstr "" @@ -713,7 +714,7 @@ msgstr "" msgid "To create a new automated marketing campaign, open the :guilabel:`Marketing Automation` app and click :guilabel:`Create`. On the :guilabel:`Campaign` page, there are the following smart buttons and fields:" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:-1 msgid "A dashboard showing the creation of a new marketing automation campaign in Odoo." msgstr "" @@ -745,7 +746,7 @@ msgstr "" msgid "To add a filter to the target audience, click :guilabel:`Add Filter`, and a node field will appear. In the node field, a custom equation can be configured for Odoo to use when filtering who to include (and exclude) in this specific marketing campaign." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:-1 msgid "A filter node in Odoo Marketing Automation." msgstr "" @@ -778,133 +779,139 @@ msgid "Target an audience" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:5 -msgid "Delivering marketing campaigns to the *right* audience is paramount when trying to grow a business. The :guilabel:`Odoo Marketing Automation` application helps marketers to do just that by providing filtering tools, that can be as simple or as complex as necessary, to reach the right customers at the right time." +msgid "Delivering marketing campaigns to the right audience is paramount when trying to grow a business. The Odoo *Marketing Automation* application helps marketers to do just that by providing detailed filtering tools, which can be as simple (or as complex) as necessary, to reach the right customers at the right time." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:11 -msgid "Work with target filters" +msgid "Configure target filters" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:13 -msgid "When configuring the filters on a marketing campaign, there are some options that have an arrow icon beside them. The arrow signifies that the filter has more refined parameters within it." +msgid "When configuring the target filters on a marketing campaign, there are some options that have an :guilabel:`> (arrow)` icon beside them. The :guilabel:`> (arrow)` icon signifies that the particular filter has more refined parameters within it that can be customized." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:None -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:-1 msgid "The drop-down filter menu in the Marketing Automation application." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:20 -msgid "Filters can be extended by adding *branches* and *nodes*. A *node* adds another filtering parameter to a group of targeting conditions (e.g. a new line), and a *branch* creates a narrowly refined cluster of parameters, allowing filters to be grouped with *Any* or *All* statements." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:24 -msgid "Every time a new branch is created, there are two options:" +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:21 +msgid "Filters can be extended by adding *branches* and *nodes*. A *node* adds another filtering parameter to a group of targeting conditions (e.g. a new line), and a *branch* creates a narrowly refined cluster of parameters, allowing filters to be grouped with :guilabel:`ANY` or :guilabel:`ALL` statements." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:26 -msgid "Either the records can match :guilabel:`ALL` criteria for the upcoming rules (an AND statement where all criteria must match)." +msgid "Every time a new branch is created, there are two options:" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:29 -msgid "Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (an OR statement where only one of the criteria must match)." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:28 +msgid "Either the records can match :guilabel:`ALL` criteria for the upcoming rules (creating an AND statement where *all* criteria must match)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:32 -msgid "To change between these two options, simply click the drop-down arrow icon in the green box and select :guilabel:`Any` or :guilabel:`All`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:30 +msgid "Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (creating an OR statement where *only one* of the criteria must match)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:35 -msgid "To add a node, click on the :guilabel:`+ (plus sign icon)` and to add another branch click on the :guilabel:`... (ellipses icon)`. To exclude a :guilabel:`node` (or a :guilabel:`branch`), click on :guilabel:`x (delete)`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:33 +msgid "To change between these two options, simply click the drop-down arrow icon in the green box and select :guilabel:`ANY` or :guilabel:`ALL`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:44 +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:36 +msgid "To add a node, click on the :guilabel:`➕ (plus sign)` icon, and to add another branch click on the :guilabel:`⋯ (ellipses)` icon. To exclude a node or a branch, click on :guilabel:`✖ (delete)` icon to delete it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:45 msgid "Use cases" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:46 -msgid "The following scenarios below outline different combinations of filters a marketing campaign might commonly use." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:47 +msgid "The following scenarios outline different combinations of filters a marketing campaign might commonly use." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:50 -msgid "Scenario #1: Narrow the target down to new opportunities in the pipeline" +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:51 +msgid "Scenario #1: Narrow target down to new opportunities in the pipeline" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:52 -msgid "While in Edit mode on a campaign template form, select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, search for :guilabel:`Lead/Opportunity` and select it." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:53 +msgid "While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, search for :guilabel:`Lead/Opportunity`, and select it." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:56 -msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Type`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:57 +msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Then, click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Type`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:61 -msgid "Keep the second portion of the filter equation on the default :guilabel:`= (equal sign)`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:62 +msgid "Keep the second portion of the filter equation on the default :guilabel:`🟰 (equal sign)` icon." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:63 -msgid "Then, change the third (and final) portion of the filter equation from :guilabel:`Lead` to :guilabel:`Opportunity`. The number of :guilabel:`Records` that fit this specific filter equation will change as the equation is customized." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:64 +msgid "Next, change the third (and final) portion of the filter equation from :guilabel:`Lead` to :guilabel:`Opportunity`. The number of :guilabel:`Records` that fit this specific filter equation changes as the equation is customized." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:67 -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:103 -msgid "Add another node to this filter by clicking the :guilabel:`+ (plus sign)` to the right of the equation." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:68 +msgid "Add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of the equation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:70 -msgid "With \"new\" opportunities being the target of this filter, the second node will focus on only locating opportunities that are in the :guilabel:`New` stage of the pipeline. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Stage` from the field drop-down menu." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:71 +msgid "With \"new\" opportunities being the target of this filter, the second node will focus on *only* locating opportunities that are in the :guilabel:`New` stage of the pipeline. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Stage` from the field drop-down menu." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:75 -msgid "Once again, leave the second portion of the filter equation on :guilabel:`= (equal sign)`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:76 +msgid "Once again, leave the second portion of the filter equation on :guilabel:`🟰 (equal sign)` icon." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:77 -msgid "Lastly, highlight the default value in the third (and final) portion of the second filter equation and type in :guilabel:`New`. With that completed, Odoo will only target opportunities that are in the \"New\" stage of the pipeline." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:78 +msgid "Lastly, highlight the default value in the third (and final) portion of the second filter equation, and type in `New`. With that in place, Odoo only targets opportunities that are in the \"New\" stage of the pipeline." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:-1 msgid "A standard scenario using filters in the Odoo Marketing Automation app." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:86 -msgid "Scenario #2: Narrow the target down to the event attendees that purchased a specific ticket" +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:87 +msgid "Scenario #2: Narrow down target to event attendees who purchased a specific ticket" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:88 -msgid "While in Edit mode on a campaign template form, select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, scroll down (or search for) :guilabel:`Event` and select it." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:89 +msgid "While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, scroll down (or search for) :guilabel:`Event`, and select it." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:92 +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:93 msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Event`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:97 -msgid "Click the the default :guilabel:`= (equal sign)` in the second portion of the filter equation. This reveals a drop-down menu. On this menu, select :guilabel:`contains`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:98 +msgid "Click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation. This reveals a drop-down menu. From this drop-down menu, select :guilabel:`contains`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:100 -msgid "In the third (and final) empty portion of the filter equation, type in the name of the event(s) that you would like Odoo to consider for this campaign filter." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:101 +msgid "In the third (and final) empty portion of the filter equation, type in the name of the event(s) that Odoo should consider for this campaign filter." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:106 -msgid "The second node will focus on targeting this campaign to attendees who purchase a specific type of ticket to the aforementioned event(s) in the first filter equation. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that same drop-down menu, select :guilabel:`Name`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:104 +msgid "Then, add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of the equation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:112 -msgid "Once again, click the the default :guilabel:`= (equal sign)` in the second portion of the filter equation, and select :guilabel:`contains`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:107 +msgid "The second node will focus on targeting this campaign to attendees who purchase a specific type of ticket to the aforementioned event(s) mentioned in the first filter equation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:115 -msgid "Lastly, in the third (and final) portion of the second filter equation, which will be blank, type in the name of the ticket type that should be used for the filter. In this case, :guilabel:`Standard` is the name of the event ticket type for this sample filter." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:110 +msgid "To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that same drop-down menu, select :guilabel:`Name`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:114 +msgid "Once again, click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation, and select :guilabel:`contains`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:117 +msgid "Lastly, in the third (and final) portion of the second filter equation, which is blank, type in the name of the ticket type that should be used for the filter. In this case, :guilabel:`Standard` is the name of the event ticket type for this sample filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:-1 msgid "An event ticket filter in the Odoo Marketing Automation application." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:3 -msgid "Testing and running a campaign" +msgid "Testing/running campaigns" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5 @@ -912,39 +919,51 @@ msgid "Odoo gives users the ability to test marketing campaigns (and mailings) b msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:8 -msgid "First, open the :guilabel:`Marketing Automation` application and click on a campaign. Make sure the campaign already has activities configured on it (or build a campaign by following the directions here on :doc:`this documentation `). To start a test, click the :guilabel:`Launch a Test` button at the top of the template form." +msgid "First, open the :menuselection:`Marketing Automation` application, and select the desired campaign, which reveals that campaign's detail form." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:11 +msgid "On the campaign detail form, make sure the campaign already has activities configured (or build a campaign by following the directions here on :doc:`this documentation `)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:15 +msgid "To start a test, click the :guilabel:`Launch a Test` button at the top of the campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 msgid "Launch a test button in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:17 -msgid "When clicked, a pop-up window appears. In the dropdown field choose a specific record to run the test on, or create a brand new record by clicking the :guilabel:`Search More...` link at the bottom of the dropdown menu, and then click the :guilabel:`Create` button." -msgstr "" - #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21 -msgid "Once the record is selected, click :guilabel:`Continue`, and Odoo will redirect to the campaign test page." +msgid "When clicked, a :guilabel:`Launch a test` pop-up window appears. In the drop-down field, choose an existing record (or create a new one) to run the test on. To create a brand new record, click the :guilabel:`Search More...` link at the bottom of the drop-down menu, and then click the :guilabel:`Create` button." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:None -msgid "Test screen in Odoo Marketing Automation." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:28 -msgid "Here, the name of the :guilabel:`Record` being tested is visible, along with the precise time this test workflow was started. Beneath that is the first activity (or activities) in the workflow." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:26 +msgid "Doing so reveals a blank contact form, in which the :guilabel:`Name` and :guilabel:`Email` **must** be entered. When all the necessary information has been entered, click :guilabel:`Save`, and Odoo returns to the :guilabel:`Launch a test` pop-up, with that new record in the :guilabel:`Choose an existing record or create a new one to test` field." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31 -msgid "To start a test, click the :guilabel:`Run` icon beside the first activity in the workflow. When clicked, the page will reload, and Odoo will show the various results (and analytics) connected to that specific activity." +msgid "Once a record is selected, click :guilabel:`Continue`, and Odoo reveals the campaign test page." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "Test screen in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:37 +msgid "On the campaign test page, the name of the :guilabel:`Record` being tested is visible, along with the precise time this test workflow was started in the :guilabel:`Workflow Started On` field. Beneath that, in the :guilabel:`Workflow` section is the first activity (or activities) in the workflow that's being tested." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:42 +msgid "To start a test, click the :guilabel:`Run` button, represented by a :guilabel:`▶️ (play button)` icon beside the first activity in the workflow. When clicked, the page reloads, and Odoo shows the various results (and analytics) connected to that specific activity as they occur, in real-time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 msgid "Workflow test progress in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:39 -msgid "Once all the workflow activities are completed, the test will end and be moved to the :guilabel:`Completed` stage. To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:50 +msgid "Once all the workflow activities are completed, the test will end, and move to the :guilabel:`Completed` stage. To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button in the upper-left corner of the campaign test page." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3 @@ -952,115 +971,127 @@ msgid "Marketing activities" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5 -msgid "When creating a campaign in the :guilabel:`Marketing Automation` app, users can plan marketing activities such as email or SMS campaigns. To get started, navigate to the :guilabel:`Workflow` area, and click :guilabel:`Add New Activity`. A blank activity template will appear where parameters can be set for that specific activity." +msgid "When creating a campaign in the *Marketing Automation* app, users can plan marketing activities, such as email or SMS campaigns." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:10 -msgid "When :guilabel:`Add New Activity` is selected, a blank activity template will appear with the following customizable fields:" +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:8 +msgid "To get started, navigate to the bottom of a marketing automation campaign detail form, and click :guilabel:`Add New Activity`. Doing so reveals a :guilabel:`Create Activities` pop-up window. This pop-up window is a blank activity template, where specific parameters can be set for that particular activity." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:13 +msgid "The following fields are available in the :guilabel:`Create Activities` pop-up window (when :guilabel:`Add New Activity` is clicked):" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 msgid "An activity template in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:17 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20 msgid ":guilabel:`Activity Name`: the title of the activity." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:18 -msgid ":guilabel:`Activity Type`: choose between Email, Server Action (internal Odoo operation), or SMS." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21 +msgid ":guilabel:`Activity Type`: choose between `Email`, `Server Action` (internal Odoo operation), or `SMS`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:19 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:23 msgid ":guilabel:`Mail Template`: choose from pre-configured templates (or create a new one on-the-fly)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:24 msgid ":guilabel:`Trigger`: choose when this activity should be triggered." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25 msgid ":guilabel:`Expiry Duration`: configure to stop the actions after a specific amount of time (after the scheduled date). When selected, a :guilabel:`Cancel after` field appears, in which the user can choose how many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to cease after the initial date." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25 -msgid ":guilabel:`Activity Filter`: domain related to this activity (and all subsequent Child Activities)." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:29 +msgid ":guilabel:`Activity Filter`: domain related to this activity (and all subsequent child activities)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:27 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:31 msgid ":guilabel:`Applied Filter`: activity will *only* be performed if it satisfies the specified domain (filter)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:30 -msgid "After the activity's settings are fully configured, click :guilabel:`Save & Close` to finish creating the activity." -msgstr "" - #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:34 -msgid "Workflow activity" -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:36 -msgid "Once saved, the :guilabel:`Workflow Activity` will appear in Odoo, where each activity will be shown as a graph by default. The configured trigger time for that activity can be found to the left of the :guilabel:`Workflow Activity` card." +msgid "After the activity's settings are fully configured, click :guilabel:`Save & Close` to save the activity and return to the marketing automation campaign form, :guilabel:`Save & New` to save the activity and immediately create another one in a fresh :guilabel:`Create Activities` pop-up window, or :guilabel:`Discard` to delete the activity and return to the marketing automation campaign form." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40 -msgid "In the :guilabel:`Workflow Activity` section, there is also the number of activities that are successful or rejected. The :guilabel:`Success` and :guilabel:`Rejected` numbers are color-coded in the graph for easy reference (in green and red, respectively)." +msgid "Workflow activity" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:None +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:42 +msgid "Once an activity is saved, the :guilabel:`Workflow Activity` section appears at the bottom of the marketing automation campaign form. Each activity is displayed as a line graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:45 +msgid "The configured :guilabel:`Trigger` time for that activity can be found to the left of the :guilabel:`Workflow Activity` card in the :guilabel:`Workflow` section." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:48 +msgid "Once the activity has been triggered, a figure representing the number of :guilabel:`Success` or :guilabel:`Rejected` activities will be displayed to the right of the graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 msgid "Typical workflow activity in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:49 -msgid "If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`, there are more in-depth analytics beneath the :guilabel:`Workflow Activity` data detailing how many emails have been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:56 +msgid "If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`, there are more in-depth analytics beneath the activity graph data, detailing how many emails have been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:55 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:62 msgid "Child activities" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:57 -msgid "Odoo also has the option to :guilabel:`Add Child Activity`. *Child Activities* are sub-activities that are connected to (and triggered by) the activity above it, which is also known as its *Parent Activity*." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:61 -msgid "Odoo provides a number of triggering options to launch a :guilabel:`Child Activity` - all of which depend on the trigger configurations related to the parent activity. Under the desired parent activity, hover over :guilabel:`Add child activity`, and select the trigger:" -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:65 -msgid ":guilabel:`Add Another Activity`: instantly add another activity." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:66 -msgid ":guilabel:`Opened`: the next activity will be triggered if the (email) recipient opens the mailing." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:64 +msgid "There is also the option to add a *child activity* by clicking :guilabel:`Add child activity`, located at the bottom of each activity block in the :guilabel:`Workflow` section of a marketing automation form." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:68 -msgid ":guilabel:`Not Opened`: the next activity will be triggered if the recipient does not open the mailing." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:70 -msgid ":guilabel:`Replied`: the next activity will be triggered if the recipient replies to the mailing." +msgid "Child activities are sub-activities that are connected to (and triggered by) the activity above it, which is also known as its *parent activity*." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:71 -msgid ":guilabel:`Not Replied`: the next activity will be triggered if the recipient does not reply to the mailing." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:73 -msgid ":guilabel:`Clicked`: the next activity will be triggered if the recipient clicks on a link included in the mailing." +msgid "Odoo provides a number of triggering options to launch a child activity - all of which depend on the trigger configurations related to the parent activity. Under the desired parent activity, hover over :guilabel:`Add child activity`, and select any of the following triggers:" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75 +msgid ":guilabel:`Add Another Activity`: instantly add another activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:76 +msgid ":guilabel:`Opened`: the next activity will be triggered if the (email) recipient opens the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:78 +msgid ":guilabel:`Not Opened`: the next activity will be triggered if the recipient does not open the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:80 +msgid ":guilabel:`Replied`: the next activity will be triggered if the recipient replies to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:81 +msgid ":guilabel:`Not Replied`: the next activity will be triggered if the recipient does not reply to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:83 +msgid ":guilabel:`Clicked`: the next activity will be triggered if the recipient clicks on a link included in the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:85 msgid ":guilabel:`Not Clicked`: the next activity will be triggered if the recipient does not click on a link included in the mailing." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:77 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:87 msgid ":guilabel:`Bounced`: the next activity will be triggered if the mailing is bounced (not sent)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:79 -msgid "Once a trigger is selected, the user can configure the child activity (it has the same configuration options as a regular activity) and click :guilabel:`Save & Close`` to finish creating the child activity." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:89 +msgid "Once a trigger is selected, the user can configure the child activity (it has the same configuration options as a regular activity), and click :guilabel:`Save & Close` to finish creating the child activity, which will then be displayed in the :guilabel:`Workflow` section, in a slightly indented position beneath its parent activity." msgstr "" #: ../../content/applications/marketing/sms_marketing.rst:8 @@ -1095,7 +1126,7 @@ msgstr "" msgid "**GSM7** is the standard format, with a limit of 160 characters per message, that includes the following characters:" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:-1 msgid "GSM7 characters available in Odoo SMS Marketing." msgstr "" @@ -1119,7 +1150,7 @@ msgstr "" msgid "The number of SMSs a message represents will always be available in the database." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:-1 msgid "Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing." msgstr "" @@ -1131,7 +1162,7 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Buy Credits`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:-1 msgid "Buying credits for SMS Marketing in Odoo settings." msgstr "" @@ -1139,7 +1170,7 @@ msgstr "" msgid "Or go to :menuselection:`Settings --> View my Services`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:-1 msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings." msgstr "" @@ -1251,448 +1282,1008 @@ msgstr "" msgid "Yes, but it is not possible out-of-the-box. Odoo experts can help customize a database to allow for the use of a personal SMS provider. Please check our success packs `here `_." msgstr "" -#: ../../content/applications/marketing/surveys.rst:8 +#: ../../content/applications/marketing/social_marketing.rst:8 +msgid "Social Marketing" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials.rst:5 +msgid "Essentials" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:3 +msgid "Social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:5 +msgid "Social marketing campaigns help companies connect directly with the marketplace. These campaigns are helpful when introducing a new product to customers, explaining the value of a product or service, or when advertising an upcoming event or product release." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:9 +msgid "The most effective social marketing campaigns typically involve multiple channels to maximize content distribution, and Odoo's *Social Marketing* application acts as a singular control center to monitor, plan, post, track, and analyze all of the various content and content channels within a single dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:15 +msgid "Campaigns page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:17 +msgid "To access a complete overview of all social marketing campaigns, open the :menuselection:`Social Marketing` application, and click :menuselection:`Campaigns` from the header menu. Doing so reveals a separate page with every campaign in a default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 +msgid "View of the campaigns page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:25 +msgid "Each *stage* in the kanban view can be edited, by clicking the :guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located to the right of the stage title." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:29 +msgid "The **gear icon** *only* appears when the cursor hovers to the left of the **+ (plus sign)**. When the gear icon is clicked, a drop-down menu reveals the options: :guilabel:`Fold`, :guilabel:`Edit Stage`, and :guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:37 +msgid "Clicking :guilabel:`Fold` minimizes that specific stage's column. The stage column can be restored by clicking the folded version of it on the main :guilabel:`Campaigns` dashboard in the default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:41 +msgid "Selecting :guilabel:`Edit Stage` reveals a pop-up window, in which the name and the sequence of the stage can be modified. If changes are made, be sure to click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:44 +msgid "Clicking :guilabel:`Delete` removes the stage entirely." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:47 +msgid "To add a new stage to the pipeline, side-scroll to the right on the :guilabel:`Campaigns` dashboard, click :guilabel:`Add a Column`, enter in the desired information, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:52 +msgid "The same social marketing campaign information on the :guilabel:`Campaigns` dashboard can also be viewed as a list, by selecting the :guilabel:`List` option, located under the search bar, in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:57 +msgid "Create social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:59 +msgid "First, open the :menuselection:`Social Marketing` application, and select :guilabel:`Campaigns` from the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:62 +msgid "On the :guilabel:`Campaigns` dashboard, a new campaign can be created by clicking the quick add :guilabel:`+ (plus sign)` located in the top-right corner of each stage in the pipeline, visible in the kanban view. Campaigns can also be created by clicking :guilabel:`Create` in the upper-left corner of the :guilabel:`Campaigns` dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:67 +msgid "Both options reveal a new campaign detail window directly on the :guilabel:`Campaigns` dashboard when clicked." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 +msgid "View of the quick add option for campaigns in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:74 +msgid "Here, the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and :guilabel:`Tags` can be entered. When all modifications are complete, click :guilabel:`Add` to add the campaign to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:78 +msgid "Edit social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:80 +msgid "In order to edit a campaign in greater detail, and create/send various forms of communications related to it, the template page for that campaign must be accessed and modified, accordingly. There are multiple ways to access a template page for a campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:84 +msgid "After entering the pertinent information in the :guilabel:`Quick Add` campaign drop-down, click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:86 +msgid "Simply select the desired campaign from the :guilabel:`Campaigns` dashboard in list or kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:88 +msgid "On the :guilabel:`Campaigns` dashboard in the kanban view, select the :guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and select :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:91 +msgid "Any of the above routes will reveal the *Campaign Template* page for that specific campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:94 +msgid "Social marketing campaign templates" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:96 +msgid "On a *Campaign Template* page, numerous elements can be customized/modified, and various forms of communications can be created, modified, and sent or scheduled. Below is a sample of a completed campaign template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 +msgid "View of a sample campaign template page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:105 +msgid "In order for the :guilabel:`Send New Mailing` option to appear on campaign templates, make sure the *Mailing Campaigns* feature is enabled in the *Email Marketing* app. To do that, navigate to :menuselection:`Email Marketing --> Configuration --> Settings`, activate :guilabel:`Mailing Campaigns`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:111 +msgid "In order for the :guilabel:`Send SMS` option to appear, the Odoo *SMS Marketing* application must be installed on the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:115 +msgid "Add content and communications to campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:117 +msgid "If the proper settings and applications are installed (as instructed above), there are four forms of communication/content options that can be added to campaigns. Each of these options are displayed as buttons in the upper-left corner of the campaign template page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:121 +msgid ":guilabel:`Send New Mailing`: reveals a blank email template on a separate page, in which the message can be fully customized in a variety of ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:123 +msgid ":guilabel:`Send SMS`: reveals a blank SMS template on a separate page, in which a SMS communication can be created and configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:125 +msgid ":guilabel:`Send Social Post`: reveals a blank social post template on a separate page, in which a post can be created, and applied to social media accounts that are already connected to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:128 +msgid ":guilabel:`Push Notification`: reveals a similar blank social post template on a separate page, however, the :guilabel:`Push Notification` options are already pre-selected in the :guilabel:`Post on` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:132 +msgid "Whichever form of communication is created, once it's completed, Odoo returns to the :guilabel:`Campaign Template` page, showcasing that new content in its corresponding tab (e.g. :guilabel:`Mailings`, :guilabel:`SMS`, :guilabel:`Social Media`, and/or :guilabel:`Push Notifications`)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:137 +msgid "As content and communications are added to a campaign, tabs for those specific mediums appear, along with a variety of analytical smart buttons (e.g. :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Leads`, etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:141 +msgid "These smart buttons, located at the top of the template, display different metrics related to the campaign, and its various communications and content. Clicking any smart button reveals a separate page dedicated to that particular element of the campaign, allowing for quicker, more organized analysis." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:147 +msgid "The Odoo *Social Marketing* app is integrated with other Odoo applications, such as *Sales*, *Invoicing*, *CRM*, and *Website*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:151 +msgid ":doc:`/applications/marketing/social_marketing/essentials/social_essentials`" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:3 +msgid "Social marketing essentials" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:5 +msgid "Odoo's *Social Marketing* helps content marketers create and schedule posts, manage various social media accounts, analyze content effectiveness, and engage directly with social media followers in one, centralized location." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:10 +msgid "Add social media accounts" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:12 +msgid "In order to create posts, each social media account must be added as a stream in the Odoo *Social Marketing* application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:16 +msgid "Add a social media stream" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:18 +msgid "Add a social media account as a stream by navigating to :menuselection:`Social Marketing` and then select the :guilabel:`Add A Stream` button located in the upper left corner" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:21 +msgid "When :guilabel:`Add A Stream` is clicked, the following pop-up appears, displaying the different social media outlets to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "View of the pop-up that appears when 'Add a Stream' is selected in Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:29 +msgid "Additional social media outlet options are available depending on your version of Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:31 +msgid "From this pop-up, select a social media option: :guilabel:`Facebook`, :guilabel:`LinkedIn`, or :guilabel:`Twitter`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:34 +msgid "Then, Odoo navigates directly to that specific social media outlet's authorization page, where permission must be granted, in order for Odoo to add that particular social media account to the *Social Marketing* application as a stream on the main dashboard of the app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:39 +msgid "A Facebook page can be added as long as the Facebook account that grants permission is the administrator for the page. Also, different pages can be added for different streams." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:42 +msgid "Once permission is granted, Odoo navigates back to the :guilabel:`Feed` on the main :guilabel:`Social Marketing` dashboard, and a new column with that account's posts are automatically added." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:46 +msgid "From here, new accounts and/or streams can be added and managed at any time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Example of how a populated stream-filled dashboard looks in Odoo Social Marketing" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:53 +msgid "Adding social media accounts to the feed also links that specific social media platform's KPIs (if the platform has them). To get redirected to the statistics and metrics related to any social account, click on :guilabel:`Insights`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "The insights link that can be accessed for each social media stream added in Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:62 +msgid "Create and publish social media posts in Odoo" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:64 +msgid "To create content for social media accounts in the :menuselection:`Social Marketing` application, click the :guilabel:`New Post` button located in the upper-left corner of the main dashboard, or navigate to :menuselection:`Posts --> Create` from the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:68 +msgid "Either route reveals a blank post template page that can be customized and configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "How to create a social media post directly through Odoo" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:76 +msgid "Post template" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:78 +msgid "The post template page has many different options avaiable." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:81 +msgid "'Your Post' section" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:83 +msgid "The first option is the :guilabel:`Post on` field. This is where it's determined on what social media account(s), or on which website(s) via push notification, this post will be published." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:87 +msgid "In order for the :guilabel:`Push Notification` option to appear, make sure the *Enable Web Push Notifications* feature is enabled in the *Website* app. To do that, navigate to :menuselection:`Website --> Configuration --> Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the corresponding fields, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:92 +msgid "Odoo automatically provides every available social media account that's been linked to the database as an option in this section, as well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:96 +msgid "If a social media account hasn't been added as a stream to the *Social Marketing* application, it will not appear as an option on the post template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:99 +msgid "Next, there's the :guilabel:`Message` field. This is where the main content of the post is created." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:101 +msgid "Type the desired message for the post in this field. To the right, as the :guilabel:`Message` field is populated, Odoo displays visual samples of how the post will look on all the previously selected social media accounts from the :guilabel:`Post on` field above." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:106 +msgid "Emojis can also be added directly to the text in the :guilabel:`Message` field. Just click the :guilabel:`emoji (smiley face) icon`, located on the line of the :guilabel:`Message` field to the far right. Clicking this icon reveals a drop-down containing numerous emojis to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:110 +msgid "If images are to be used in the post, click the :guilabel:`ATTACH IMAGES` link beneath the :guilabel:`Message` field, and Odoo reveals a pop-up window. In this pop-up, the desired image must be chosen, and then uploaded." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:114 +msgid "A preview of the entire post, text and image (if applicable), is instantly displayed in the visual preview of the post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:117 +msgid "Next, there's the option to attach this post to a specific marketing campaign in the database in the :guilabel:`Campaign` field. Click the blank line next to :guilabel:`Campaign` to reveal the previously configured campaigns to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:122 +msgid "A new campaign can be created, as well, by typing the name of the new campaign on the blank :guilabel:`Campaign` field, and selecting :guilabel:`Create` from the drop-down field menu. Or, select :guilabel:`Create and edit` from the menu to further customize that newly-created campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:128 +msgid "A social post does *not* need to be attached to a campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:130 +msgid "Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to have Odoo publish the post immediately, or :guilabel:`Schedule later` to have Odoo publish the post at a later date and time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:134 +msgid "If :guilabel:`Schedule later` is selected, Odoo reveals a new field beneath it (the :guilabel:`Scheduled post date` field). Clicking that empty field reveals a pop-up calendar, in which a future date and time is designated. At which time, Odoo will promptly publish the post on the pre-determined social media accounts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:139 +msgid "Click on the desired date to schedule the post for that day. Then, either select and customize the default time in the :guilabel:`Scheduled post date` field manually. Or, adjust the desired post time, by clicking the :guilabel:`scheduling (clock) icon` located on the calendar pop-up, and choose the desired time for Odoo to publish this post on that future date." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:144 +msgid "If scheduling a post, remember to hit :guilabel:`Schedule` in the upper left of the post template. Doing so, locks in that specific date/time for Odoo to send the post, and it changes the status of the post to :guilabel:`Scheduled`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:149 +msgid "Also, when :guilabel:`Schedule` is clicked, a number of analytical smart buttons appear on the post page. Each one offers up a detailed anaylsis of the corresponding metric (e.g. :guilabel:`Leads`, :guilabel:`Revenues`, etc.). These same smart buttons appear when a post is officially published, as well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:155 +msgid "'Web Notification Options' section" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:157 +msgid "If any :guilabel:`Push Notifications` are selected in the :guilabel:`Post on` field, Odoo provides another section of settings/options at the bottom of the post template. It should be noted that *none* of these fields are required." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:161 +msgid "The first field is for a :guilabel:`Push Notification Title`. This is text that is displayed as the title of the push notification whenever it's sent. Odoo displays a visual preview of this title, if one is created." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:165 +msgid "To designate a specific page on the website that should trigger this push notification, enter that page's URL in the :guilabel:`Push Target URL` field. Then, once a visitor reaches that specific page, Odoo will display the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:169 +msgid "Below that field is the option to add a custom :guilabel:`Push Icon Image`. This is an icon that appears beside the push notification. By default, Odoo uses a \"smiley face\" as the icon." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:172 +msgid "To upload a new image, click the :guilabel:`Edit (pencil) icon` when the :guilabel:`Push Icon Image` field is hovered over with the cursor. Then, proceed to locate and upload the desired image, and Odoo automatically displays a preview of how the icon will appear on the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:176 +msgid "Next, there is the option to :guilabel:`Send at Visitors' Timezone`. If enabled, Odoo will send it at the appropriate, pre-determined time, taking the visitor's location into consideration." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:180 +msgid "Save, post, and test notification options" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:182 +msgid "When all the modifications have been made, and the post is completed, either click :guilabel:`Save` to save the post as a *Draft*. Or, if the post is ready to be published immediately, click :guilabel:`Post`, and Odoo automatically publishes the post on the pre-determined social media accounts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:187 +msgid "There is also the option to :guilabel:`Test Notification`, if a :guilabel:`Push Notification` was selected in the :guilabel:`Post on` field. Clicking that, provides a quick example of how the notification will appear for visitors." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:192 +msgid "Social post status bar" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:194 +msgid "In the top-right of the :guilabel:`Post Template` page is the :guilabel:`Status Bar`. This displays the current status of the post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:197 +msgid "When :guilabel:`Save` is clicked, the post is in the *Draft* status." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:199 +msgid "If the post is scheduled to be sent at a future date/time, and the :guilabel:`Schedule` button has been clicked, the status of the post is *Scheduled*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:202 +msgid "If the post is in the process of currently being published or sent, the status of the post is *Posting*. And, lastly, if the post has already been published or sent, the status is *Posted*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:206 +msgid "Posts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:208 +msgid "To see a complete overview of posts, go to Odoo :menuselection:`Social Marketing`, and click :menuselection:`Posts` in the header menu. Here, every post that has been created and posted with Odoo is available." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:212 +msgid "There are four different view options for :guilabel:`Posts` page data: *kanban*, *calendar*, *list*, and *pivot*. The view options are located in the upper right corner of the :guilabel:`Posts` page, beneath the search bar." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:218 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:220 +msgid "By default, Odoo displays the posts in a kanban view. The information on this page can be sorted even further, via the :guilabel:`Filters` and :guilabel:`Group by` drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "Kanban view of the posts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:227 +msgid "Calendar view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:229 +msgid "The calendar view option displays a visual representation in a calendar format of when posts were published, or are scheduled to be published. This option provides a clear overview of any planned day, week, or month, and Odoo displays all drafted, scheduled, and published posts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "Example of the calendar view in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:237 +msgid "List view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:239 +msgid "The list view option is similar to the kanban option, but instead of individual blocks, all the post information is displayed in a clear, list layout. Each line of the list displays the :guilabel:`Social Accounts`, :guilabel:`Message`, and :guilabel:`Status` of every post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "View of the list option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:247 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:249 +msgid "The pivot view option provides a fully customizable grid table, where different measures of data can be added and analyzed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "View of the pivot option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:256 +msgid "The pivot view option provides numerous analytical options, allowing for in-depth, detailed analysis of various posts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:259 +msgid "Click on any :guilabel:`+ (plus sign) icon` next to a line in the pivot table to reveal more metric options to add to the grid." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:262 +msgid "While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is available, located to the right of the :guilabel:`Measures` drop-down." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:265 +msgid "When clicked, a pop-up appears, where the option to add this information to a current spreadsheet is available. The option to create a new spreadsheet for this information on-the-fly is also available in this pop-up, as well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:269 +msgid "Next to the :guilabel:`Insert in Spreadsheet` are three view options, specific to the pivot view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:272 +msgid "From left to right, the options are:" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:274 +msgid ":guilabel:`Flip Axis`, which switches the *X* and *Y* axis in the grid table." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:275 +msgid ":guilabel:`Expand All`, which expands each line in the grid, revealing more detailed information related to it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:277 +msgid ":guilabel:`Download`, which, when clicked, instantly downloads the pivot table as a spreadsheet." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:281 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:283 +msgid "To see a complete overview of all the people who have visited the website(s) connected to the database, navigate to :menuselection:`Social Marketing --> Visitors` in the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "View of the Visitors page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:290 +msgid "Here, Odoo provides a detailed layout of all the visitors' pertinent information in a default kanban view. This same information can be sorted via the :guilabel:`Filters` and :guilabel:`Group By` options." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:294 +msgid "The visitor data can also be viewed as a list or a graph. Those view options are located in the upper-right corner of the :guilabel:`Visitors` page beneath the search bar." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:298 +msgid "Social media page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:300 +msgid "Go to :menuselection:`Configuration --> Social Media` to see a collection of all social media options: :guilabel:`Facebook`, :guilabel:`LinkedIn`, :guilabel:`Twitter`, and :guilabel:`Push Notifications`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "View of the social media page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:308 +msgid "If no account has been linked to any particular social media, click :guilabel:`Link Account` to proceed through the linking process." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:312 +msgid "Social accounts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:314 +msgid "To see a list of all social accounts linked to the database, go to :menuselection:`Configuration --> Social Accounts`. This page will display the :guilabel:`Medium Name` and the :guilabel:`Social Media` platform it is associated with." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "View of the social accounts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:322 +msgid "To edit/modify any social accounts, simply select the desired account from the list on this page, and proceed to make any adjustments necessary. Don't forget to hit :guilabel:`Save` to secure any changes." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:327 +msgid "Social streams page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:329 +msgid "Navigate to :menuselection:`Configuration --> Social Streams` to reveal a separate page containing all of the social media streams that have been added to the main dashboard of the *Social Marketing* app, accessible via the :guilabel:`Feed` option in the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:337 +msgid "Here, the social stream information is organized in a list with the :guilabel:`Social Media`, the :guilabel:`Title` of the stream, and the :guilabel:`Type` of the stream (e.g. :guilabel:`Posts`, :guilabel:`Keyword`, etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:341 +msgid "To modify any stream's information, simply click the desired stream from the list, and proceed to make any necessary adjustments. Don't forget to hit :guilabel:`Save` to secure any changes." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:345 +msgid ":doc:`/applications/marketing/social_marketing/essentials/social_campaigns`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:5 msgid "Surveys" msgstr "" -#: ../../content/applications/marketing/surveys.rst:11 +#: ../../content/applications/marketing/surveys.rst:8 msgid "`Odoo Tutorials: Surveys `_" msgstr "" -#: ../../content/applications/marketing/surveys/overview.rst:5 -msgid "Overview" -msgstr "" - -#: ../../content/applications/marketing/surveys/overview/create.rst:3 +#: ../../content/applications/marketing/surveys/create.rst:3 msgid "Survey essentials" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:5 +#: ../../content/applications/marketing/surveys/create.rst:5 msgid "Companies often use surveys to collect valuable information from their customers and employees, which in turn, allows them to make more informed business decisions." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:8 +#: ../../content/applications/marketing/surveys/create.rst:8 msgid "In Odoo, surveys are used to collect customer feedback, evaluate the success of a recent event, measure the satisfaction of customers (or employees), and gain more insight into shifting market sentiments." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:13 +#: ../../content/applications/marketing/surveys/create.rst:13 msgid "Getting started" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:15 +#: ../../content/applications/marketing/surveys/create.rst:15 msgid "To begin, open the :guilabel:`Surveys` application and click :guilabel:`Create`. Odoo then redirects the page to a blank survey template form." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:18 +#: ../../content/applications/marketing/surveys/create.rst:18 msgid "On the survey form, add a :guilabel:`Survey Title` and then add a cover image to the survey by hovering over the photo icon and clicking on the :guilabel:`Edit (pencil)` icon. When the file explorer window opens, choose an image from the local files." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:22 +#: ../../content/applications/marketing/surveys/create.rst:22 msgid "Below the :guilabel:`Survey Title` are various tabs in which the survey questions and format can be created and customized. These tabs are labeled as follows:" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:25 +#: ../../content/applications/marketing/surveys/create.rst:25 msgid ":guilabel:`Questions`: the list of questions to be asked in the survey" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:26 +#: ../../content/applications/marketing/surveys/create.rst:26 msgid ":guilabel:`Description`: contextual information to aid in understanding the survey" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:27 +#: ../../content/applications/marketing/surveys/create.rst:27 msgid ":guilabel:`Options`: choices for survey respondents to answer the questions" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:None +#: ../../content/applications/marketing/surveys/create.rst:-1 msgid "Various tabs that can be found on the survey template page." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:34 +#: ../../content/applications/marketing/surveys/create.rst:34 msgid "Questions tab" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:36 +#: ../../content/applications/marketing/surveys/create.rst:36 msgid "Add questions and sections to the survey in the :guilabel:`Questions` tab. A section divides the survey into parts in order to visually group similar questions together. To make a section, click :guilabel:`Add a section` and type in a section name. Then, add questions or drag and drop questions into the divided sections." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:41 +#: ../../content/applications/marketing/surveys/create.rst:41 msgid "Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and Questions` pop-up to create and customize the survey question." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:None +#: ../../content/applications/marketing/surveys/create.rst:-1 msgid "The survey question pop-up window." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:49 +#: ../../content/applications/marketing/surveys/create.rst:49 msgid "Create questions" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:51 +#: ../../content/applications/marketing/surveys/create.rst:51 msgid "In the :guilabel:`Create Sections and Questions` pop-up, type the question in the :guilabel:`Question` field. Then, choose the :guilabel:`Question Type`. A preview of how the question type looks is shown in the preview window." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:55 +#: ../../content/applications/marketing/surveys/create.rst:55 msgid "Choose from the following :guilabel:`Question Types`:" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:57 +#: ../../content/applications/marketing/surveys/create.rst:57 msgid ":guilabel:`Multiple Lines Text Box`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:58 +#: ../../content/applications/marketing/surveys/create.rst:58 msgid ":guilabel:`Single Line Text Box`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:59 +#: ../../content/applications/marketing/surveys/create.rst:59 msgid ":guilabel:`Numerical Value`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:60 +#: ../../content/applications/marketing/surveys/create.rst:60 msgid ":guilabel:`Date`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:61 +#: ../../content/applications/marketing/surveys/create.rst:61 msgid ":guilabel:`Datetime`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:62 +#: ../../content/applications/marketing/surveys/create.rst:62 msgid ":guilabel:`Multiple choice: only one answer`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:63 +#: ../../content/applications/marketing/surveys/create.rst:63 msgid ":guilabel:`Multiple choice: multiple answers allowed`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:64 +#: ../../content/applications/marketing/surveys/create.rst:64 msgid ":guilabel:`Matrix`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:67 +#: ../../content/applications/marketing/surveys/create.rst:67 msgid "Different features appear in the :guilabel:`Answers` and :guilabel:`Options` tabs, depending on the :guilabel:`Question Type` chosen. However, the :guilabel:`Description` tab always remains the same, regardless of what question is chosen." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:72 +#: ../../content/applications/marketing/surveys/create.rst:72 msgid "Create sections and questions" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:74 +#: ../../content/applications/marketing/surveys/create.rst:74 msgid "Once a :guilabel:`Question Type` has been selected, there are three possible tabs where information can be customized for the question. These include the :guilabel:`Answers` (if applicable), :guilabel:`Description`, and :guilabel:`Options` tabs." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:78 +#: ../../content/applications/marketing/surveys/create.rst:78 msgid "Each tab offers a variety of different features depending on what :guilabel:`Question Type` was chosen." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:81 +#: ../../content/applications/marketing/surveys/create.rst:81 msgid "For example, in the :guilabel:`Options` tab, the following options may appear:" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:83 +#: ../../content/applications/marketing/surveys/create.rst:83 msgid ":guilabel:`Mandatory Answer`: the question must be answered." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:84 +#: ../../content/applications/marketing/surveys/create.rst:84 msgid ":guilabel:`Matrix Type`: for matrix-type questions, select if one choice or multiple choices can be selected per row." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:86 +#: ../../content/applications/marketing/surveys/create.rst:86 msgid ":guilabel:`Number of columns`: select how many columns are displayed." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:87 +#: ../../content/applications/marketing/surveys/create.rst:87 msgid ":guilabel:`Images on answers`: allow images on the answer options." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:88 +#: ../../content/applications/marketing/surveys/create.rst:88 msgid ":guilabel:`Conditional Display`: determine if the question is displayed based on the participant's answer to a previous question." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:90 +#: ../../content/applications/marketing/surveys/create.rst:90 msgid ":guilabel:`Show Comments Field`: allow the participant to type a comment in a text box." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:91 +#: ../../content/applications/marketing/surveys/create.rst:91 msgid ":guilabel:`Question Time Limit`: for live session surveys, set a time limit for the question." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:94 +#: ../../content/applications/marketing/surveys/create.rst:94 msgid "Conditional Display" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:96 +#: ../../content/applications/marketing/surveys/create.rst:96 msgid ":guilabel:`Conditional Display` means the question is only displayed if the specified conditional answer has been selected in a previous question." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:99 +#: ../../content/applications/marketing/surveys/create.rst:99 msgid "When the box next to :guilabel:`Conditional Display` is selected, the :guilabel:`Triggering Question` field appears. Select a question from the survey." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:102 +#: ../../content/applications/marketing/surveys/create.rst:102 msgid "Then, a :guilabel:`Triggering Answer` field appears. Here, select which answer will trigger this :guilabel:`Conditional Display` question." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:106 +#: ../../content/applications/marketing/surveys/create.rst:106 msgid "Options tab" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:108 +#: ../../content/applications/marketing/surveys/create.rst:108 msgid "Back on the main survey template form, under the :guilabel:`Options` tab, there are different sections of settings that can be modified." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:111 +#: ../../content/applications/marketing/surveys/create.rst:111 msgid "The sections include:" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:113 +#: ../../content/applications/marketing/surveys/create.rst:113 msgid ":guilabel:`Questions`: focuses on the overall presentation of the survey" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:114 +#: ../../content/applications/marketing/surveys/create.rst:114 msgid ":guilabel:`Scoring`: decides how the survey is scored" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:115 +#: ../../content/applications/marketing/surveys/create.rst:115 msgid ":guilabel:`Candidates`: manages access to the survey" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:116 +#: ../../content/applications/marketing/surveys/create.rst:116 msgid ":guilabel:`Live Session`: enables the survey into a real-time group activity." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:119 +#: ../../content/applications/marketing/surveys/create.rst:119 msgid "Questions" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:121 +#: ../../content/applications/marketing/surveys/create.rst:121 msgid "First, select the :guilabel:`Layout` of the survey. The following options can be chosen:" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:123 +#: ../../content/applications/marketing/surveys/create.rst:123 msgid ":guilabel:`One page with all the questions`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:124 +#: ../../content/applications/marketing/surveys/create.rst:124 msgid ":guilabel:`One page per section`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:125 +#: ../../content/applications/marketing/surveys/create.rst:125 msgid ":guilabel:`One page per question`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:127 +#: ../../content/applications/marketing/surveys/create.rst:127 msgid "If either the :guilabel:`One page per section` or :guilabel:`One page per question` options are chosen, then the :guilabel:`Back Button` option appears. If selected, the :guilabel:`Back Button` option allows the participant to go back to a question during the survey." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:131 +#: ../../content/applications/marketing/surveys/create.rst:131 msgid "Under the :guilabel:`Layout` options is the :guilabel:`Progression Mode` setting, which indicates how the participant's progress during the survey is displayed. It is shown as either a :guilabel:`Percentage` or a :guilabel:`Number`." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:135 +#: ../../content/applications/marketing/surveys/create.rst:135 msgid "Next, there is an option available to add a :guilabel:`Survey Time Limit`. To implement this option, simply check the box, and enter the amount of time (in minutes) participants have to complete the survey." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:139 +#: ../../content/applications/marketing/surveys/create.rst:139 msgid "After the :guilabel:`Survey Time Limit` option is a section labeled :guilabel:`Selection`. Here, questions can be :guilabel:`Randomized per section`, in other words, the number of random questions can be configured by section. This mode is ignored in a live session." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:144 -#: ../../content/applications/marketing/surveys/overview/scoring.rst:56 +#: ../../content/applications/marketing/surveys/create.rst:144 +#: ../../content/applications/marketing/surveys/scoring.rst:56 msgid ":doc:`time_random`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:147 +#: ../../content/applications/marketing/surveys/create.rst:147 msgid "Scoring" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:149 +#: ../../content/applications/marketing/surveys/create.rst:149 msgid "The following options are available when deciding how a :guilabel:`Scoring` method:" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:151 +#: ../../content/applications/marketing/surveys/create.rst:151 msgid ":guilabel:`No scoring`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:152 +#: ../../content/applications/marketing/surveys/create.rst:152 msgid ":guilabel:`Scoring with answers at the end`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:153 +#: ../../content/applications/marketing/surveys/create.rst:153 msgid ":guilabel:`Scoring without answers at the end`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:155 +#: ../../content/applications/marketing/surveys/create.rst:155 msgid "If either the :guilabel:`Scoring with answers at the end` or :guilabel:`Scoring without answers at the end` options are selected, a :guilabel:`Success %` field appears. Set the percentage of correct answers needed to pass the survey." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:159 +#: ../../content/applications/marketing/surveys/create.rst:159 msgid "Next, there is the option to make the survey a certification. To do so, check the box next to the option labeled :guilabel:`Is a Certification`, and two additional fields appear. Select a color theme in the :guilabel:`Certification Template` field and then choose an :guilabel:`Email Template`. When a participant passes the certification with the required score, an email from Odoo will automatically be sent to that person using the selected email template." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:165 +#: ../../content/applications/marketing/surveys/create.rst:165 msgid "If the :guilabel:`Give Badge` feature is enabled and the :guilabel:`Certification Badge` is set, the survey participant also receives a badge upon passing the certification." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:169 -#: ../../content/applications/marketing/surveys/overview/time_random.rst:48 +#: ../../content/applications/marketing/surveys/create.rst:169 +#: ../../content/applications/marketing/surveys/time_random.rst:48 msgid ":doc:`scoring`" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:172 +#: ../../content/applications/marketing/surveys/create.rst:172 msgid "Candidates" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:174 +#: ../../content/applications/marketing/surveys/create.rst:174 msgid "To determine access to the survey, the :guilabel:`Access Mode` has two options to choose between: :guilabel:`Anyone with the link` and :guilabel:`Invited people only`." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:177 +#: ../../content/applications/marketing/surveys/create.rst:177 msgid "Below the :guilabel:`Appraisal Managers Only` checkbox is the :guilabel:`Login Required` option to require a login to participate in the survey. If this option is activated, an :guilabel:`Attempts Limit` field also populates, in which the number of survey attempts is defined for the participant." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:182 +#: ../../content/applications/marketing/surveys/create.rst:182 msgid "Live Session" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:184 +#: ../../content/applications/marketing/surveys/create.rst:184 msgid "The :guilabel:`Live Session` section is dedicated to users who are conducting surveys in real-time, wherein they directly engage with and collect answers from a live audience." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:187 +#: ../../content/applications/marketing/surveys/create.rst:187 msgid "Customize the :guilabel:`Session Code` here; this code is needed for participants to access the live session survey. Reward participants for quick answers by selecting the checkbox labeled :guilabel:`Reward quick answers`. By checking it, attendees will get more points if they answer quickly." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:193 +#: ../../content/applications/marketing/surveys/create.rst:193 msgid "Description tab" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:195 +#: ../../content/applications/marketing/surveys/create.rst:195 msgid "Back on the main survey template page is the :guilabel:`Description` tab, where a custom description of the survey can be added. This is displayed beneath the title on the survey's homepage, which is on the front end of the website made through the Odoo :guilabel:`Website` app." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:200 +#: ../../content/applications/marketing/surveys/create.rst:200 msgid "Test and share the survey" msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:202 +#: ../../content/applications/marketing/surveys/create.rst:202 msgid "Once the survey is created and saved, run a test to check for possible errors before finally sending it out to the participants by clicking :guilabel:`Test` in the upper left corner of the survey template page." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:206 +#: ../../content/applications/marketing/surveys/create.rst:206 msgid "When activated, Odoo redirects the page to a test version of the survey on the front end of the website. This page displays how the survey will look to participants. Proceed to run through the survey, like a normal participant, to check for errors." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:210 +#: ../../content/applications/marketing/surveys/create.rst:210 msgid "To return to the survey template form in the backend, simply click the :guilabel:`This is a test survey. Edit Survey` link in the blue banner along the top of the page. Once Odoo redirects the page to the survey template in the backend, make any further changes, as needed, before officially sending the survey out to participants." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:215 +#: ../../content/applications/marketing/surveys/create.rst:215 msgid "When the survey is ready to be shared with the audience, click the :guilabel:`Start Survey` button in the upper-left corner of the survey template form. Then, click :guilabel:`Share`." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:218 +#: ../../content/applications/marketing/surveys/create.rst:218 msgid "In the pop-up window, add the survey recipients in the :guilabel:`Recipients` field (for existing contacts in the Odoo database) or the :guilabel:`Additional emails` field (for contacts that do not want to be listed in the Odoo database). Finally, click :guilabel:`Send`." msgstr "" -#: ../../content/applications/marketing/surveys/overview/create.rst:222 +#: ../../content/applications/marketing/surveys/create.rst:222 msgid "As answers are received, check them by clicking the :guilabel:`Answers` smart button on the survey template form, or the :guilabel:`See Results` button in the upper left corner. To end the survey, click the :guilabel:`Close` button on the survey template form." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:3 +#: ../../content/applications/marketing/surveys/scoring.rst:3 msgid "Scoring surveys" msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:5 +#: ../../content/applications/marketing/surveys/scoring.rst:5 msgid "To measure a survey participant's performance, knowledge, or overall satisfaction, Odoo ascribes points to survey answers. At the end of the survey, these points are summed up, resulting in the participant's final score." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:9 +#: ../../content/applications/marketing/surveys/scoring.rst:9 msgid "To add points to questions, open the :guilabel:`Surveys` application, choose the desired survey form, and then click on the :guilabel:`Options` tab. Under the :guilabel;`Scoring` section, choose between :guilabel:`Scoring with answers at the end` or :guilabel:`Scoring without answers at the end`." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:14 +#: ../../content/applications/marketing/surveys/scoring.rst:14 msgid ":guilabel:`Scoring with answers at the end` shows the survey participant their answers after completing the survey, and displays which questions they got right or wrong. On questions where there was an incorrect answer, the correct answer will be highlighted." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:18 +#: ../../content/applications/marketing/surveys/scoring.rst:18 msgid ":guilabel:`Scoring without answers at the end` does not show the survey participant their answer choices after completing the survey, only their final score." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:21 +#: ../../content/applications/marketing/surveys/scoring.rst:21 msgid "To indicate correct answers, click on the :guilabel:`Questions tab` and choose a question. In the question form, check the :guilabel:`Is a correct answer` box for the choice that is the correct answer and attach a score value." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:25 +#: ../../content/applications/marketing/surveys/scoring.rst:25 msgid "Back on the :guilabel:`Options` tab of the survey, set the :guilabel:`Success %`. The percentage entered determines what percentage of correct answers is needed to pass the survey." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:28 +#: ../../content/applications/marketing/surveys/scoring.rst:28 msgid "Further on the :guilabel:`Options` tab of the survey, survey administrators can also choose to make the survey a certification. A certification indicates that the survey asks questions to test the participants' knowledge level on a subject." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:32 +#: ../../content/applications/marketing/surveys/scoring.rst:32 msgid "When enabling the :guilabel:`Is a certification` option, choose a :guilabel:`Certification email template`. The certification will automatically be emailed using this email template to users who pass the survey with a final score that is greater than or equal to the set :guilabel:`Success %`." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:36 +#: ../../content/applications/marketing/surveys/scoring.rst:36 msgid "In the :guilabel:`Candidates` section, participants can be required to log in to take the survey. If the :guilabel:`Login Required` setting is enabled, two new options appear: the :guilabel:`Attempts Limit` checkbox, which limits the number of times a participant can attempt the survey, and the option to :guilabel:`Give Badge`, located beneath the :guilabel:`Certification` options in the :guilabel:`Scoring` section." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:None +#: ../../content/applications/marketing/surveys/scoring.rst:-1 msgid "Setting the Required Score (percentage), login required, and certification template." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:46 +#: ../../content/applications/marketing/surveys/scoring.rst:46 msgid "Badges are displayed on the eLearning portion of a given user's portal, and are a way to set milestones and reward participants for passing surveys or gaining points. Besides the awardee, website visitors who access the :guilabel:`Courses` page will also be able to see the granted badges." msgstr "" -#: ../../content/applications/marketing/surveys/overview/scoring.rst:None +#: ../../content/applications/marketing/surveys/scoring.rst:-1 msgid "Example of how a badge looks on the eLearning portion of the website." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:3 +#: ../../content/applications/marketing/surveys/time_random.rst:3 msgid "Timed and randomized questions" msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:5 +#: ../../content/applications/marketing/surveys/time_random.rst:5 msgid "When creating a survey in Odoo, there are options to set a time limit on the survey and randomize the questions." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:9 +#: ../../content/applications/marketing/surveys/time_random.rst:9 msgid "Time limit" msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:11 +#: ../../content/applications/marketing/surveys/time_random.rst:11 msgid "During a timed survey, participants must finish the survey within a specified period of time. A common use case for implementing a time limit is that it greatly reduces the chance of participants looking up responses via external resources (e.g. web search), and reduces the survey to a \"closed book\" testing environment." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:16 +#: ../../content/applications/marketing/surveys/time_random.rst:16 msgid "Find the :guilabel:`Survey Time Limit` setting in the :guilabel:`Options` tab of the survey form, under the :guilabel:`Questions` section." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:None +#: ../../content/applications/marketing/surveys/time_random.rst:-1 msgid "Time limit field in the options tab of a survey template form." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:23 +#: ../../content/applications/marketing/surveys/time_random.rst:23 msgid "When the :guilabel:`Survey Time Limit` option is checked, a timer will be displayed on every page of the survey, letting participants keep track of the time remaining while the survey is active." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:27 +#: ../../content/applications/marketing/surveys/time_random.rst:27 msgid "Participants that do not submit their survey by the preconfigured time limit will *not* have their answers saved." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:31 +#: ../../content/applications/marketing/surveys/time_random.rst:31 msgid "Randomized selection" msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:33 +#: ../../content/applications/marketing/surveys/time_random.rst:33 msgid "When a survey is randomized, Odoo shuffles the questions and reveals them in a random order every time a participant begins the questionnaire. Using randomization as a survey method discourages participants from looking at each other's responses, and helps control for individual testing." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:37 +#: ../../content/applications/marketing/surveys/time_random.rst:37 msgid "To randomize a survey, click the :guilabel:`Options` tab on the survey form. In the :guilabel:`Questions` section, select :guilabel:`Randomized per section` for the :guilabel:`Selection` field. After enabling, navigate to the :guilabel:`Questions` tab and look in the :guilabel:`Random questions count` column. From there, determine how many questions (per section) Odoo should select and display during the shuffling of questions." msgstr "" -#: ../../content/applications/marketing/surveys/overview/time_random.rst:None +#: ../../content/applications/marketing/surveys/time_random.rst:-1 msgid "Randomized question count in the questions tab of a survey." msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 431432de1..04f320310 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,6 +20,378 @@ msgstr "" msgid "Productivity" msgstr "" +#: ../../content/applications/productivity/calendar.rst:5 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:3 +msgid "Synchronize Google calendar with Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:5 +msgid "Synchronize Google Calendar with Odoo to see and manage meetings from both platforms (updates go in both directions). This integration helps organize schedules, so a meeting is never missed." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:9 +msgid ":doc:`/applications/general/auth/google`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:10 +msgid ":doc:`/administration/maintain/google_oauth`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:13 +msgid "Setup in Google" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:16 +msgid "Select (or create) a project" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:18 +msgid "Create a new Google API project and enable the Google Calendar API. First, go to the `Google API Console `_ and log into the Google account." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:22 +msgid "If this is the first time visiting this page, Google will prompt the user to enter a country and agree to the Terms of Service. Select a country from the drop-down list and agree to the :abbr:`ToS (Terms of Service)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:26 +msgid "Next, click :guilabel:`Select a project` and select (or create) an API project to configure OAuth in, and store credentials. Click :guilabel:`New Project`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "Create a new API project to store credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:34 +msgid "Give the API Project a clear name, like \"Odoo Sync\", so it can be easily identified." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:37 +msgid "Enable Google calendar API" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:39 +msgid "Now, click on :guilabel:`Enabled APIs and Services` in the left menu. Select :guilabel:`Enabled APIs and Services` again if the :guilabel:`Search bar` doesn't appear." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "Enable APIs and Services on the API Project." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:46 +msgid "After that, search for `Google Calendar API` using the search bar and select :guilabel:`Google Calendar API` from the search results. Click :guilabel:`Enable`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "Enable the Google Calendar API." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:54 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:56 +msgid "Now that the API project has been created, OAuth should be configured. To do that, click on :guilabel:`OAuth consent` in the left menu and then select the :guilabel:`User Type`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:60 +msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:64 +msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:67 +msgid "In the second step, :guilabel:`OAuth Consent Screen`, type `Odoo` in the :guilabel:`App name` field, select the email address for the :guilabel:`User support email` field, and type the email address for the :guilabel:`Developer contact information` section. Then, click :guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:72 +msgid "Skip the third step, :menuselection:`Scopes`, by clicking :guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:74 +msgid "Next, if continuing in testing mode (External), add the email addresses being configured under the :guilabel:`Test users` step, by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:78 +msgid "Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:80 +msgid "Now, the OAuth consent has been configured, and it's time to create credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:83 +msgid "Create credentials" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:85 +msgid "The *Client ID* and the *Client Secret* are both needed to connect Google Calendar to Odoo. This is the last step in the Google console. Begin by clicking :guilabel:`Credentials` in the left menu. Then, click :guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`, Google will open a guide to create credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:90 +msgid "Under :menuselection:`Create OAuth Client ID`, select :guilabel:`Website application` for the :guilabel:`Application Type` field, and type `My Odoo Database` for the :guilabel:`Name`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:93 +msgid "Under the :guilabel:`Authorized JavaScript Origins` section, click :guilabel:`+ Add URI` and type the company's Odoo full :abbr:`URL (Uniform Resource Locator)` address." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:95 +msgid "Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ Add URI` and type the company's Odoo :abbr:`URL (Uniform Resource Locator)` address followed by `/google_account/authentication`. Finally, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "Add the authorized JavaScript origins and the authorized redirect URIs." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:103 +msgid "A :guilabel:`Client ID` and :guilabel:`Client Secret` will appear, copy these to a notepad." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:106 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:108 +msgid "Once the *Client ID* and the *Client Secret* are located, open the Odoo database and go to :menuselection:`Settings --> General Settings --> Integrations --> Google Calendar`. Check the box next to :guilabel:`Google Calendar`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "The Google Calendar checkbox in General Settings." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:116 +msgid "Next, copy and paste the *Client ID* and the *Client Secret* from the Google Calendar API credentials page into their respective fields below the :guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:121 +msgid "Sync calendar in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:123 +msgid "Finally, open the :menuselection:`Calendar` app in Odoo and click on the :guilabel:`Google` sync button to sync Google Calendar with Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "Click the Google sync button in Odoo Calendar to sync Google Calendar with Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:131 +msgid "When syncing Google Calendar with Odoo for the first time, the page will redirect to the Google Account. From there, select the :guilabel:`Email Account` that should have access, then select :guilabel:`Continue` (should the app be unverifed), and finally select :guilabel:`Continue` (to give permission for the transfer of data)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "Give Odoo permission to access Google Calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:140 +msgid "Now, Odoo Calendar is successfully synced with Google Calendar!" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:143 +msgid "Odoo highly recommends testing the Google calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Google Calendar with the user's production database." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:147 +msgid "Once a user synchronizes their Google calendar with the Odoo calendar:" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:149 +msgid "Creating an event in Odoo causes Google to send an invitation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:150 +msgid "Deleting an event in Odoo causes Google to send a cancellation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:151 +msgid "Adding a contact to an event causes Google to send an invitation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:152 +msgid "Removing a contact from an event causes Google to send a cancellation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:154 +msgid "Events can be created in Google Calendar without sending a notification by selecting :guilabel:`Don't Send` when prompted to send invitation emails." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:3 +msgid "Outlook Calendar synchronization" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:5 +msgid "Synchronizing a user's Outlook Calendar with Odoo is useful for keeping track of their tasks and appointments across all related applications." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:9 +msgid ":doc:`/applications/general/auth/azure`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:10 +msgid ":doc:`/administration/maintain/azure_oauth`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:13 +msgid "Register the application with Microsoft Azure" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:15 +msgid "To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account is needed. Creating an account is free for users who have never tried or paid for Azure. For more information, `click here `_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:19 +msgid "Refer to `Microsoft's documentation `_ on how to set up an Azure AD Tenant (also called an *environment*), which is a representation of an organization to manage and register apps." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:23 +msgid "Then, `Register an Application `_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:29 +msgid "When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and copy the Odoo database URI (URL) followed by `/microsoft_account/authentication`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:33 +msgid "Enter `https://www.companyname.odoo.com/microsoft_account/authentication` for the :guilabel:`Redirect URI`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "The \"Supported account type\" and \"Redirect URI\" settings in the Microsoft Azure AD portal." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:40 +msgid "For more information on the restrictions and limitations of URIs, `check this page `_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:43 +msgid "Regarding the application credentials, the user *must* add a client secret, which allows Odoo to authenticate itself, requiring no interaction from the user's side. :guilabel:`Certificates` are optional." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:47 +msgid "To do add a client secret, click :guilabel:`Add a certificate or secret` and then click :guilabel:`New client secret`. Next, type a :guilabel:`Description` and select when the client secret :guilabel:`Expires`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:51 +msgid "Since resetting the synchronization can be tricky, Odoo recommends setting the maximum allowed expiration date for the client secret (24 months), so there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to generate the client secret (:guilabel:`Secret ID`)." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:56 +msgid "Configuration in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:58 +msgid "In the Odoo database, go to :menuselection:`Settings --> General Settings --> Integrations` and activate the :guilabel:`Outlook Calendar` setting." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "The \"Outlook Calendar\" setting activated in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:65 +msgid "From the Microsoft Azure portal, under the :guilabel:`Overview` section of the application, copy the :guilabel:`Application (Client) ID`, and paste it into the :guilabel:`Client ID` field in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "The \"Client ID\" in the Microsoft Azure portal." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:72 +msgid "In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` section, copy the :guilabel:`Client Secret Value` and paste it into the :guilabel:`Client Secret` field in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:79 +msgid "Finally, on the Odoo :menuselection:`Settings --> General Settings` page, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:84 +msgid "Sync with Outlook" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:88 +msgid "Odoo highly recommends testing the Outlook calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Outlook Calendar with the user's production database." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:92 +msgid "If the user has any past, present, or future events on their Odoo calendar before syncing their Outlook calendar, Outlook will treat the events pulled from Odoo's calendar during the sync as new events, causing an email notification to be sent from Outlook to all the event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:96 +msgid "To avoid unwanted emails being sent to all past, present, and future event attendees, the user must add the events from the Odoo calendar to the Outlook calendar before the first ever sync, delete the events from Odoo, and then start the sync." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:100 +msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Outlook will still send a notification to all event participants every time an event is edited (created, deleted, unarchived, or event date/time changed), with no exceptions. This is a limitation that cannot be fixed from Odoo's side." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:105 +msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:112 +msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:114 +msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:115 +msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:116 +msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:117 +msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:118 +msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:119 +msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:122 +msgid "Sync Odoo Calendar and Outlook" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:124 +msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "The \"Outlook\" sync button in Odoo Calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:132 +msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:136 +msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook `. The configuration of Microsoft's Azure account is only done once, as Azure AD tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:143 +msgid ":doc:`../../sales/crm/optimize/outlook_extension`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:144 +msgid ":doc:`google`" +msgstr "" + #: ../../content/applications/productivity/discuss.rst:8 msgid "Discuss" msgstr "" @@ -44,7 +416,7 @@ msgstr "" msgid "Access your *Preferences* and choose how you would like your notifications to be handled." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 msgid "View of the preferences page for Odoo Discuss" msgstr "" @@ -56,7 +428,7 @@ msgstr "" msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 msgid "View of an inbox message and its action options in Odoo Discuss" msgstr "" @@ -64,7 +436,7 @@ msgstr "" msgid "The messages tagged as *Mark as Todo* are also shown in *Starred*, while the ones *Marked as Read* are moved to *History*." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 msgid "View of messages marked as todo in Odoo Discuss" msgstr "" @@ -76,7 +448,7 @@ msgstr "" msgid "The first time you log in to your account, OdooBot sends you a message asking for permission to receive desktop notifications to chats. If accepted, you receive push notifications to the messages sent to you despite of where you are in Odoo." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 msgid "View of the messages under the messaging menu emphasizing the request for push\n" "notifications for Odoo Discuss" msgstr "" @@ -89,7 +461,7 @@ msgstr "" msgid "To start a chat, click on *New Message* on the *Messaging Menu*, or go to *Discuss* and send a *Direct Message*." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 msgid "View of discuss’s panel emphasizing the titles channels and direct messages in Odoo Discuss" msgstr "" @@ -109,7 +481,7 @@ msgstr "" msgid "A notification is sent to the user mentioned either to his *Inbox* or through email, depending on his settings." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 msgid "View of a couple of chat window messages for Odoo Discuss" msgstr "" @@ -141,7 +513,7 @@ msgstr "" msgid "Airplane = out of the office" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 msgid "View of the contacts’ status for Odoo Discuss" msgstr "" @@ -170,7 +542,7 @@ msgstr "" msgid "Access and manage your activities wherever you are in Odoo by the *Activities* menu." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:None +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 msgid "View of crm leads page emphasizing the activities menu for Odoo Discuss" msgstr "" @@ -182,7 +554,7 @@ msgstr "" msgid "Activities can be planned and managed from the chatter by clicking on *Schedule activity*, or through Kanban views." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:None +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 msgid "View of crm leads and the option to schedule an activity for Odoo Discuss" msgstr "" @@ -194,7 +566,7 @@ msgstr "" msgid "A number of activities types are available by default in Odoo (call, email, meeting, etc.). However, you can set new ones going to :menuselection:`Settings --> Activity types`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:None +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 msgid "View of the settings page emphasizing the menu activity types for Odoo Discuss" msgstr "" @@ -210,7 +582,7 @@ msgstr "" msgid "Odoo helps you to plan a flow of activities by allowing you to set *Recommended Next Activities*." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:None +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 msgid "View of an activity type form emphasizing the field recommended next activities for Odoo\n" "Discuss" msgstr "" @@ -219,7 +591,7 @@ msgstr "" msgid "Once the respective activity is completed, select *Done & Schedule Next* and next steps are suggested to you." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:None +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 msgid "View of an activity being schedule emphasizing the recommended activities field being\n" "shown for Odoo Discuss" msgstr "" @@ -245,7 +617,7 @@ msgstr "" msgid "A *Public* channel can be seen by everyone, while a *Private* one is only visible to users invited to it." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of discuss’s sidebar and a channel being created in Odo Discuss" msgstr "" @@ -261,7 +633,7 @@ msgstr "" msgid "You can configure a channel’s name, description, email alias, and privacy by clicking on the *Channel Settings* icon on the sidebar." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of a channel’s settings form in Odoo Discuss" msgstr "" @@ -277,7 +649,7 @@ msgstr "" msgid "If you choose *Invited people only*, go to the *Members* tab to add your members, or, go to Discuss’ main page, select the channel and click on *Invite*." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of Discuss’ sidebar emphasizing the option to invite members in Odoo Discuss" msgstr "" @@ -297,7 +669,7 @@ msgstr "" msgid "Enabling this option allows you to *Moderate this channel*, meaning that messages will need to be approved before being sent." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of a message with a pending moderation status in Odoo Discuss" msgstr "" @@ -309,7 +681,7 @@ msgstr "" msgid "Mark *Send guidelines to new subscribers* to automatically send instructions to newcomers." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of a channel’s settings form emphasizing the tab moderation in Odoo Discuss" msgstr "" @@ -317,7 +689,7 @@ msgstr "" msgid "Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* messages." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of a message to be moderated in Odoo Discuss" msgstr "" @@ -329,7 +701,7 @@ msgstr "" msgid "Once a channel is moderated, the menu *Ban List* allows you to add email addresses per moderated channel to auto-ban them from sending messages." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of a channel’s setting form emphasizing the ban Lists menu in Odoo Discuss" msgstr "" @@ -341,7 +713,7 @@ msgstr "" msgid "Once at least 20 channels, direct message and live chat conversations (if the module is installed on your database) are pinned in the sidebar, a *Quick search…* bar is displayed. It is a clever way to filter conversations and quickly find the one you need." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of the Discuss’ sidebar emphasizing the quick search bar in Odoo Discuss" msgstr "" @@ -357,7 +729,7 @@ msgstr "" msgid "Apply filters criteria and save it for later use. The search function accepts wildcards by using the underscore character *(_)* to represent a single character." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 msgid "View of a channel being searched through filters in Odoo Discuss" msgstr "" @@ -374,191 +746,675 @@ msgid "Configuration" msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:3 -msgid "Connect an IoT Box to your database" +msgid "Connect an IoT box to Odoo" msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:5 -msgid "Install the Internet of Things (IoT) App on your Odoo Database." +msgid "An Internet of Things (IoT) box is a micro-computer device that allows for the connection of input and output devices to an Odoo database. An :abbr:`IoT (Internet of Things)` box subscription is required in order to use the :abbr:`IoT (Internet of Things)` box with a secured connection. A computer is also required to set up the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:10 -msgid "Go in the IoT App and click on Connect on the IoT Boxes page." +#: ../../content/applications/productivity/iot/config/connect.rst:11 +msgid "`IoT Box FAQ `_" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:15 -msgid "Follow the steps to connect your IoT Box." +#: ../../content/applications/productivity/iot/config/connect.rst:13 +msgid "Begin the :abbr:`IoT (Internet of Things)` configuration process by :ref:`installing the IoT app ` on the Odoo database through the :menuselection:`Apps` application." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:21 -msgid "Ethernet Connection" +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "The Internet of Things (IoT) app on the Odoo database." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:23 -msgid "Connect to the IoT Box all the devices that have to be connected with cables (ethernet, usb devices, etc.)." +#: ../../content/applications/productivity/iot/config/connect.rst:20 +msgid "Next, after the *IoT app* is installed, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the :menuselection:`IoT Boxes` dashboard." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:26 -msgid "Power on the IoT Box." +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "Connecting an IoT box to the Odoo database." msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:28 -msgid "Read the Pairing Code from a screen or a receipt printer connected to the IoT Box." +msgid "There are two recommended ways to connect the :abbr:`IoT (Internet of Things)` box to the database once the *IoT app* is installed. Follow the steps in either of the next two sections to connect the :abbr:`IoT (Internet of Things)` box via :ref:`wired ethernet connection ` or via :ref:`WiFi `." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:32 -msgid "Input the Pairing Code and click on the Pair button." +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "Connection steps for a wired connection or WiFi connection." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:35 -msgid "Recent changes in modern web browsers forced us to modify the connection wizard. If your screen is different from the screenshots, make sure that the ``iot_pairing`` module is installed." +#: ../../content/applications/productivity/iot/config/connect.rst:38 +msgid "The disk image that the :abbr:`IoT (Internet of Things)` box SD card is formatted with is unique to the version of the Odoo database that the :abbr:`IoT (Internet of Things)` box is running on. Ensure that the :abbr:`IoT (Internet of Things)` box is :doc:`flashed ` with the most up-to-date disk image." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:40 -msgid "WiFi Connection" -msgstr "" - -#: ../../content/applications/productivity/iot/config/connect.rst:42 -msgid "Power on the IoT Box" -msgstr "" - -#: ../../content/applications/productivity/iot/config/connect.rst:44 -msgid "Copy the token" +#: ../../content/applications/productivity/iot/config/connect.rst:46 +msgid "Ethernet connection" msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:48 -msgid "Connect to the IoT Box WiFi Network (make sure there is no ethernet cable plugged in your computer)." +msgid "The following is the process to connect the :abbr:`IoT (Internet of Things)` box via an ethernet cable to the Odoo database (by way of the ethernet port; RJ-45)." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:53 -msgid "You will be redirected to the IoT Box Homepage (if it doesn't work, connect to the IP address of the box). Give a name to your IoT Box (not required) and paste the token, then click on next." +#: ../../content/applications/productivity/iot/config/connect.rst:51 +msgid "First, connect all wired devices to the :abbr:`IoT (Internet of Things)` box (ethernet, :abbr:`USB (Universal Serial Bus)` devices, etc.). At minimum, an HDMI screen should be connected. Then, plug the :abbr:`IoT (Internet of Things)` box into a power source." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:60 -msgid "If you are on Runbot, do not forget to add the -all or -base in the token (e.g. this token **http://375228-saas-11-5-iot-f3f920.runbot16.odoo.com\\|4957098401** should become **http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)." +#: ../../content/applications/productivity/iot/config/connect.rst:55 +msgid "Immediately after the unit powers on and boots up, read the *pairing code* from the screen or from the printout of a receipt printer connected to the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:66 -msgid "Choose the WiFi network you want to connect with (enter the password if there is one) and click on Submit. Wait a few seconds before being redirected to your database." +#: ../../content/applications/productivity/iot/config/connect.rst:59 +msgid "By default, the :abbr:`IoT (Internet of Things)` box will display the *pairing code* for a maximum of 5 minutes after the unit boots up. After 5 minutes, the *pairing code* will disappear for security purposes and the :abbr:`IoT (Internet of Things)` box will need to be rebooted manually by unplugging the unit from the power source for ten seconds and re-plugging it back in." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:72 -msgid "You should now see the IoT Box." +#: ../../content/applications/productivity/iot/config/connect.rst:65 +msgid "If no screen is attached to the :abbr:`IoT (Internet of Things)` box, then the *pairing code* can be accessed from the :abbr:`IoT (Internet of Things)` box homepage by clicking on the :guilabel:`POS Display` button. For instructions on how to access the :abbr:`IoT (Internet of Things)` box homepage visit :ref:`iot_connect/token`." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:78 -msgid "IoT Box Schema" +#: ../../content/applications/productivity/iot/config/connect.rst:70 +msgid "On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Input the *pairing code* in the :guilabel:`Pairing Code` field and click on the :guilabel:`Pair` button. The database will now link to the :abbr:`IoT (Internet of Things)` box and it will appear on the :menuselection:`IoT Boxes` page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:79 +msgid "WiFi connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:81 +msgid "The following is the process to connect the :abbr:`IoT (Internet of Things)` box via a WiFi connection to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:84 +msgid "First, ensure there is no ethernet cable plugged into the :abbr:`IoT (Internet of Things)` box. Then, connect all wired devices to the :abbr:`IoT (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:88 +msgid "After connecting the devices, plug the :abbr:`IoT (Internet of Things)` box into to a power source. On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Then copy the :guilabel:`Token` from the :guilabel:`WiFi connection` section as this will later be used to link the Odoo database to the :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:94 +msgid "Back on the computer, navigate to the available WiFi networks and connect to the :abbr:`IoT (Internet of Things)` box WiFi network. The WiFi network dispersed by the :abbr:`IoT (Internet of Things)` box will start with `IoTBox-xxxxxxxxxx`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "WiFi networks available on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:102 +msgid "Upon connecting to the :abbr:`IoT (Internet of Things)` box WiFi, a browser will automatically redirect to the :menuselection:`Configure Iot Box` wizard. Name the :abbr:`IoT (Internet of Things)` box, then paste the previously copied *token* into the :guilabel:`Server Token` field, and then click on :guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "Enter the server token into the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:112 +msgid "If the :abbr:`IoT (Internet of Things)` box WiFi connection wizard doesn't start, then see the documentation on :ref:`connecting with a token `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:115 +msgid "Now, choose the WiFi network that the :abbr:`IoT (Internet of Things)` box will connect with (enter the password if there is one) and click on :guilabel:`Connect`. Wait a few seconds and the browser will redirect to the :abbr:`IoT (Internet of Things)` box homepage. The computer may need to be manually re-connected back to the original WiFi connection, if this does not happen automatically." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "Configuring the WiFi for the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:124 +msgid "After completing each step, the :abbr:`IoT (Internet of Things)` box should appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "The IoT box has been successfully configured on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:132 +msgid "The :abbr:`IoT (Internet of Things)` box may need to be manually rebooted upon successfully connecting via WiFi for the box to appear in the *IoT app* on the Odoo database. To do so, simply unplug the device and plug it back into the power source after ten seconds." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:139 +msgid "Manually connecting the IoT box using the token" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:141 +msgid "A manual connection of the :abbr:`IoT (Internet of Things)` box to the :abbr:`IoT (Internet of Things)` app can be made using the *token*, from a computer. The *token* can be found by navigating to :menuselection:`IoT app --> IoT Boxes` and clicking on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:145 +msgid "Under the :guilabel:`WiFi Connection` section of the :guilabel:`Connect an IoT Box` page that appears, click :guilabel:`Copy` to the right of the :guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:149 +msgid "Access the :abbr:`IoT (Internet of Things)` box homepage by entering the :abbr:`IP (Internet Protocol)` address of the :abbr:`IoT (Internet of Things)` box into a browser window from a computer on the same network as the :abbr:`IoT (Internet of Things)` box (preferably by ethernet connection)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:154 +msgid "The :abbr:`IP (Internet Protocol)` address can be accessed by the router admin console that the :abbr:`IoT (Internet of Things)` box is connected to, or by connecting a receipt printer to the :abbr:`IoT (Internet of Things)` box. A receipt will print out with the :abbr:`IoT (Internet of Things)` box's :abbr:`IP (Internet Protocol)` address on it." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:159 +msgid "On the :abbr:`IoT (Internet of Things)` box homepage, enter the *token* under the :guilabel:`Server` section by clicking on :guilabel:`Configure`. Then, paste the *token* into the :guilabel:`Server Token` field and click :guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:167 +msgid "IoT box schema" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:170 +msgid "Raspberry Pi 4" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:174 +msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:177 +msgid "Raspberry Pi 3" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:181 +msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:3 -msgid "Flashing your SD Card" +msgid "Flashing the SD card" msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:5 -msgid "In some case, you may need to reflash your IoT Box’s SD Card to benefit from our latest updates." +msgid "In some circumstances, the :abbr:`IoT (Internet of Things)` box's micro SD Card may need to be re-flashed to benefit from Odoo's latest :abbr:`IoT (Internet of Things)` image update. This means that the Odoo :abbr:`IoT (Internet of Things)` box software may need to be updated." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:9 -msgid "Upgrade from the IoT Box homepage" +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:10 +msgid "Upgrade from the IoT box home page" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:11 -msgid "Go to the IoT Box homepage, click on *Update*, next to the version number. If a new version of the IoT Box image is available, you will see a *Upgrade to ___* button a the bottom of the page, the IoT Box will then flash itself to the new version of the IoT Box. All of your configurations will be saved." +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:12 +msgid "Go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to :menuselection:`IoT app --> IoT Boxes` and clicking on the :guilabel:`IP address` of the :abbr:`IoT (Internet of Things)` box. Then click on :guilabel:`Update` (next to the version number)." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:18 -msgid "This process can take more than 30 minutes. Do not turn off or unplug the IoT Box as it would leave it in an inconsistent state." +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:16 +msgid "If a new version of the :abbr:`IoT (Internet of Things)` Box image is available, an :guilabel:`Upgrade to _xx.xx_` button will appear at the bottom of the page. Click this button to upgrade the unit and the :abbr:`IoT (Internet of Things)` box will then flash itself to the new version. All of the previous configurations will be saved." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:25 -msgid "Upgrade with Etcher" +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:22 +msgid "This process can take more than 30 minutes. Do not turn off or unplug the :abbr:`IoT (Internet of Things)` box as it would leave it in an inconsistent state. This means that the :abbr:`IoT (Internet of Things)` box will need to be re-flashed with a new image. See :ref:`flash_sdcard/etcher`." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:27 -msgid "Go to Balena’s website and download `Etcher `__. It’s a free and open-source utility used for burning image files. Install and launch it. Download the latest image from `nightly `__." +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:-1 +msgid "IoT box software upgrade in the IoT Box Home Page." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:32 -msgid "Then, open *Etcher* and select *Flash from file*, find the image you just downloaded. Insert the IoT Box SD card into your computer and select it. Click on *Flash* and wait for the process to finish." +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:34 +msgid "Upgrade with Etcher Software" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:37 +msgid "A computer with a micro SD card reader/adapter is required in order to re-flash the micro SD card." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:40 +msgid "Navigate to Balena's website and download `Etcher `_. It's a free and open-source utility used for burning image files onto drives. Click to `download `_. Install and launch the program on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:44 +msgid "Then download the version-specific :abbr:`IoT (Internet of Things)` image from `nightly `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:47 +msgid "The following are image versions on the `nightly `_ website with their corresponding Odoo database version:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:50 +msgid "Odoo V16 --> iotbox-latest.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:51 +msgid "Odoo V15 --> iotboxv21_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:52 +msgid "Odoo V14 --> iotboxv21_04.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:53 +msgid "Odoo V13 --> iotboxv20_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:55 +msgid "The images should be downloaded and extracted to a convenient file location." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:57 +msgid "After this step is complete, insert the :abbr:`IoT (Internet of Things)` box's micro SD card into the computer or reader. Open *Etcher* and select :guilabel:`Flash from file`, then find and select the image just downloaded and extracted. Next, select the drive the image should be burned to. Lastly, click on :guilabel:`Flash` and wait for the process to finish." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:-1 +msgid "Balena's Etcher software dashboard." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:67 +msgid "An alternative software for flashing the micro SD card is *Raspberry Pi Imager*. Download the *Raspberry Pi* software `here `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:5 +msgid "HTTPS certificate (IoT)" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:8 +msgid "What is HTTPS?" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:10 +msgid "*Hypertext Transfer Protocol Secure* (HTTPS) is the secure version of *Hypertext Transfer Protocol* (HTTP), which is the primary protocol used to send data back and forth between a web browser and a website. :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` is encrypted in order to increase the security of data transfer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:15 +msgid ":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` uses an encryption protocol to encrypt communications. The protocol is called *Transport Layer Security* (TLS), although formerly it was known as *Secure Sockets Layer* (SSL)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:19 +msgid ":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` occurs based upon the transmission of :abbr:`TLS (Transport Layer Security)`/:abbr:`SSL (Secure Sockets Layer)` certificates, which verify that a particular provider is who they say they are." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:24 +msgid "In this documentation and throughout Odoo the term \"HTTPS certificate\" will be used to define the fact that the :abbr:`SSL (Secure Sockets Layer)` certificate is valid and allows a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:29 +msgid "Why is it needed?" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:31 +msgid "In order to communicate with certain network devices (in particular for payment terminals), the usage of :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` is mandatory. If the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate isn't valid, some devices won't be able to interact with the :abbr:`IoT (Internet of Things)` Box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:37 +msgid "How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:39 +msgid "The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate is automatic." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:41 +msgid "The :abbr:`IoT (Internet of Things)` Box will send a specific request to ``_ which will send back the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate if the :abbr:`IoT (Internet of Things)` box and database are eligible." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:48 +msgid "Internet of Things (IoT) eligibility" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:50 +msgid "The database should be a **production** instance. The database instance should not be a copy, a duplicate, a staging, or a development environment." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:52 +msgid "The Odoo subscription must:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:54 +msgid "Have an :guilabel:`IoT Box Subscription` line." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:55 +msgid ":guilabel:`Status` must be :guilabel:`In Progress`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:57 +msgid "If the subscription is linked to a ``_ portal user check the information on the portal subscription page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +msgid "Odoo.com portal subscriptions filtered by \"in progress\"." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:64 +msgid "In this case, both subscriptions are considered \"in progress\" as the :guilabel:`Filter By\\: In Progress` was used." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:68 +msgid "If the subscription is in question, contact the database's Account Manager or Partner regarding the matter." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:72 +msgid "Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate errors" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:74 +msgid "If anything goes wrong during the process of the \"HTTPS certificate\" generation or reception, a specific error will code be given on the :abbr:`IoT (Internet of Things)` box home page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:78 +msgid "Accessing the :abbr:`IoT (Internet of Things)` box homepage will check for the presence of the \"HTTPS certificate\" and will attempt its generation if it is missing. As such, if there is an error on the :abbr:`IoT (Internet of Things)` box home page, refresh the :abbr:`IoT (Internet of Things)` home page to see if the error disappears." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:84 +msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:88 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:101 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:132 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:150 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:167 +msgid "Reason:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:87 +msgid "The configuration regarding the server is missing. In other words, the Odoo instance is not connected with the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:114 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:138 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:160 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:171 +msgid "Solution:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 +msgid "Ensure that the server is configured." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:94 +msgid ":doc:`/applications/productivity/iot/config/connect`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:97 +msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:100 +msgid "An unhandled error happened when trying to read the existing :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 +msgid "Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate file is readable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:107 +msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 +msgid "The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is missing." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:113 +msgid "Ensure that both values are configured as intended. To modify them, go to the :abbr:`IoT (Internet of Things)` box home page, and navigate to :guilabel:`Credential`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:117 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:120 +msgid "An unexpected error happened when the :abbr:`IoT (Internet of Things)` box tried to reach ``_. The causes are likely due to the network infrastructure/configuration:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:124 +msgid "The :abbr:`IoT (Internet of Things)` box does not have access to internet." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:125 +msgid "The network does not allow the :abbr:`IoT (Internet of Things)` box to communicate with ``_. This may be due to network devices preventing the communication (firewalls, etc.) or the network configuration (:abbr:`VPN (Virtual Private Network)`, etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:131 +msgid "More information regarding the error that occurred can be found in the full request exception details, which are in the :abbr:`IoT (Internet of Things)` box logs." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:136 +msgid "Consult with your system or network administrator should this issue arise. This error code depends on the network infrastructure and goes beyond :doc:`Odoo support's service scope `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:141 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:144 +msgid "The IoT-box was able to reach ``_ but received an unusual `HTTP response (status codes) `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:148 +msgid "This error code will also give the HTTP response status codes. For example, if the error reads `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the page returned a 404 error, which is the \"Page Not Found\" code." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:153 +msgid "Check if ``_ is down using a web browser, as it's possible that it is down due to maintenance." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:156 +msgid "If ``_ is down due to maintenance, unfortunately there is nothing that can be done but instead wait for it to recover." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:158 +msgid "If ``_ is not down due to maintenance, open a `support ticket `_ on the matter. Ensure that the 3 digits status code next to the code error is included in the support ticket." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:163 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:166 +msgid "The :abbr:`IoT (Internet of Things)` box was able to reach ``_ but it refused to deliver the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:170 +msgid "Ensure that the :abbr:`IoT (Internet of Things)` box and database are eligible for a certificate: :ref:`Internet of Things (IoT) eligibility `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:174 +msgid "How to ensure that the HTTPS certificate is correct" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:176 +msgid "If the certificate has been applied successfully, a new :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` :abbr:`URL (Uniform Resource Locator)` for the :abbr:`IoT (Internet of Things)` box ending with `.odoo-iot.com` will appear on the Odoo database, inside of the :menuselection:`IoT` application on that specific device's form." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:-1 +msgid "Odoo IoT app IoT box with .odoo-iot.com domain." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:185 +msgid "When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a secured :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection will be established." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:192 +msgid "Example of valid SSL certificate details on the browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:192 +msgid "Padlock in Chrome on Windows 10 attesting the fact that the connection is secured in :abbr:`HTTPS (Hypertext Transfer Protocol Secure)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:195 +msgid "The IoT-box homepage will now display an `OK` status next to `HTTPS certificate`. The drop-down menu icon, when clicked, will reveal information regarding the certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:-1 +msgid "IoT box homepage with HTTPS certificate OK status." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:203 +msgid "Domain Name System (DNS) issue" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:205 +msgid "If the :abbr:`IoT (Internet of Things)` box can be accessed from its :abbr:`IP (Intrernet Protocol)` address but not the Odoo assigned domain: `.odoo-iot.com`; then the :abbr:`IoT (Internet of Things)` box is likely running into a :abbr:`DNS (Domain Name System)` issue. On some browsers, it will give an error code mentioning :abbr:`DNS (Domain Name System)` (like `DNS_PROBE_FINISHED_NXDOMAIN`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:210 +msgid "These :abbr:`DNS (Domain Name System)` issues may appear as the following in different browsers:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:214 +msgid "Chrome" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:220 +msgid "DNS issue on Chrome browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:223 +msgid "Firefox" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:229 +msgid "DNS issue on Firefox browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:231 +msgid "Edge" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:237 +msgid "DNS issue on Edge browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:241 +msgid "Domain Name System (DNS) issue solution" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:243 +msgid "Should the router allow the :abbr:`DNS (Domain Name System)` to be manually changed, change the DNS to use `Google DNS `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:245 +msgid "If your router doesn't allow for this, then a change will need to be made on the :abbr:`DNS (Domain Name System)` settings of each of the devices using `Google DNS `_. This will need to occur on **every** device that plans to interact with the :abbr:`IoT (Internet of Things)` box (e.g. computer, tablet or phone). The individual device configuration processes can be found on the website of the device's manufacturer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:253 +msgid "Other :abbr:`IoT (Internet of Things)` devices such as payment terminals likely won't need their :abbr:`DNS (Domain Name System)` settings changed as they are already configured with custom :abbr:`DNS (Domain Name System)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:258 +msgid "Consult with your system or network administrator should this issue arise. This error code depends on the network infrastructure, and it goes beyond :doc:`Odoo support's service scope `." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:3 -msgid "Use the IoT Box for the PoS" +msgid "Use an IoT box with a PoS" msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:9 +#: ../../content/applications/productivity/iot/config/pos.rst:6 msgid "Prerequisites" msgstr "" +#: ../../content/applications/productivity/iot/config/pos.rst:8 +msgid "Before starting, make sure the following equipment is available:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:10 +msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." +msgstr "" + #: ../../content/applications/productivity/iot/config/pos.rst:11 -msgid "Before starting, make sure you have the following:" +msgid "A computer or tablet with an up-to-date web browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:12 +msgid "Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* applications installed." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:13 -msgid "An IoT Box, with its power adapter." +msgid "A local network set up with :abbr:`DHCP (Dynamic Host Configuration Protocol)` (this is the default setting)." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:15 -msgid "A computer or tablet with an up-to-date web browser" +msgid "An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already built in)." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:17 -msgid "A running Odoo Online or Odoo instance with the Point of Sale and IoT apps installed" +#: ../../content/applications/productivity/iot/config/pos.rst:16 +msgid "Any of the supported hardware (receipt printer, barcode scanner, cash drawer, payment terminal, scale, customer display, etc.). The list of supported hardware can be found on the `POS Hardware page `_." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:20 -msgid "A local network setup with DHCP (this is the default setting)" +#: ../../content/applications/productivity/iot/config/pos.rst:21 +msgid "Setup" msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:22 -msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)" +#: ../../content/applications/productivity/iot/config/pos.rst:25 +msgid "A suggested configuration for a point of sale system." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:24 -msgid "Any of the supported hardware (receipt printer, barcode scanner, cash drawer, payment terminal, scale, customer display, etc.). The list of supported hardware can be found on the `POS Hardware page `__" +#: ../../content/applications/productivity/iot/config/pos.rst:27 +msgid "To connect hardware to the :abbr:`PoS (Point of Sale)`, the first step is to connect an :abbr:`IoT (Internet of Things)` box to the database. To do this, follow these instructions: :doc:`Connect an Internet of Things (IoT) box to the Odoo database `." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:30 -msgid "Set Up" +#: ../../content/applications/productivity/iot/config/pos.rst:31 +msgid "Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:32 -msgid "To connect hardware to the PoS, the first step is to connect an IoT Box to your database. For this, follow this :doc:`documentation `." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:36 -msgid "Then, you have to connect the peripheral devices to your IoT Box." +#: ../../content/applications/productivity/iot/config/pos.rst:37 +msgid "Device Name" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:38 -msgid "**Printer**: Connect a supported receipt printer to a USB port or to the network and power it on." +msgid "Instructions" msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:41 -msgid "**Cash drawer**: The cash drawer should be connected to the printer with an RJ25 cable." +#: ../../content/applications/productivity/iot/config/pos.rst:39 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 +msgid "Printer" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:40 +msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` port or to the network, and power it on. Refer to :doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:43 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149 +msgid "Cash drawer" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:44 -msgid "**Barcode scanner**: Connect your barcode scanner. In order for your barcode scanner to be compatible it must end barcodes with an Enter character (keycode 28). This is most likely the default configuration of your barcode scanner." +msgid "The cash drawer should be connected to the printer with an RJ25 cable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:45 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:117 +msgid "Barcode scanner" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:46 +msgid "In order for the barcode scanner to be compatible it must end barcodes with an `ENTER` character (keycode 28). This is most likely the default configuration of the barcode scanner." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:48 +msgid "Scale" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:49 -msgid "**Scale**: Connect your scale and power it on." +msgid "Connect the scale and power it on. Refer to :doc:`/applications/productivity/iot/devices/scale`." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:51 -msgid "**Customer Display**: Connect a screen to the IoT Box to display the PoS order. Please refer to :doc:`/applications/productivity/iot/devices/screen`." +msgid "Customer display" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:52 +msgid "Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the :abbr:`PoS (Point of Sale)` order. Refer to :doc:`/applications/productivity/iot/devices/screen`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:54 +msgid "Payment terminal" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:55 -msgid "**Payment terminal**: The connection process depends on the terminal, please refer to the :doc:`payment terminals documentation `." +msgid "The connection process depends on the terminal. Refer to the :doc:`payment terminals documentation `." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:59 -msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in :menuselection:`Point of Sale --> Configuration --> PoS`, tick *IoT Box* and select the devices you want to use in this Point of Sale. Save the changes." +#: ../../content/applications/productivity/iot/config/pos.rst:58 +msgid "Once this is completed, connect the :abbr:`IoT (Internet of Things)` box to the :menuselection:`PoS` application. To do this, go to :menuselection:`Point of Sale --> Configuration --> PoS`, tick the :guilabel:`IoT Box` option, and select the devices to be used in this :abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:-1 +msgid "Configuring the connected devices in the POS application." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:67 -msgid "Set up is done, you can launch a new PoS Session." +msgid "Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be launched." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 @@ -566,15 +1422,15 @@ msgid "Troubleshooting" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 -msgid "IoT Box Connection" +msgid "IoT box connection" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 -msgid "I can't find the pairing code to connect my IoT Box" +msgid "Unable to locate the pairing code to connect the IoT box" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:11 -msgid "The pairing code should be printed on receipt printers connected to the IoT Box and should also be displayed on connected monitors." +msgid "The pairing code should be printed on receipt printers connected to the :abbr:`IoT (Internet of Things)` box and should also be displayed on connected monitors." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 @@ -582,123 +1438,147 @@ msgid "The pairing code doesn't show under the following circumstances:" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:16 -msgid "The IoT Box is already connected to an Odoo database;" +msgid "The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:17 +msgid "The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:18 -msgid "The IoT Box is not connected to the Internet;" +msgid "The code is only valid for 5 minutes after the :abbr:`IoT (Internet of Things)` box has started. It's automatically removed from connected displays when this time has expired." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:20 -msgid "The code is only valid for 5 minutes after the IoT Box has started. It's automatically removed from connected displays when this delay has expired;" +msgid "The version of the :abbr:`IoT (Internet of Things)` box image is too old. If the :abbr:`IoT (Internet of Things)` box image is from an earlier version, then the SD card of the :abbr:`IoT (Internet of Things)` box will need to be re-flashed to update the image (see :doc:`Flashing the SD Card `)." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:23 -msgid "The version of the IoT Box image is too old. It should use version 20.06 or more recent. If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (see :doc:`Flashing your SD Card `)" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:25 +msgid "If none of the cases listed above correct the issue, then make sure that the :abbr:`IoT (Internet of Things)` box has correctly started, by checking that a fixed green LED is showing next to the power port." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:28 -msgid "If you are not in any of the cases listed above, make sure that the IoT Box has correctly started, by checking that a fixed green LED is showing next to the micro-USB port." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:30 +msgid "IoT box is connected but it's not showing in the database" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:33 -msgid "I've connected my IoT Box but it's not showing in my database" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:32 +msgid "When an :abbr:`IoT (Internet of Things)` box connects to a database, it may restart. If so, it can take up to five minutes before appearing in the database. If the :abbr:`IoT (Internet of Things)` box is still not showing after five minutes, make sure that the :abbr:`IoT (Internet of Things)` box can reach the database and that the server doesn't use a multi-database environment." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:35 -msgid "When you connect an IoT Box to a database, the IoT Box might restart, if that is the case, it might take up to one minute before appearing in your database. If after some time the IoT is still not showing, make sure that your database can be reached from the IoT Box and that your server doesn't use a multi-database environment." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:37 +msgid "To access the database from the :abbr:`IoT (Internet of Things)` box, open a browser and type in the database address." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:42 -msgid "My IoT Box is connected to my database, but cannot be reached" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:41 +msgid "The IoT box is connected to the Odoo database, but cannot be reached" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:44 -msgid "Make sure that the IoT Box and the device running the browser are located on the same network as the IoT Box cannot be reached from outside the local network." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:43 +msgid "Make sure that the :abbr:`IoT (Internet of Things)` box and the computer running the browser are located on the same network, as the :abbr:`IoT (Internet of Things)` box cannot be reached from outside the local network." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:49 -msgid "Printer" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:48 +msgid "The HTTPS certificate doesn't generate" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:52 -msgid "My printer is not detected" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:50 +msgid "In order to generate a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate, an IoT box subscription is required for the :abbr:`IoT (Internet of Things)` box. Connecting the :abbr:`IoT (Internet of Things)` box prior to configuring an :abbr:`IoT (Internet of Things)` subscription for the database and :abbr:`IoT (Internet of Things)` box with the Account Manager will result in an unsecured connection." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:54 -msgid "If one of your printers doesn't show up in your devices list, go to the IoT Box homepage and make sure that it is listed under *Printers*." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:56 +msgid "In addition, a firewall can also prevent the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate from generating correctly. In this case, deactivate the firewall until the certificate is successfully generated. It should also be noted that certain devices, such as a router that has a built-in firewall, can prevent the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate from generating." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:60 -msgid "If your printer is not present on the IoT Box homepage, hit *Printers Server*, go to the *Administration* tab and click on *Add Printer*. If you can't find your printer in the list, it's probably not connected properly." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:63 +msgid ":doc:`HTTPS certificate (IoT) `" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 -msgid "My printer outputs random text" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:69 +msgid "The printer is not detected" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:68 -msgid "For most printers, the correct driver should be automatically detected and selected. However, in some cases, the automatic detection mechanism might not be enough, and if no driver is found the printer might print random characters." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:71 +msgid "If a printer doesn't show up in the devices list, go to the :abbr:`IoT (Internet of Things)` box homepage and make sure that it is listed under :guilabel:`Printers`." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:73 -msgid "The solution is to manually select the corresponding driver. On the IoT Box homepage, click on *Printers Server*, go to the *Printers* tab and select the printer in the list. In the Administration dropdown, click on *Modify Printer*. Follow the steps and select the Make and Model corresponding to your printer." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 +msgid "The IoT box Home Page landing page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:78 +msgid "If the printer is not present on the :abbr:`IoT (Internet of Things)` box homepage, click :guilabel:`Printers Server`, go to the :guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the printer is not present in the list, it's likely not connected properly." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:83 +msgid "The printer outputs random text" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:85 +msgid "For most printers, the correct driver should be automatically detected and selected. However, in some cases, the automatic detection mechanism might not be enough, and if no driver is found, the printer might print random characters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:89 +msgid "The solution is to manually select the corresponding driver. On the :abbr:`IoT (Internet of Things)` box homepage, click on :guilabel:`Printers Server`, go to the :guilabel:`Printers` tab and select the printer in the list. In the :guilabel:`Administration` dropdown, click on :guilabel:`Modify Printer`. Follow the steps and select the *make* and *model* corresponding to the printer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 +msgid "Edit the printer connected to the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:99 msgid "Epson and Star receipt printers and Zebra label printers do not need a driver to work. Make sure that no driver is selected for those printers." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:88 -msgid "My Zebra Printer doesn't print anything" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:103 +msgid "The Zebra printer doesn't print anything" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:90 -msgid "Zebra printers are quite sensitive to the format of the ZPL code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings ~~> Technical ~~> Views` in developer mode and look for the corresponding template." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:105 +msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (ZPL) code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings --> Technical --> User Interface --> Views` in :ref:`developer mode ` and look for the corresponding template." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:97 -msgid "Barcode Scanner" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:112 +msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here `_." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:100 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:120 msgid "The characters read by the barcode scanner don't match the barcode" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:102 -msgid "By default, we assume that your barcode scanner is configured in US QWERTY. This is the default configuration of most barcode readers. If your barcode scanner uses a different layout, please go to the form view of your device and select the correct one." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:122 +msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:108 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:127 msgid "Nothing happens when a barcode is scanned" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:110 -msgid "Make sure that the correct device is selected in your Point of Sale configuration and that your barcode is configured to send an ENTER character (keycode 28) at the end of every barcode." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:129 +msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:115 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:135 msgid "The barcode scanner is detected as a keyboard" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:117 -msgid "Some poorly built barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the IoT Box." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:138 +msgid "Some barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:121 -msgid "You can manually change the device type by going to its form view and activating the *Is scanner* option." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:141 +msgid "The device type can be manually changed by going to its form view (:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the :guilabel:`Is scanner` option." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:128 -msgid "Cashdrawer" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 +msgid "Modifying the form view of the barcode scanner." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:131 -msgid "The cashdrawer does not open" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 +msgid "The cash drawer does not open" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:133 -msgid "The cashdrawer should be connected to the printer and the *Cashdrawer* checkbox should be ticked in the POS configuration." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 +msgid "The cash drawer should be connected to the printer and the :guilabel:`Cash drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer checkbox`." msgstr "" #: ../../content/applications/productivity/iot/devices.rst:5 @@ -706,291 +1586,398 @@ msgid "Devices" msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:3 -msgid "Connect a Camera" +msgid "Connect a camera" msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:5 -msgid "When using your *IoT Box* in Odoo, you could need to use a camera. As it can be done in a few steps, this device is really easy to configure. Then, you can use it in your manufacturing process and link it to a control point. Doing so will allow you to take pictures when you reach the chosen quality control point." +msgid "A camera can be connected to an :abbr:`IoT (Internet of Things)` box with an Odoo database in just a few steps. Once a camera is connected to an :abbr:`IoT (Internet of Things)` box, it can be used in a manufacturing process, or it can be linked to a quality control point/quality check. Doing so allows for the taking of pictures when a chosen quality control point/check has been reached, or when a specific key is pressed during manufacturing." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:12 -#: ../../content/applications/productivity/iot/devices/footswitch.rst:13 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:14 #: ../../content/applications/productivity/iot/devices/printer.rst:11 #: ../../content/applications/productivity/iot/devices/scale.rst:10 -#: ../../content/applications/productivity/iot/devices/screen.rst:17 +#: ../../content/applications/productivity/iot/devices/screen.rst:18 msgid "Connection" msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:14 -msgid "To connect the camera to the *IoT Box*, simply connect the two by cable." +msgid "To connect a camera to an :abbr:`IoT (Internet of Things)` box, simply connect the two via cable. This is usually done with a :abbr:`USB (Universal Serial Bus)` cable of some sort." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:17 -msgid "If your camera is a `*supported one* `__, there is no need to set up anything as it will be detected as soon as it is connected." +msgid "If the camera is `supported `_, there is no need to set up anything, as it'll be detected as soon as it's connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:-1 +msgid "Camera recognized on the IoT box." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:25 -msgid "Link a Camera to a Quality Control Point" +msgid "Link camera to quality control point in manufacturing process" msgstr "" -#: ../../content/applications/productivity/iot/devices/camera.rst:28 -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:34 -msgid "With the Manufacturing app" +#: ../../content/applications/productivity/iot/devices/camera.rst:27 +msgid "In the :menuselection:`Quality app`, a device can be set up on a :guilabel:`Quality Control Point`. To do that, navigate to the :menuselection:`Quality app --> Quality Control --> Control Points` and open the desired :guilabel:`Control Point` that'll be linked to the camera." msgstr "" -#: ../../content/applications/productivity/iot/devices/camera.rst:30 -msgid "In your *Quality app*, you can setup the device on a *Quality Control Point*. Go to the *Control Points* menu, under *Quality Control* and open the control point you want to link with the camera." +#: ../../content/applications/productivity/iot/devices/camera.rst:31 +msgid "On the control point form, edit the control point by selecting the :guilabel:`Type` field, and clicking on :guilabel:`Take a Picture` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, wherein the attached *device* can be selected. :guilabel:`Save` the changes, if required." msgstr "" -#: ../../content/applications/productivity/iot/devices/camera.rst:34 -msgid "Now, you can edit the control point and select the device from the dropdown list. Now, hit save." +#: ../../content/applications/productivity/iot/devices/camera.rst:-1 +msgid "Setting up the device on the quality control point." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:40 -msgid "Then, your camera can be used with the picked *Control Point*. During the manufacturing process, reaching the *Quality Control Point* you chose before will allow you to take a picture." +msgid "The camera is now useable with the selected quality control point. When the quality control point is reached during the manufacturing process, the database prompts the operator to take a picture." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:-1 +msgid "Graphic user interface of the device on the quality control point." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:48 +msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`. From here, select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:53 +msgid "On a quality check form, the :guilabel:`Type` of check can also be specified to :guilabel:`Take a Picture`. Navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New` to create a new quality check from the :guilabel:`Quality Checks` page." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:58 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:66 +#: ../../content/applications/productivity/iot/devices/printer.rst:70 +msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_control_points`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:59 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67 +#: ../../content/applications/productivity/iot/devices/printer.rst:71 +msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_alerts`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:62 +msgid "Link camera to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:64 +msgid "To link a camera to an action, it first needs to be configured on a work center. Navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Next, go to the desired :guilabel:`Work Center` in which a camera will be used to reveal that specific work center's detail form. From here, add the device in the :guilabel:`IoT Triggers` tab, in the :guilabel:`Device` column, by clicking :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:70 +msgid "Now, the camera device can be linked to the :guilabel:`Action` column drop-down option labeled :guilabel:`Take a Picture`. A key can also be added to trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:74 +msgid "The first trigger listed is chosen first. The order of triggers matters, and they can be dragged into any desired order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:78 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the camera." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:82 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:52 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:90 +#: ../../content/applications/productivity/iot/devices/printer.rst:95 +msgid ":ref:`workcenter_iot`" msgstr "" #: ../../content/applications/productivity/iot/devices/footswitch.rst:3 -msgid "Connect a Footswitch" +msgid "Connect a footswitch" msgstr "" #: ../../content/applications/productivity/iot/devices/footswitch.rst:5 -msgid "When working, it is always better to have your two hands available. Using Odoo’s *IoT Box* and a footswitch will allow it." +msgid "When working in a manufacturing environment, it's always better for an operator to have both hands available at all times. Odoo's :abbr:`IoT (Internet of Things)` box makes this possible when using a footswitch." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:8 -msgid "In fact, you will be able to go from one screen to another and perform actions by using your foot and the footswitch. Really convenient, it can be configured in a few steps." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:9 +msgid "In fact, with a footswitch, the operator is able to go from one screen to another, and perform actions using their foot. This can be configured in just a few steps on the work center in the *Manufacturing* app." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:15 -msgid "Connecting the footswitch to the *IoT Box* is easy, you just have to connect the two by cable." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:16 +msgid "To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect the two devices via cable. More often than not, this is done with a :abbr:`USB (Universal Serial Bus)` cable." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:18 -msgid "If your footswitch is a `supported one `__, there is no need to set up anything since it will be automatically detected when connected." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:19 +msgid "If the footswitch is a `supported device `_, there is no need to take further action, since it'll be automatically detected when connected." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:26 -msgid "Link a Footswitch to a Workcenter" +#: ../../content/applications/productivity/iot/devices/footswitch.rst:-1 +msgid "Footswitch recognized on the IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:28 -msgid "To link the footswitch to an action, it needs to be configured on a workcenter. Go to the workcenter you want to use the footswitch in and add the device in the *IoT Triggers* tab. Then, you can link it to an action and also add a key to trigger it." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:27 +msgid "Link a footswitch to a work center in the Odoo Manufacturing app" msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:36 -msgid "Note that the one that is first in the list will be chosen. So, the order matters! In the picture above, using the footswitch will, for example, automatically skip the current part of the process you work on." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:29 +msgid "To link a footswitch to an action, it first needs to be configured on a work center. Navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, go to the desired :guilabel:`Work Center` in which the footswitch will be used, and add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Doing so means the footswitch can be linked to an option in the :guilabel:`Action` column drop-down, and optionally, a key can be added to trigger it. An example of an :guilabel:`Action` in the *Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as Done` buttons on a manufacturing work order." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:41 -msgid "When you are on the work order screen, a status button indicates if you are correctly connected to the footswitch." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:-1 +msgid "Footswitch trigger setup on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:43 +msgid "It should be noted that the first listed trigger is chosen first. So, the order matters, and these triggers can be dragged into any order. In the picture above, using the footswitch automatically skips the part of the process that's currently being worked on." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:48 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the footswitch." msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:3 -msgid "Connect a Measurement Tool" +msgid "Connect a measurement tool" msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:5 -msgid "With Odoo’s *IoT Box*, it is possible to connect measurement tools to your database. Find the list of supported devices here: `Supported devices `__,." +msgid "With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect measurement tools to the Odoo database for use in the *Quality app* on a quality control point/quality check, or for use in a work center during the manufacturing process." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:10 -msgid "Connect in USB" +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:9 +msgid "Find the list of supported devices here: `Supported devices `_." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:12 -msgid "To add a device connected by USB, just plug the USB cable in the *IoT Box*, and the device should appear in your Odoo database." +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:13 +msgid "Connect with universal serial bus (USB)" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:19 -msgid "Connect in Bluetooth" +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 +msgid "To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the :abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of Things)` box, and the device appears in the Odoo database." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:21 -msgid "Activate the Bluetooth on your device (see your device manual for further explanation) and the IoT Box will automatically try to connect to the device." +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 +msgid "Measurement tool recognized on the IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:25 -msgid "Here is an example of what it should look like:" +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:24 +msgid "Connect with bluetooth" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:31 -msgid "Link a measurement tool to a quality control point" +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 +msgid "Activate the Bluetooth functionality on the device (see the device manual for further explanation), and the :abbr:`IoT (Internet of Things)` box automatically connects to the device." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:36 -msgid "In your *Quality app*, you can setup a device on your *Quality Control Points*. To do so, go to the *Control Points* menu, under *Quality Control* and open the control point to which you want to assign a measurement tool." +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 +msgid "Bluetooth indicator on measurement tool." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:35 +msgid "Link a measurement tool to a quality control point in the manufacturing process" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 +msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, navigate to :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the measurement tool should be linked." msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:41 -msgid "Now, you can edit the control point and choose the device from the dropdown list. Then, hit save." +msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, where the attached device can be selected." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47 -msgid "Now, your measurement tool is linked to the chosen *Control Point*. The value, which needs to be changed manually, will be automatically updated while the tool is being used." +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:45 +msgid "Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. :guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:48 +msgid "At this point, the measurement tool is linked to the chosen quality control point. The value, which usually needs to be changed manually, is automatically updated while the tool is being used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 +msgid "Measurement tool input in the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:56 +#: ../../content/applications/productivity/iot/devices/printer.rst:60 +msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:61 +msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Measure`. Access a new quality check detail page, by navigating to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:70 +msgid "Link a measurement tool to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 +msgid "To link a measurement tool to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Then, select the desired work center in which the measurement tool will be used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:76 +msgid "On the work center page, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Then, the measurement tool can be linked to the :guilabel:`Action` drop-down menu option labeled :guilabel:`Take Measure`. A key can be added to trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:82 +msgid "It should be noted that the first listed trigger is chosen first. The order matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:86 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the measurement tool." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:3 -msgid "Connect a Printer" +msgid "Connect a printer" msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:5 -msgid "When using your *IoT Box* in Odoo, you could need to use a printer. Doing so is easy and convenient as it can be done in a few steps. Then, you can use it to print receipts, orders or even reports in different Odoo apps." +msgid "Printer installation can be done in a few easy steps. The printer can be used to print receipts, labels, orders, or even reports from the different Odoo apps. In addition, printer actions can be assigned as an *action on a trigger* during the manufacturing process, or added onto a quality control point or a quality check." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:13 -msgid "The IoT Box supports printers connected through USB, network or Bluetooth. `Supported printers `__ will be detected automatically and will appear in the *Devices* list of your IoT app." +msgid "The :abbr:`IoT (Internet of Things)` box supports printers connected through :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. `Supported printers `__ are detected automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:18 -msgid "The printer can take up to two minutes to appear in your devices list." +#: ../../content/applications/productivity/iot/devices/printer.rst:-1 +msgid "The printer as it would appear in the IoT app devices list." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:24 -msgid "Link the Printer" +#: ../../content/applications/productivity/iot/devices/printer.rst:23 +msgid "The printer can take up to two minutes to appear in the *IoT app* devices list." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:27 -msgid "To Work Orders" +#: ../../content/applications/productivity/iot/devices/printer.rst:26 +msgid "Link printer" msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:29 -msgid "You can link *Work Orders* to printers via a *Quality Control Point* to print labels for manufactured products." +msgid "Link printer to work orders" msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:32 -msgid "To do so, you need to create a *Quality Control Point* from the *Quality* app. Then, you can select the correct manufacturing operation and the work order operation. In type, choose *Print Label* and hit save." +#: ../../content/applications/productivity/iot/devices/printer.rst:31 +msgid "*Work Orders* can be linked to printers, via a quality control point, to print labels for manufactured products." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:40 -msgid "Now, each time you reach the quality control point for the chosen product, a *Print Label* button will appear." +#: ../../content/applications/productivity/iot/devices/printer.rst:34 +msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, go to the :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the printer will be linked." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:47 -msgid "To Reports" +#: ../../content/applications/productivity/iot/devices/printer.rst:39 +msgid "A *Manufacturing Operation* and *Work Order Operation* need to be attached to a quality control point before the :guilabel:`Type` field allows for the :guilabel:`Print Label` option to be selected." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:49 -msgid "You can also link a type of report to a certain printer. In the *IoT* app, go to the *Devices* menu and select the printer you want to set up." +#: ../../content/applications/productivity/iot/devices/printer.rst:43 +msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and selecting :guilabel:`Print Label` from the drop-down menu of options. Doing so reveals a field called :guilabel:`Device`, where the attached *device* can be selected. :guilabel:`Save` the changes, if required." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:56 -msgid "Now, go to the *Printer Reports* tab." +#: ../../content/applications/productivity/iot/devices/printer.rst:-1 +msgid "This is the quality control point setup." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:61 -msgid "Hit edit and then, click on *Add a line*. In the window that shows up, check all the types of reports that should be linked to this printer. Click on select and save." +#: ../../content/applications/productivity/iot/devices/printer.rst:52 +msgid "The printer can now be used with the selected quality control point. When the quality control point is reached during the manufacturing process, the database presents the option to print labels for a specific product." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:68 -msgid "Now, each time you click on *Print* in the control panel, instead of downloading a PDF, it will send it to the selected printer and automatically print it." +#: ../../content/applications/productivity/iot/devices/printer.rst:65 +msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Print Label`. To create new quality checks, navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:73 -msgid "Print Receipts from the PoS" +#: ../../content/applications/productivity/iot/devices/printer.rst:74 +msgid "Link a printer to a work center in the Manufacturing app" msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:75 -msgid "You can link a printer to your *Point of Sale* app so you can print receipts directly from your *PoS*." +#: ../../content/applications/productivity/iot/devices/printer.rst:76 +msgid "To link a printer to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, select the desired work center in which the printer will be used. Next, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:78 -msgid "Doing so is really easy. Go to your *Point of Sale* app and open your *Point of Sale* settings, under *Configuration*. There, click on *Edit* and check the *IoT Box* feature. Then, choose your *Receipt Printer* from the dropdown." +#: ../../content/applications/productivity/iot/devices/printer.rst:82 +msgid "Then, the printer can be linked to either of the following options in the :guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, :guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can also be added to trigger the action." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:86 -msgid "Now, you will be able to print different kinds of tickets from your *POS*: **receipts**, **sale details** and **bills**." +#: ../../content/applications/productivity/iot/devices/printer.rst:87 +msgid "The first listed trigger on the form will be chosen first. So, the order matters, and these triggers can be dragged into any order." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:89 -msgid "Receipts are printed once the order is validated. The process is automated when you enable the feature in your *PoS* configuration." +#: ../../content/applications/productivity/iot/devices/printer.rst:91 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the printer." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:92 -msgid "Sales details can be printed by clicking on the printer icon on the navbar at the top of the *PoS*. It will print the details of the sales of the current day." +#: ../../content/applications/productivity/iot/devices/printer.rst:98 +msgid "Link printer to reports" msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:99 -msgid "As for the bill, it is only available in restaurant mode. In your restaurant settings, activate *Print Bills* and a *Bill* button will appear in the left panel of the *PoS*." +#: ../../content/applications/productivity/iot/devices/printer.rst:100 +msgid "It's also possible to link a type of report to a certain printer. In the *IoT app*, go to the :guilabel:`Devices` menu, and select the desired printer that needs to be configured." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:107 -msgid "Print Orders in the kitchen" +#: ../../content/applications/productivity/iot/devices/printer.rst:103 +msgid "From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` tab, and select :guilabel:`Add a line`. In the window that appears, check all the types of :guilabel:`Reports` that should be linked to this printer." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:109 -msgid "In restaurant mode, you can send order tickets to the kitchen." +#: ../../content/applications/productivity/iot/devices/printer.rst:-1 +msgid "The printer devices listed in the IoT Devices menu." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:111 -msgid "To do so, go to the *PoS* app and open your *PoS* settings. Then, tick *Order Printer*." +msgid "Now, each time :guilabel:`Print` is selected in the control panel, instead of downloading a PDF, Odoo sends the report to the selected printer, and automatically prints it." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:117 -msgid "Now, go to the *Printers* menu. Hit create, select the printer from the dropdown and, in the *Printer Product Categories* field, choose all the categories of products that should be printed on this printer." +#: ../../content/applications/productivity/iot/devices/printer.rst:115 +msgid ":doc:`POS Order Printing <../../../sales/point_of_sale/restaurant/kitchen_printing>`" msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:124 -msgid "In the *PoS*, when you add or remove a product from one of the selected categories, the button *Order* will be green. If you click on it, the IoT Box will print a receipt on the corresponding printer." +#: ../../content/applications/productivity/iot/devices/printer.rst:118 +msgid "Reports can also be configured in the :guilabel:`Technical Menu` while in :ref:`debug mode `. To do that, navigate to :menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. From here, the individual report can be found in this list, where the :guilabel:`IoT Device` can be set on the report." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:3 -msgid "Connect a Scale" +msgid "Connect a scale" msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:5 -msgid "When using your **IoT Box** in Odoo, you could need to use a scale. Doing so is easy and convenient as it can be done in a few steps. Then, you can use it in your **Point of Sale app** to weigh your products, which is helpful if their price are based on it." +msgid "A scale can be connected to the :abbr:`IoT (Internet of Things)` box on an Odoo database in a few easy steps. After setup, the *Point of Sale* app can be used to weigh products, which is helpful if their prices are calculated based on weight." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:12 -msgid "To link the scale to the **IoT Box**, connect them with a cable." +msgid "To link the scale to the :abbr:`IoT (Internet of Things)` box, connect it with a :abbr:`USB (Universal Serial Bus)` cable." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:15 -msgid "In some cases, a serial to USB adapter may be needed." +#: ../../content/applications/productivity/iot/devices/scale.rst:16 +msgid "In some cases, a serial port to :abbr:`USB (Universal Serial Bus)` adapter may be needed." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:17 -msgid "If your scale is `compatible with Odoo IoT Box `_, there is no need to set up anything because it will be automatically detected as soon as it is connected." +#: ../../content/applications/productivity/iot/devices/scale.rst:18 +msgid "If the scale is `compatible with Odoo IoT Box `_, there is no need to set up anything because it will be automatically detected as soon as it is connected." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:None +#: ../../content/applications/productivity/iot/devices/scale.rst:-1 msgid "IOT box auto detection." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:24 -msgid "You may need to restart the box and download your scales’ drivers from the box in some cases. To do so, go to the *IoT Box Home Page* and click on *drivers list*. Then, click on load drivers." +#: ../../content/applications/productivity/iot/devices/scale.rst:25 +msgid "The :abbr:`IoT (Internet of Things)` box may need to be restarted and the scale's drivers may need to be downloaded to the box in some cases. To update the drivers, go to the :abbr:`IoT (Internet of Things)` box homepage and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load Drivers`." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:None +#: ../../content/applications/productivity/iot/devices/scale.rst:-1 msgid "View of the IoT box settings and driver list." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:32 -msgid "Use a Scale in Point of Sale" -msgstr "" - #: ../../content/applications/productivity/iot/devices/scale.rst:34 -msgid "To use the scale in your *Point of Sale* app, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the one you want to configure, then click on *Edit* and enable the *IoT Box* feature." +msgid "If loading the drivers still doesn't allow for the scale to function, it may be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of Things)` box. In this case, a different scale will need to be used." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:None -msgid "View of the IoT box feature inside of the PoS settings." +#: ../../content/applications/productivity/iot/devices/scale.rst:39 +msgid "Use a scale in a point of sale (POS) system" msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:42 -msgid "Now, choose the *IoT Box* in the dropdown menu and check the *Electronic Scale* option. Then, you hit save." +#: ../../content/applications/productivity/iot/devices/scale.rst:41 +msgid "To use the scale in the *Point of Sale app*, go to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> Settings`, then enable the :abbr:`IoT (Internet of Things)` box feature. After this is complete, the scale device can be set." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:None +#: ../../content/applications/productivity/iot/devices/scale.rst:45 +msgid "Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then click :guilabel:`Save` to save the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:-1 msgid "List of the external tools that can be used with PoS and the IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:49 -msgid "The scale is now available in all your *PoS* sessions. Then, if a product has a price per weight set, clicking on it on the *PoS* screen opens the scale screen, where the cashier can weigh the product and add the correct price to the cart." +#: ../../content/applications/productivity/iot/devices/scale.rst:52 +msgid "The scale is now available in all the :abbr:`PoS (Point of Sale)` sessions. Now, if a product has a price per weight set, clicking on it on the :guilabel:`PoS` screen opens the scale screen, where the cashier can weigh the product and add the correct price to the cart." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:None +#: ../../content/applications/productivity/iot/devices/scale.rst:-1 msgid "Electronic Scale dashboard view when no items are being weighed." msgstr "" @@ -999,113 +1986,117 @@ msgid "Connect a screen" msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:5 -msgid "In Odoo, an :abbr:`IoT (Internet of Things)` Box can be connected to a screen display. After being connected, the screen can be used to display a :abbr:`PoS (Point of Sale)` order to a client." +msgid "In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a screen display. After being configured, the screen can be used to display a Point of Sale (PoS) order to a client." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:None +#: ../../content/applications/productivity/iot/devices/screen.rst:10 msgid "An example of a PoS (point of sale) order on a screen display." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:13 -msgid "Access the customer display from any other computer by going to the :abbr:`IoT (Internet of Things)` Box homepage and clicking on the :guilabel:`POS Display` button." +#: ../../content/applications/productivity/iot/devices/screen.rst:12 +msgid "Access the customer display by going to the :abbr:`IoT (Internet of Things)` box homepage and clicking on the :guilabel:`PoS Display` button. To get to the :abbr:`IoT (Internet of Things)` box homepage, navigate to :menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet of Things)` box homepage link." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:19 -msgid "The way to connect the screen display to the :abbr:`IoT (Internet of Things)` Box differs depending on the model." +#: ../../content/applications/productivity/iot/devices/screen.rst:20 +msgid "The way to connect the screen display to the :abbr:`IoT (Internet of Things)` box differs depending on the model." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:24 +#: ../../content/applications/productivity/iot/devices/screen.rst:25 msgid "IoT Box model 4" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:26 -msgid "Connect up to two screens with Micro-HDMI cables on the side of the :abbr:`IoT (Internet of Things)` Box. If two screens are connected, they can display distinct content (see usage below)." +#: ../../content/applications/productivity/iot/devices/screen.rst:27 +msgid "Connect up to two screens with micro-HDMI cables on the side of the :abbr:`IoT (Internet of Things)` box. If two screens are connected, they can display distinct content (see :ref:`Screen Usage `)." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:30 +#: ../../content/applications/productivity/iot/devices/screen.rst:31 msgid "IoT Box model 3" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:32 -msgid "Connect the screen with an HDMI cable on the side of the :abbr:`IoT (Internet of Things)` Box." +#: ../../content/applications/productivity/iot/devices/screen.rst:33 +msgid "Connect the screen with an HDMI cable on the side of the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:35 -msgid "Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` Box is switched on. If it is already on, connect the screen(s), and then restart the :abbr:`IoT (Internet of Things)` Box by unplugging it and plugging it back into its power source." +#: ../../content/applications/productivity/iot/devices/screen.rst:36 +msgid ":ref:`See the Raspberry Pi Schema `." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:40 -msgid "The usage of HDMI/Micro-HDMI adapters may cause issues which will result in a blank, black screen on the screen display. Cable usage is recommended." +#: ../../content/applications/productivity/iot/devices/screen.rst:39 +msgid "Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` box is switched on. If it is already on, connect the screen(s), and then restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten seconds and plugging it back into its power source." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:43 +#: ../../content/applications/productivity/iot/devices/screen.rst:44 +msgid "The usage of HDMI/micro-HDMI adapters may cause issues which will result in a blank, black screen on the screen display. Using the specific cable for the display connection is recommended." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:47 msgid "If the connection was successful, the screen should display the :guilabel:`POS Client display` screen." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:None +#: ../../content/applications/productivity/iot/devices/screen.rst:-1 msgid "The default \"POS Client Display\" screen that appears when a screen display is successfully\n" -"connected to an IoT Box." +"connected to an IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:51 -msgid "The screen should also appear in the list of :guilabel:`Displays` on the :abbr:`IoT (Internet of Things)` Box homepage." +#: ../../content/applications/productivity/iot/devices/screen.rst:55 +msgid "The screen should also appear in the list of :guilabel:`Displays` on the :abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display can be seen by accessing :menuselection:`IoT app --> Devices`." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:None -msgid "An example of a screen display name shown on the IoT Box homepage." +#: ../../content/applications/productivity/iot/devices/screen.rst:-1 +msgid "An example of a screen display name shown on the IoT Box Home Page." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:59 -msgid "If no screen is detected, a default display named :guilabel:`Distant Display` will be used instead." +#: ../../content/applications/productivity/iot/devices/screen.rst:64 +msgid "If no screen is detected, a default display named :guilabel:`Distant Display` will be displayed instead. This indicates that there is no hardware screen connected." msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:0 msgid "The \"Distant Display\" screen name will be used if no screen is detected." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:67 +#: ../../content/applications/productivity/iot/devices/screen.rst:74 msgid "Usage" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:70 -msgid "Show Point of Sales orders to customers" +#: ../../content/applications/productivity/iot/devices/screen.rst:77 +msgid "Show Point of Sale orders to customers" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:72 -msgid "To use the screen in the :guilabel:`Point of Sale` app, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the desired screen, click on :guilabel:`Edit`, and enable the :guilabel:`IoT Box Devices` feature." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:76 -msgid "Now, select :guilabel:`IoT Box` in the drop-down menu and choose the screen in the :guilabel:`Customer Display` option. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:0 -msgid "Connect the screen display to the Point of Sale app." +#: ../../content/applications/productivity/iot/devices/screen.rst:79 +msgid "To use the screen in the *Point of Sale app*, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select a :abbr:`PoS (Point of Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT Box` feature." msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:83 -msgid "The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A \"screen\" icon will appear in the top bar to inform the connection status with the screen." +msgid "Next, select the screen from the :guilabel:`Customer Display` drop-down menu. Then click :guilabel:`Save`, if required." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:0 +#: ../../content/applications/productivity/iot/devices/screen.rst:-1 +msgid "Connect the screen display to the Point of Sale app." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:90 +msgid "The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A screen icon will appear in the menu at the top of the screen to indicate the screen's connection status." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:-1 msgid "The \"screen\" icon on the Point of Sale display shows the connection status with the\n" "screen." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:91 -msgid "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are performed on the order." +#: ../../content/applications/productivity/iot/devices/screen.rst:98 +msgid "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are made to the order." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:None +#: ../../content/applications/productivity/iot/devices/screen.rst:-1 msgid "An example of a PoS order on a screen display." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:99 -msgid "Display a website" +#: ../../content/applications/productivity/iot/devices/screen.rst:106 +msgid "Display a website on the screen" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:101 -msgid "Opening the screen form view at :menuselection:`IoT --> Devices --> (screen device)` allows the user to choose a particular website URL to display on the screen with the :guilabel:`Screen URL` field." +#: ../../content/applications/productivity/iot/devices/screen.rst:108 +msgid "Open the screen form view by accessing :menuselection:`IoT app --> Devices --> Customer Display`. This allows the user to choose a particular website URL to display on the screen using the :guilabel:`Display URL` field." msgstr "" #: ../../content/applications/productivity/studio.rst:8 @@ -1136,7 +2127,7 @@ msgstr "" msgid "Examples of automated actions include: creating a next activity upon a quote's confirmation; adding a user as a follower of a confirmed invoice if its total is higher than a certain amount; or preventing a lead from changing stage if a field is not filled in." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:None +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:-1 msgid "Flowchart to exemplify an automated action rule for Odoo Studio" msgstr "" @@ -1192,83 +2183,83 @@ msgstr "" msgid "The **Active** option is to be turned off when the rule should be hidden and not executed." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:43 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:46 msgid "Under **Action To Do** choose the type of server action that must be executed once records meet the *Trigger* conditions:" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:45 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:48 msgid "*Execute Python Code*: a block of code is executed. A *Help* tab with the variables that can be used is available." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:47 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:50 msgid "*Create New Record*: a new record with new values is created." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:48 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:51 msgid "*Update a Record*: updates the record that triggered the action." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:49 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:52 msgid "*Execute several actions*: defines an action that triggers other server actions." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:50 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:53 msgid "*Send Email*: an automatic :doc:`email ` is sent." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:51 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:54 msgid "*Add Followers*: followers are notified of changes in the task." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:52 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:55 msgid "*Create Next Activity*: creates an activity such as: *Call*, *Email*, *Reminder*." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:53 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:56 msgid "*Send SMS Text Message*: sends an :doc:`SMS `." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:56 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:59 msgid "Example" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:58 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:61 msgid "This is the process of which the update of the *Email* field on the Lead/Opportunity *Model*, with a *Trigger Condition* set to *On Update*, goes through:" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:None +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:-1 msgid "View of an automated action being created in Odoo Studio" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:65 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:68 msgid "The user creates the record without an email address set." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:66 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:69 msgid "The user updates the record defining an email address." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:67 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:70 msgid "Once the change is saved, the automation checks if any of the *Watched Fields* are being updated (for the example: field name *email_from* (Email)." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:69 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:72 msgid "If true, it checks if the record matches the *Before Update Domain* (for the example: *email is not set*)." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:71 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:74 msgid "If true, it checks (*after the update*) whether the record matches the *Apply on* domain (for the example: *email is set*)." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:73 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:76 msgid "If true, the chosen *Action To Do* is performed on the record." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:76 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:79 msgid ":doc:`understanding_general`" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:77 +#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:80 msgid ":doc:`../use_cases/automated_actions`" msgstr "" @@ -1304,7 +2295,7 @@ msgstr "" msgid "In object-oriented programming, models usually represent a concept from the real world. Example: Odoo has models for Sales Orders, Users, Countries, etc. If you were to build an application to manage Real Estate sales, a model that represents the Properties for sale would probably be your first step." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:None +#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:-1 msgid "Overview of the main dashboard emphasizing the option to create a new app in Odoo Studio" msgstr "" @@ -1348,7 +2339,7 @@ msgstr "" msgid "In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:None +#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:-1 msgid "Tables with a visual explanation of related fields for Odoo Studio" msgstr "" @@ -1396,7 +2387,7 @@ msgstr "" msgid "A **Menu** is a button that executes an action. In Odoo Studio, to create menus (models) and rearrange their hierarchy, click on *Edit Menu*." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:None +#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:-1 msgid "Overview of a menu being edit in Odoo Studio" msgstr "" @@ -1420,7 +2411,7 @@ msgstr "" msgid "To export these customizations, activate Studio on the main dashboard and, under the menu *Customizations*, click on *Export*. The default filename is *customizations.zip*." msgstr "" -#: ../../content/applications/productivity/studio/how_to/export_import.rst:None +#: ../../content/applications/productivity/studio/how_to/export_import.rst:-1 msgid "View of the menu customizations in Odoo Studio" msgstr "" @@ -1432,7 +2423,7 @@ msgstr "" msgid "To import and install the customizations in another instance, connect to the destination database, activate Studio and, under *Customizations*, click on *Import*." msgstr "" -#: ../../content/applications/productivity/studio/how_to/export_import.rst:None +#: ../../content/applications/productivity/studio/how_to/export_import.rst:-1 msgid "View of the import modules window for Odoo Studio" msgstr "" @@ -1448,8 +2439,7 @@ msgstr "" msgid "The Rainbow Man in Odoo is an animation shown once the user completes certain tasks and clicks on certain buttons. It is a way to make the software fun to use, and rewarding, for employees." msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:None -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:None +#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:-1 msgid "View of a sales form and the tab properties and its rainbow man field in Odoo Studio" msgstr "" @@ -1489,7 +2479,7 @@ msgstr "" msgid "When creating a new report, choose the purpose of it and if you would like the report to include header and footer (company logo, name, address, phone, email address, etc.)." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:None +#: ../../content/applications/productivity/studio/how_to/reports.rst:-1 msgid "View of the types of new reports in Odoo Studio" msgstr "" @@ -1497,7 +2487,7 @@ msgstr "" msgid "Under the tab **Add**, you find the fields to be dragged and dropped to the view. *Fields*, *Data tables*, *Subtotal & Total*, and *Address Book* are dynamic elements (meaning that they need a :doc:`one2many or a many2many <../concepts/understanding_general>` related object). *Text*, *Title Block*, *Image*, and *Text in Cell* are static elements." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:None +#: ../../content/applications/productivity/studio/how_to/reports.rst:-1 msgid "View of a report and the tab add in Odoo Studio" msgstr "" @@ -1505,7 +2495,7 @@ msgstr "" msgid "Once the element is added to the view, select it to see its **Options**. The first section shows the hierarchy of the selected object and its properties, allowing you to individually edit them. Fields with related objects have their directives shown on *Field Expression*." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:None +#: ../../content/applications/productivity/studio/how_to/reports.rst:-1 msgid "View of a report and the tab options in Odoo Studio" msgstr "" @@ -1521,7 +2511,7 @@ msgstr "" msgid "**Visible for** is used to set which :doc:`groups ` can have access to specific elements in the report. **Limit visibility to groups**, under *Report*, sets the visibility of the report to specifics groups, meaning that users belonging to other groups do not see the same final document." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:None +#: ../../content/applications/productivity/studio/how_to/reports.rst:-1 msgid "View of a report’s settings emphasizing the field limit visibility to groups in Odoo Studio" msgstr "" @@ -1529,7 +2519,7 @@ msgstr "" msgid "Under the **Report** tab, name your report, choose the paper format, and if the report should be added to the *Print* menu list on its respective document form." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:None +#: ../../content/applications/productivity/studio/how_to/reports.rst:-1 msgid "View of an invoice form emphasizing the menu print for Odoo Studio" msgstr "" @@ -1594,7 +2584,7 @@ msgstr "" msgid "*Data to Write*: Lead/Opportunity > Value > 3" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:None +#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:-1 msgid "View of an automated action that sets a high priority to Belgian leads in Odoo Studio" msgstr "" @@ -1625,7 +2615,7 @@ msgstr "" msgid "On your customer’s page, use *Filters* > *Add Custom Filter* to group customers by country. Now, under *Favorites*, *Save Current Search* enabling *Use by default* and *Save*." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:None +#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:-1 msgid "View of a custom filter being set to be used by default in Odoo" msgstr "" @@ -1633,7 +2623,7 @@ msgstr "" msgid "On *Filter Rules* in Studio mode, select the respective filter and enable *Default Filter*." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:None +#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:-1 msgid "View of a filter’s rule form emphasizing the field default filter in Odoo Studio" msgstr "" @@ -1649,7 +2639,7 @@ msgstr "" msgid "On the *Views* menu, access *Kanban* and, under its *View* options, set the *Default Group by* as *Pipeline status bar*." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:None +#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:-1 msgid "Form view emphasizing the button add a pipeline bar in Odoo Studio" msgstr "" @@ -1693,7 +2683,7 @@ msgstr "" msgid "*Data to Write*: Cost (Product Template) > Value > 0" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:None +#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:-1 msgid "View of the automated action created to set the price of a product to zero in Odoo Studio" msgstr "" @@ -1717,7 +2707,7 @@ msgstr "" msgid "You can now hide the related field created (*Country*) if you wish." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "View of the invisibility domain of a field being set in Odoo Studio" msgstr "" @@ -1733,7 +2723,7 @@ msgstr "" msgid "Again, hide the related field with the country’s ID if you prefer." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "View of an URL emphasizing where a country’s ID can be found for Odoo Studio" msgstr "" @@ -1745,7 +2735,7 @@ msgstr "" msgid "From the dashboard, (optionally) start a new module. Then, click on *Edit Menu* and start a *New Menu* (model). Set your menu name and *Confirm*. Now, on its form, drag & drop the necessary fields." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "View of the recommended fields for an object in Odoo Studio" msgstr "" @@ -1765,8 +2755,8 @@ msgstr "" msgid "The *Existing Fields* are the ones that are on the current model but not yet in the view." msgstr "" +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:0 -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None msgid "Form view and a Many2one field being dropped in Odoo Studio" msgstr "" @@ -1778,7 +2768,7 @@ msgstr "" msgid "*Status buttons* are computed fields, meaning that they count the numbers of records on the related model, and allow you to access them." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "Form view and the status button window being shown in Odoo Studio" msgstr "" @@ -1798,7 +2788,7 @@ msgstr "" msgid "Once the field *Tags* is added to the form, select it and, under its *Properties > Widgets*, choose *Checkboxes*." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "Form view showing the widgets available in Odoo Studio" msgstr "" @@ -1810,7 +2800,7 @@ msgstr "" msgid "In your form view, add a *Tags* field and relate it to *Partners Tag*. Under *Properties*, define its *Widget* as *Many2many*. Do the same process another 2 times for *Checkboxes* and *Tags*." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "Form view emphasizing the widget property in Odoo Studio" msgstr "" @@ -1822,7 +2812,7 @@ msgstr "" msgid "Continue by selecting your *Tags* fields, one by one, to set their *Invisible* options according to their *Widget*. In the example below, the invisibility rule for the *Partner Tags* is set as: *Select Tag type > is not = > Tags.*" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "Form view emphasizing a field added and its invisibility properties in Odoo Studio" msgstr "" @@ -1834,7 +2824,7 @@ msgstr "" msgid "On your quotation form, add a *Selection* field with the values *Accepted* and *Refused*. Set its *Required* condition as *Untaxed Amount > 500* and the *Limit visibility to groups* as *Sales / Administrator* or managers." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "Form view of a required domain being set in Odoo Studio" msgstr "" @@ -1850,7 +2840,7 @@ msgstr "" msgid "Select the necessary field and, under *Properties*, click on *More* to write your tooltip message on *Field Help*. The tooltip message is the explanatory message shown when the user hovers the field. The message here written is displayed on all views forms where the field is added." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:None +#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:-1 msgid "Form view showing more property options and emphasizing the help feature in Odoo Studio" msgstr "" @@ -1874,7 +2864,7 @@ msgstr "" msgid "From the Sales page, access Studio and, under *Views*, set the *Kanban* option as the default one." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/views.rst:None +#: ../../content/applications/productivity/studio/use_cases/views.rst:-1 msgid "View of the Kanban option being set as the default one in Odoo Studio" msgstr "" @@ -1890,6 +2880,6 @@ msgstr "" msgid "If the field is left blank, no editing is possible and records are shown based on your column preferences on the lead's page (front-end)." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/views.rst:None +#: ../../content/applications/productivity/studio/use_cases/views.rst:-1 msgid "View options emphasizing the editable options of a leads page in Odoo Studio" msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index e67bff3e8..9868cf54b 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -57,17 +57,18 @@ msgstr "" #: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:10 #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:12 #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12 -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:9 -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:10 -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:9 -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:12 -#: ../../content/applications/sales/point_of_sale/payment/six.rst:16 -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:13 -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:14 -#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:10 +#: ../../content/applications/sales/point_of_sale/configuration.rst:6 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:11 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:16 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:11 +#: ../../content/applications/sales/point_of_sale/restaurant.rst:20 +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:17 -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:8 #: ../../content/applications/sales/rental.rst:20 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:9 @@ -141,7 +142,7 @@ msgstr "" msgid "Each Sales Team can use its own unique email alias to generate leads/opportunities. Any email sent to a Sales Team's email alias will automatically create a lead (if leads are activated in your CRM settings) or an opportunity in the pipeline for that particular team. Configure custom email aliases on the configuration page for each Sales Team by navigating to :menuselection:`CRM --> Configuration --> Sales Teams`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:None +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 msgid "Configuring Sales Teams" msgstr "" @@ -153,7 +154,7 @@ msgstr "" msgid "By default, your website's *Contact Us* page displays Odoo's ready-to-use Contact Form. Whenever someone submits this form, a lead or an opportunity is generated in your database." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:None +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 msgid "Default Contact Us page" msgstr "" @@ -161,7 +162,7 @@ msgstr "" msgid "The Contact Form can be activated or deactivated at any time by going to :menuselection:`Website --> Go to Website --> Customize --> Contact Form`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:None +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 msgid "Contact Form toggle" msgstr "" @@ -169,7 +170,7 @@ msgstr "" msgid "When the Form is deactivated, the *Contact Us* page simply displays a button to email your company directly. Any email sent this way will generate a lead/opportunity." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:None +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 msgid "Contact Us Page using email" msgstr "" @@ -177,7 +178,7 @@ msgstr "" msgid "Choose which Sales Team or salesperson is automatically assigned to the leads/opportunities created from the Contact Form by going to :menuselection:`Website --> Configuration --> Settings --> Communication`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:None +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 msgid "Contact Form settings" msgstr "" @@ -193,7 +194,7 @@ msgstr "" msgid "The *Form Builder* module is installed automatically when a Form element is added to a web page via the Website Builder. It can also be installed manually from the :guilabel:`Apps` page." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:None +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 msgid "Form Builder building blocks" msgstr "" @@ -241,7 +242,7 @@ msgstr "" msgid ":guilabel:`Shown on Mobile`: Toggle this option to show the field to users on mobile devices." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:None +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 msgid "Editable field options" msgstr "" @@ -265,7 +266,7 @@ msgstr "" msgid "To get started, go to :menuselection:`CRM --> Configuration --> Settings` and activate :guilabel:`Lead Mining`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 msgid "Activate lead mining in Odoo CRM settings." msgstr "" @@ -277,7 +278,7 @@ msgstr "" msgid "After the :guilabel:`Lead Mining` setting is activated, a new button called :guilabel:`Generate Leads` is available to use in the :guilabel:`CRM` pipeline. Lead mining requests are also available through :menuselection:`CRM --> Configuration --> Lead Mining Requests`, or through :menuselection:`CRM --> Leads --> Leads` where the :guilabel:`Generate Leads` button is also available." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 msgid "The Generate Leads button to use the lead mining feature." msgstr "" @@ -285,7 +286,7 @@ msgstr "" msgid "Click on the :guilabel:`Generate Leads` button, and a window will appear offering a variety of criteria by which to generate leads." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 msgid "The pop-up window with the selection criteria in order to generate leads in Odoo." msgstr "" @@ -351,7 +352,7 @@ msgstr "" msgid "To buy credits, navigate to :menuselection:`CRM --> Configuration --> Settings`. In the :guilabel:`Lead Generation` section, under the :guilabel:`Lead Mining` feature, click on :guilabel:`Buy Credits`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 msgid "Buy credits from the lead mining settings." msgstr "" @@ -359,7 +360,7 @@ msgstr "" msgid "Credits may also be purchased by navigating to the :menuselection:`Settings --> General Settings`. In the :guilabel:`In-App Purchases` section, under the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 msgid "Buy credits in the Odoo IAP settings." msgstr "" @@ -420,7 +421,7 @@ msgstr "" msgid "Install the *Gamification* module, or the *CRM gamification* one, which adds some useful data (goals and challenges) that can be used on *CRM/Sale*." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:None +#: ../../content/applications/sales/crm/optimize/gamification.rst:-1 msgid "View of the gamification module being installed in Odoo" msgstr "" @@ -436,7 +437,7 @@ msgstr "" msgid "As the gamification tool is a one-time technical setup, you need to activate the technical features in order to access the configuration. To do so, go to *Settings* and *Activate the developer mode*." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:None +#: ../../content/applications/sales/crm/optimize/gamification.rst:-1 msgid "View if the gamification tools menu in Odoo Settings" msgstr "" @@ -472,7 +473,7 @@ msgstr "" msgid "In the example below, 2 employees are being challenged with a *Monthly Sales Target*. The challenge is based on 2 goals: the total amount invoiced and number of new leads generated. At the end of the month, the winner will be granted with a badge." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:None +#: ../../content/applications/sales/crm/optimize/gamification.rst:-1 msgid "View of the challenge form and a challenge being created for Odoo Sales" msgstr "" @@ -492,7 +493,7 @@ msgstr "" msgid "You can create a new goal on the fly from a *Challenge* by clicking on *Add new item*, under *Goals*. Select the business object according to your company's needs. Examples: number of new leads, time to qualify a lead, total amount invoiced in a specific week, month or any other time frame based on your management preferences, etc." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:None +#: ../../content/applications/sales/crm/optimize/gamification.rst:-1 msgid "View of the goal definition form and a goal definition being created for Odoo Sales" msgstr "" @@ -508,7 +509,7 @@ msgstr "" msgid "For non-numerical achievements, **Badges** can be granted to users. From a simple thank you to an exceptional achievement, a badge is an easy way to express gratitude to a user for their good work. To create and grant badges to your employees based on their performance, go to :menuselection:`Settings --> Gamification Tools --> Badges`." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:None +#: ../../content/applications/sales/crm/optimize/gamification.rst:-1 msgid "View of the badges page in Odoo" msgstr "" @@ -532,7 +533,7 @@ msgstr "" msgid "Search and store insights on your contacts." msgstr "" -#: ../../content/applications/sales/crm/optimize/outlook_extension.rst:None +#: ../../content/applications/sales/crm/optimize/outlook_extension.rst:-1 msgid "Overview of the Outlook Extension in Outlook" msgstr "" @@ -568,7 +569,6 @@ msgstr "" msgid "URL of the **Odoo for Outlook** add-in's manifest file:" msgstr "" -#: ../../content/applications/sales/crm/optimize/outlook_extension.rst:0 #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:0 msgid "``https://download.odoo.com/plugins/outlook/manifest.xml``" msgstr "" @@ -629,7 +629,7 @@ msgstr "" msgid "By default, you can open the **Odoo for Outlook** extension from the *More actions* menu. This section explains how to move the launcher next to the other default actions." msgstr "" -#: ../../content/applications/sales/crm/optimize/outlook_extension.rst:None +#: ../../content/applications/sales/crm/optimize/outlook_extension.rst:-1 msgid "Odoo for Outlook extension as a default action in the mailbox" msgstr "" @@ -693,7 +693,7 @@ msgstr "" msgid "The extension allows you to test this service for free, whether you connect the extension to a database or not. After a while, the extension asks you to buy credits to keep using this additional service." msgstr "" -#: ../../content/applications/sales/crm/optimize/outlook_extension.rst:None +#: ../../content/applications/sales/crm/optimize/outlook_extension.rst:-1 msgid "\"Could not auto-complete the company: not enough credits!\" warning message in the Outlook\n" "extension" msgstr "" @@ -744,7 +744,7 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Contacts` and activate the *Partner Autocomplete* feature." msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:None +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:-1 msgid "View of settings page and the activations of the feature in Odoo" msgstr "" @@ -760,11 +760,11 @@ msgstr "" msgid "For example, after typing *Odoo*, you will get the following information:" msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:None +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:-1 msgid "Creating a new contact in Odoo" msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:None +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:-1 msgid "View of the information being shown about odoo with the autocomplete option in Odoo" msgstr "" @@ -800,7 +800,7 @@ msgstr "" msgid "From the *General Settings*, activate *Google Drive* and *Google Spreadsheet*. The options *Authorization Code* and *Get Authorization Code* are now available." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1 msgid "Enable the Google Drive and Google Spreadsheet features in Odoo" msgstr "" @@ -836,7 +836,7 @@ msgstr "" msgid "From the *CRM* app, for example, go to *Favorites* and click on *Add to Google Spreadsheet*." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1 msgid "From the CRM application, for example, click on add to Google Spreadsheet in Odoo" msgstr "" @@ -860,7 +860,7 @@ msgstr "" msgid "Go to :menuselection:`Odoo --> Server Settings --> Database Name --> Username --> Password`." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1 msgid "Menu called Odoo is shown on the settings bar in the Spreadsheet" msgstr "" @@ -888,7 +888,7 @@ msgstr "" msgid "Find some the arguments in the table below." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1 msgid "Table with examples of arguments to use in Odoo" msgstr "" @@ -904,7 +904,7 @@ msgstr "" msgid "Find some arguments in the table below." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1 msgid "Table with examples of grouped sum arguments to use in Odoo" msgstr "" @@ -1044,7 +1044,7 @@ msgstr "" msgid "Set a *Domain* to assign leads/opportunities to this Sales Team based on specific filters, such as country, language, or campaign. Set an *Invoicing Target* if this team has specific monthly revenue goals." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:None +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1 msgid "Creating a Sales Team" msgstr "" @@ -1056,7 +1056,7 @@ msgstr "" msgid "To add team members, click **Add** under the Assignment tab when editing the Sales Team's configuration page. Select a salesperson from the dropdown menu or create new salesperson. Set a maximum number of leads that can be assigned to this salesperson in a 30-day period to ensure that they do not overwork." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:None +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1 msgid "Adding a Salesperson" msgstr "" @@ -1076,7 +1076,7 @@ msgstr "" msgid "Each tile gives an overview of the Sales Team's open opportunities, quotations, sales orders, and expected revenue, as well as a bar graph of new opportunities per week and an invoicing progress bar." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:None +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1 msgid "Sales Team Overview" msgstr "" @@ -1084,7 +1084,7 @@ msgstr "" msgid "Click on the three dots in the corner of a tile to open a navigational menu that lets you quickly view documents or reports, create new quotations or opportunities, pick a color for this team, or access its configuration page." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:None +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1 msgid "Three Dot Menu" msgstr "" @@ -1112,7 +1112,7 @@ msgstr "" msgid "To use scoring, go to :menuselection:`Apps`, remove the :guilabel:`Apps` filter, search for :guilabel:`Lead Scoring` and then install the module." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:None +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1 msgid "Lead Scoring module installation" msgstr "" @@ -1128,7 +1128,7 @@ msgstr "" msgid "Customize your rules to fit the needs of your business, and add as many criteria as you want." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:None +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1 msgid "Score Rule example" msgstr "" @@ -1136,7 +1136,7 @@ msgstr "" msgid "Every hour, Odoo automatically assigns scores to new leads according to your configured rules." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:None +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1 msgid "Scoring section on a lead" msgstr "" @@ -1148,7 +1148,7 @@ msgstr "" msgid "Odoo can also assign leads to specific teams based on configured rules. To configure assignment rules, go to the individual Sales Team's configuration page via :menuselection:`CRM --> Leads --> Team Assignment` or :menuselection:`CRM --> Configuration --> Sales Teams`, and apply a specific Domain to each team. The Domain can include lead scores." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:None +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1 msgid "Team Assignments using domains" msgstr "" @@ -1156,7 +1156,7 @@ msgstr "" msgid "Assign leads to specific salespeople using further refined Domains at :menuselection:`CRM --> Leads --> Leads Assignment`." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:None +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1 msgid "Lead Assignments" msgstr "" @@ -1176,7 +1176,7 @@ msgstr "" msgid "To view your unassigned leads, go to :menuselection:`CRM --> Leads --> Leads` and select the Unassigned filter." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:None +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1 msgid "Filtering for unassigned leads" msgstr "" @@ -1232,1117 +1232,1579 @@ msgstr "" msgid "Your customers will no longer be able to keep any secrets from you!" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:8 +#: ../../content/applications/sales/point_of_sale.rst:6 msgid "Point of Sale" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:10 -msgid "With **Odoo Point of Sale**, run your shops or restaurants easily. The app runs on the browser, but is able to continue working even if you are offline." +#: ../../content/applications/sales/point_of_sale.rst:8 +msgid "With **Odoo Point of Sale**, run your shops and restaurants easily. The app works on any device with a web browser, even if you are temporarily offline. Product moves are automatically registered in your stock, you get real-time statistics, and your data is consolidated across all shops." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:14 +#: ../../content/applications/sales/point_of_sale.rst:13 msgid "`Odoo Tutorials: Point of Sale Tutorials `_" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:15 +#: ../../content/applications/sales/point_of_sale.rst:14 msgid ":doc:`IoT Boxes Documentations `" msgstr "" -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features.rst:5 -msgid "Pricing Features" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:3 -msgid "Using discount tags with a barcode scanner" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:5 -msgid "If you want to sell your products with a discount, for a product getting close to its expiration date for example, you can use discount tags. They allow you to scan discount barcodes." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:10 -msgid "To use discount tags you will need to use a barcode scanner." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:13 -msgid "Barcode Nomenclature" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:15 -msgid "To use discounts tags, we need to learn about barcode nomenclature." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:17 -msgid "Let's say you want to have a discount for the product with the following barcode:" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:23 -msgid "You can find the *Default Nomenclature* under the settings of your PoS interface." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:32 -msgid "Let's say you want 50% discount on a product you have to start your barcode with 22 (for the discount barcode nomenclature) and then 50 (for the %) before adding the product barcode. In our example, the barcode would be:" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:41 -msgid "Scan the products & tags" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:43 -msgid "You first have to scan the desired product (in our case, a lemon)." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:48 -msgid "And then scan the discount tag. The discount will be applied and you can finish the transaction." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:3 -msgid "Apply Discounts" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:5 -msgid "By offering discounts, you can entice your customers and drastically increase your revenue. It is vital to offer discounts, whether they are time-limited, seasonal or manually given." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:9 -msgid "To manage discounts, Odoo has powerful features that help set up a pricing strategy tailored to every business." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:13 -msgid "Apply manual discounts" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:15 -msgid "If you seldom use discounts, applying manual ones might be the easiest solution for your Point of Sale." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:18 -msgid "You can either apply a discount on the whole order or on specific products inside an order." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:22 -msgid "Apply a discount on a product" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:24 -msgid "From your PoS session interface, use the *Disc* button." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:None -msgid "View of the discount button for manual discount" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:30 -msgid "Then, you can input a discount over the product that is currently selected." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:34 -msgid "Apply a global discount" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:36 -msgid "To apply a discount on the whole order, go to :menuselection:`Point of Sales --> Configuration --> Point of Sale` and select your PoS." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:39 -msgid "Once on your PoS form, select *Global Discounts*, under the *Pricing* category." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:None -msgid "View of the feature to enable for global discount" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:45 -msgid "Now, you have a new *Discount* button appearing on your PoS interface." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:None -msgid "View of the button to use for global discount via the pos interface" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:51 -msgid "Click on it and enter the wanted discount." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:None -msgid "View of the discount offered in the payment summary" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:58 -msgid "On this example, there is a global discount of 50% as well as a specific 50% discount on oranges." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:62 -msgid "Apply time-limited discounts" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:64 -msgid "To activate time-limited discounts, you must activate the *Pricelists* feature. To do so, go to :menuselection:`Point of Sales --> Configuration --> Point of Sale` and open your PoS. Then, enable the pricelist feature." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:None -msgid "View of the pricelist feature" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:73 -msgid "Once activated, you must choose the pricelists you want to make available in the PoS and define a default one." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:77 -msgid "Create a pricelist" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:79 -msgid "By default, Odoo has a *Public Pricelist* configured. To create more, go to :menuselection:`Point of Sale --> Products --> Pricelists`. Then click on create." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:83 -msgid "When creating a pricelist, you can set several criteria to use a specific price: period, min. quantity, etc. You can also decide to apply that pricelist on specific products or on the whole range." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:None -msgid "View of a time-limited pricelist for two products" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:92 -msgid "Using a pricelist with the PoS interface" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:94 -msgid "On the PoS interface, a new button appears. Use it to select a pricelist." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:None -msgid "View of the button to use for time-limited discounts via the pos interface" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:101 -msgid "Click on it to instantly update the prices with the selected pricelist. Then, you can finalize the order." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:3 -msgid "Manage a loyalty program" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:5 -msgid "Encourage your customers to continue to shop at your point of sale with a *Loyalty Program*." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:11 -msgid "To activate the *Loyalty Program* feature, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface. Under the Pricing features, select *Loyalty Program*" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:19 -msgid "From there you can create and edit your loyalty programs." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:24 -msgid "You can decide what type of program you wish to use, if the reward is a discount or a gift, make it specific to some products or cover your whole range. Apply rules so that it is only valid in specific situation and everything in between." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:30 -msgid "Use the loyalty program in your PoS interface" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:32 -msgid "When a customer is set, you will now see the points they will get for the transaction and they will accumulate until they are spent. They are spent using the button *Rewards* when they have enough points according to the rules defined in the loyalty program." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:40 -msgid "You can see the price is instantly updated to reflect the pricelist. You can finalize the order in your usual way." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:44 -msgid "If you select a customer with a default pricelist, it will be applied. You can of course change it." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:3 -msgid "Using Pricelists in Point of Sale" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:5 -msgid "You probably know the concept of happy hour: during a certain period of time, the barman gives a discount on some drinks (usually 50% off or a buy one get one free). When the period is over, prices go back to normal. But how does that relate with Odoo?" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:10 -msgid "In Odoo, you can set up happy hours. It’s one of the many possible uses of *Pricelists*. Those *Pricelists* allow the creation of multiple prices for the same product: a regular one and a special one for happy hours. Available in the *PoS* app, those are really convenient." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:17 -msgid "Set up Pricelists" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:19 -msgid "To set up a *Pricelist*, go to :menuselection:`Point of Sale --> Configuration --> Configuration` and enable the *Pricelist* feature. Then, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and enable *Pricelist* for the *PoS*." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:26 -msgid "Now, you can create *Pricelists* by clicking on the *Pricelists* link. Then, set it up by choosing the product category you want to include in your happy hour and the discount." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:33 -msgid "Go back to your *PoS* settings and add the Happy Hour pricelist to the list. You can even choose a default pricelist if needed." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:39 -msgid "From now on, on the *PoS* interface, a new button is available, allowing you to choose among the different *pricelists* you added before." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:46 -msgid ":doc:`../../sales/products_prices/prices/pricing`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm.rst:5 -msgid "Fiscal Data Modules" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:3 -msgid "Setting up the Fiscal Data Module with the Odoo POS" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:6 -msgid "Introduction" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:8 -msgid "The Belgian government requires certain businesses to use a government-certified device called a **Fiscal Data Module** (also known as a **blackbox**). This device works together with the POS application and logs certain transactions. On top of that, the used POS application must also be certified by the government and must adhere to strict standards specified by them. `Odoo 9 (Enterprise Edition) is a certified application `_. More information concerning the Fiscal Data Module can be found on `the official website `_." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:20 -msgid "Required hardware" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:22 -msgid "A government certified `Fiscal Data Module `_ per POS, all of them should work, but the Cleancash SC-B is recommended, you will also need:" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:27 -msgid "Serial null modem cable per FDM (`example `__)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:29 -msgid "Serial-to-USB adapter per FDM (`example `__)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:32 -msgid "A registered IoT Box per POS configuration" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:35 -msgid "Setup" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:38 -msgid "IoT Box" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:40 -msgid "In order to use a Fiscal Data Module, you will need a registered IoT Box. These IoT Boxes are similar to the regular IoT Boxes we sell, but they are registered with the Belgian government. This is required by law. Attempting to use a Fiscal Data Module on a non-registered IoT Box will not work. You can verify that the Fiscal Data Module is recognized by the IoT Box by going to the *Hardware status page* via the IoT Box homepage." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:52 -msgid "Odoo" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:54 -msgid "An Odoo POS app can be given certified POS capabilities by installing the **Belgian Registered Cash Register** app (technical name: ``pos_blackbox_be``). Because of government restrictions imposed on us, this installation cannot be undone. After this, you will have to ensure that each POS configuration has a unique registered IoT Box associated with it (:menuselection:`Point of Sale --> Configuration --> Point of Sale` and ensure Hardware Proxy / IoT Box and the serial number of your IoT Box is set). The first time you open the Point of Sale and attempt to do a transaction, you will be asked to input the PIN that you received with your VAT signing card." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:69 -msgid "Certification & On-premise" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:71 -msgid "The certification granted by the government is restricted to the use on odoo.com Odoo Online instance. The usage of the module from the source or a modified version will **not** be certified. For on-premise users, we also support the Fiscal Data Module in such installations. The main restriction is that this requires an obfuscated version of the ``pos_blackbox_be`` module we will provide on request for Enterprise customers." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:79 -msgid "Restrictions" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:81 -msgid "As mentioned before, in order to get certified the POS application must adhere to strict government guidelines. Because of this, a certified Odoo POS has some limitations not present in the non-certified Odoo POS." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:86 -msgid "Refunding is disabled" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:87 -msgid "Modifying orderline prices" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:88 -msgid "Creating/modifying/deleting POS orders" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:89 -msgid "Selling products without a valid tax" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:90 -msgid "Multiple Odoo POS configurations per IoT Box are not allowed" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:91 -msgid "Using the POS without a connection to the IoT Box (and thus FDM)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:92 -msgid "Blacklisted modules: pos_discount, pos_reprint, pos_loyalty" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview.rst:5 -msgid "Overview" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:3 -msgid "Self-signed certificate for ePOS printers" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:5 -msgid "ePos printers are designed specifically to work with your Point of Sale system, which sends the tickets directly to the printer." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:8 -msgid "Some models don't require an IoT box, but the connection between your web browser and the printer may require a :doc:`secure connection with the HTTPS protocol `. If so, a self-signed certificate is necessary to use your printer." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:13 -msgid "Please check the following list of compatible `Epson ePOS printers `_. This list includes the following models:" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:17 -msgid "TM-H6000IV-DT (Receipt printer only)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:18 -msgid "TM-T70II-DT" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:19 -msgid "TM-T88V-DT" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:20 -msgid "TM-L90-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:21 -msgid "TM-T20II-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:22 -msgid "TM-T70-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:23 -msgid "TM-T82II-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:24 -msgid "TM-T83II-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:25 -msgid "TM-T88V-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:26 -msgid "TM-U220-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:27 -msgid "TM-m10" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:28 -msgid "TM-m30" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:29 -msgid "TM-P20 (Wi-Fi® model)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:30 -msgid "TM-P60II (Receipt: Wi-Fi® model)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:31 -msgid "TM-P60II (Peeler: Wi-Fi® model)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:32 -msgid "TM-P80 (Wi-Fi® model)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:35 -msgid "Generate a Self-signed certificate" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:37 -msgid "Access your ePOS printer's settings with your web browser by navigating to its IP address, for example, `http://192.168.1.25`." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:41 -msgid "The printer automatically prints the IP address during startup." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:42 -msgid "We recommend assigning a **fixed IP address** to the printer from the network router." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:44 -msgid "Go to :menuselection:`Authentication --> Certificate List` and create a new **Self-Signed Certificate**." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:47 -msgid "**Common Name**: the IP address of the ePos Printer, for example, `192.168.1.25`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:48 -msgid "**Validity Period**: `10`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:50 -msgid "Create and reboot the printer, go to :menuselection:`Security --> SSL/TLS`, and check if **Selfsigned Certificate** is selected." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:54 -msgid "Export the Self-signed certificate" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:56 -msgid "To avoid having to accept the self-signed certificate several times, you can export it and then import it to your web browser or mobile device." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:59 -msgid "To do so, access your ePOS printer's settings with your web browser by navigating to its IP address, for example, `https://192.168.1.25`. Then, accept the self-signed certificate." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:63 -msgid "Note that the protocol is now **HTTPS**." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:65 -msgid "Click on :menuselection:`Connection is not secure --> Certificate is not valid`." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:None -msgid "The web browser indicates that the connection to the printer is not secure." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:71 -msgid "Go to the :guilabel:`Details` tab and click on :guilabel:`Export` Select X.509 in base 64 and save it." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:74 -msgid "Import the Self-signed certificate to Windows (Using Chrome)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:76 -msgid "In your Chrome browser, go to :menuselection:`Settings --> Privacy and security --> Security --> Manage certificates`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:79 -msgid "Go to the :guilabel:`Authorities` tab and click on :guilabel:`Import` and select your previous file. Accept all warnings and restart your browser." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:83 -msgid "Import the Self-signed certificate to your Android device" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/epos_ssc.rst:85 -msgid "On your Android device, open the settings and search for *certificate*. Then, click on **Certificate AC** (Install from device storage), and select the certificate." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:3 -msgid "Getting started" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:5 -msgid "**Point of Sale** is a fully integrated application that allows you to sell products (online or offline) with any device. It also automatically registers product moves in your stock, gives you real-time statistics, and consolidations across all shops." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:13 -msgid "Make products available" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:15 -msgid "To make products available for sale, go to :menuselection:`Point of Sale --> Products --> Products`, and open a product. In the :guilabel:`Point of Sale` tab, enable :guilabel:`Available in POS`." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None -msgid "Making a product available in your POS." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:23 -msgid "Configure payment methods" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:25 -msgid "To add a payment method, you first need to create it. Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods --> Create`. Set a name and select the **payment terminal** or check :guilabel:`Cash` for cash payments." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None -msgid "Creating a new payment method for a POS." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:34 -msgid "Credentials are mandatory to use a payment terminal. To learn how to configure the different terminals, check out the following documentation pages:." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:37 -msgid ":doc:`Adyen configuration <../payment/adyen>`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:38 -msgid ":doc:`Vantiv configuration <../payment/vantiv>`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:39 -msgid ":doc:`Ingenico configuration <../payment/ingenico>`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:40 -msgid ":doc:`Six configuration <../payment/six>`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:42 -msgid "Now, you can select the payment method in your POS settings. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select a POS for which you wish to make the payment method available. Click :guilabel:`Edit` and add the payment method under the :guilabel:`Payments` section." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:49 -msgid "POS sessions" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:52 +#: ../../content/applications/sales/point_of_sale.rst:19 #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:31 msgid "Start a session" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:54 +#: ../../content/applications/sales/point_of_sale.rst:21 msgid "From the **POS dashboard**, click :guilabel:`New Session` to start a POS session, or :guilabel:`Resume` if the session was already open." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:58 -msgid "Multiple users can be connected to the same session at the same time. However, the session can only be open once on the same browser." +#: ../../content/applications/sales/point_of_sale.rst:25 +msgid ":doc:`Multiple users ` can be logged into the same session at the same time. However, the session can only be opened once on the same browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:61 +#: ../../content/applications/sales/point_of_sale.rst:31 +msgid "Sell products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:33 msgid "Click on products to add them to the cart. To change the **quantity**, click :guilabel:`Qty` and enter the number of products using the keypad. To add a **discount** or modify the product **price**, click respectively :guilabel:`Disc` or :guilabel:`Price` and enter the amounts." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:65 +#: ../../content/applications/sales/point_of_sale.rst:37 msgid "Once an order is completed, proceed to checkout by clicking :guilabel:`Payment`. Select the **payment method**, enter the received amount, and click :guilabel:`Validate`. Click :guilabel:`New Order` to move on to the next customer." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +#: ../../content/applications/sales/point_of_sale.rst:-1 msgid "POS session interface." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:74 +#: ../../content/applications/sales/point_of_sale.rst:46 msgid "You can use both `,` and `.` on your keyboard as decimal separators." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:75 +#: ../../content/applications/sales/point_of_sale.rst:47 msgid "**Cash** is selected by default if you enter the amount without choosing a payment method." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:79 +#: ../../content/applications/sales/point_of_sale.rst:52 +msgid "Set customers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:54 +msgid "You can create and set customers from an :ref:`open POS session `. Registering your customer is necessary to :doc:`collect their loyalty points and grant them rewards `, automatically apply the :doc:`attributed pricelist `, or :ref:`generate and print an invoice `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:60 +msgid "To access the list of customers, click :guilabel:`Customer` on the POS interface. Then, select a customer or create a new one by clicking :guilabel:`Create`, completing the form, and saving. Lastly, click :guilabel:`Set Customer` to set the selected customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:67 msgid "Return and refund products" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:81 +#: ../../content/applications/sales/point_of_sale.rst:69 msgid "To return a product and make a refund," msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:83 +#: ../../content/applications/sales/point_of_sale.rst:71 msgid "from the **POS dashboard**, **open a session** and select the returned product;" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:84 +#: ../../content/applications/sales/point_of_sale.rst:72 msgid "click :guilabel:`Qty` and :guilabel:`+/-` to enter the quantity of returned products;" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:85 +#: ../../content/applications/sales/point_of_sale.rst:73 msgid "once the order is completed, click :guilabel:`Payment` to proceed to the refund;" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:86 +#: ../../content/applications/sales/point_of_sale.rst:74 msgid "click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next customer." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:89 +#: ../../content/applications/sales/point_of_sale.rst:79 msgid "Close the POS session" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:91 +#: ../../content/applications/sales/point_of_sale.rst:81 msgid "To close your session," msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:93 +#: ../../content/applications/sales/point_of_sale.rst:83 msgid "go back to the POS dashboard by clicking :guilabel:`Close` and :guilabel:`Confirm` in the upper right corner of your screen;" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:95 +#: ../../content/applications/sales/point_of_sale.rst:85 msgid "then, click :guilabel:`Close` and proceed to the **closing control**;" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:96 +#: ../../content/applications/sales/point_of_sale.rst:86 msgid "click the :guilabel:`Payments` smart button to know what amount of cash should be in your cash drawer;" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:98 +#: ../../content/applications/sales/point_of_sale.rst:88 msgid "once the control is done, click :guilabel:`Close session & post entries`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:99 +#: ../../content/applications/sales/point_of_sale.rst:89 msgid "the status goes automatically from :guilabel:`In Progress` to :guilabel:`Closed & Posted`." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +#: ../../content/applications/sales/point_of_sale.rst:-1 msgid "How to close a POS session." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:106 +#: ../../content/applications/sales/point_of_sale.rst:96 msgid "It is strongly advised to close your POS session at the end of each day." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:107 +#: ../../content/applications/sales/point_of_sale.rst:97 msgid "To look at all your previous sessions, go to :menuselection:`Point of Sale --> Orders --> Sessions`." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:111 -msgid "View statistics" +#: ../../content/applications/sales/point_of_sale/configuration.rst:11 +msgid "Access POS settings" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:113 -msgid "To access your statistics, go to :menuselection:`Point of Sale --> Reporting --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis (:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`." +#: ../../content/applications/sales/point_of_sale/configuration.rst:13 +msgid "To access the general POS settings, go to :menuselection:`Point of Sale --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:117 -msgid "These statistics are available in graph or pivot view that you can filter or group depending on your needs." +#: ../../content/applications/sales/point_of_sale/configuration.rst:16 +msgid "To access the settings of a specific point of sale, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Alternatively, from the Point of Sale dashboard, click the vertical ellipsis (:guilabel:`⋮`) button on a POS card, then on :guilabel:`Settings`." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/https.rst:3 +#: ../../content/applications/sales/point_of_sale/configuration.rst:21 +msgid "Make products available" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:23 +msgid "To make products available for sale, go to :menuselection:`Point of Sale --> Products --> Products`, and open a product. In the :guilabel:`Point of Sale` tab, enable :guilabel:`Available in POS`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:-1 +msgid "Making a product available in your POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:5 +msgid "Self-signed certificate for ePOS printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:7 +msgid "ePOS printers are designed to work seamlessly with Point of Sale systems. Once connected, the two devices automatically share information, enabling the direct printing of tickets from the POS system to the ePOS printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:12 +msgid "These `Epson ePOS printers `_ are compatible with Odoo:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:15 +msgid "TM-H6000IV-DT (Receipt printer only)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:16 +msgid "TM-T70II-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:17 +msgid "TM-T88V-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:18 +msgid "TM-L90-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:19 +msgid "TM-T20II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:20 +msgid "TM-T70-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:21 +msgid "TM-T82II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22 +msgid "TM-T83II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:23 +msgid "TM-T88V-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24 +msgid "TM-U220-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:25 +msgid "TM-m10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:26 +msgid "TM-m30" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:27 +msgid "TM-P20 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28 +msgid "TM-P60II (Receipt: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:29 +msgid "TM-P60II (Peeler: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:30 +msgid "TM-P80 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:32 +msgid "To work with Odoo, some models that can be used without an :doc:`IoT box <../../../productivity/iot/config/connect>` may require :doc:`the HTTPS protocol ` to establish a secure connection between the browser and the printer. However, trying to reach the printer's IP address using HTTPS leads to a warning page on most web browsers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:41 +msgid "warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:41 +msgid "Warning page on Google Chrome, Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:43 +msgid "In that case, you can temporarily force the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to [IP address] (unsafe)`. Doing so allows you to reach the page in HTTPS and use the ePOS printer in Odoo as long as the browser window stays open." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:48 +msgid "The previous instructions apply to Google Chrome but are similar to other browsers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:51 +msgid "The connection is lost after closing the browser window. Therefore, this method should only be used as a **workaround** or as a pre-requisite for the :ref:`following instructions `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 +msgid "Generate, export, and import self-signed certificates" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:60 +msgid "For a long-term solution, you must generate a **self-signed certificate**. Then, export and import it into your browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +msgid "**Generating** an SSL certificate should only be done **once**. If you create another certificate, devices using the previous one will lose HTTPS access." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:69 +msgid "Windows 10 & Linux OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:73 +msgid "Generate a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:75 +msgid "After forcing the connection, sign in using your printer credentials to access the ePOS printer settings. To sign in, enter `epson` in the :guilabel:`ID` field and your printer serial number in the :guilabel:`Password` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:79 +msgid "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` section, and click :guilabel:`create` to generate a new **Self-Signed Certificate**. The :guilabel:`Common Name` should be automatically filled out. If not, fill it in with the printer IP address number. Select the years the certificate will be valid in the :guilabel:`Validity Period` field, click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:86 +msgid "The self-signed certificate is generated. Reload the page and click :guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure **Selfsigned Certificate** is correctly selected in the :guilabel:`Server Certificate` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:90 +msgid "Export a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:92 +msgid "The export process is heavily dependent on the :abbr:`OS (Operating System)` and the browser. Start by accessing your ePOS printer settings on your web browser by navigating to its IP address, for example, `https://192.168.1.25`. Then, force the connection as explained in the :ref:`introduction `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:97 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:160 +msgid "If you are using **Google Chrome**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:99 +msgid "click :guilabel:`Not secure` next to the search bar, and :guilabel:`Certificate is not valid`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection to the printer not secure button in Google Chrome browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 +msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:107 +msgid "add `.crt` at the end of the file name to ensure it has the correct extension;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +msgid "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom of the pop-up window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:110 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:128 +msgid "save, and the certificate is exported." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:113 +msgid "Make sure that the certificate ends with the extension `.crt`. Otherwise, some browsers might not see the file during the import process." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:172 +msgid "If you are using **Mozilla Firefox**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:118 +msgid "click the **lock-shaped** icon on the left of the address bar;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:119 +msgid "go to :menuselection:`Connection not secure --> More information --> Security tab --> View certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection is not secure button in Mozilla Firefox browser" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:126 +msgid "scroll down to the :guilabel:`Miscellaneous` section;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 +msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:130 +msgid "Import a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:132 +msgid "The import process is heavily dependent on the :abbr:`OS (Operating System)` and the browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:137 +msgid "Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 +msgid "Windows 10 manages certificates, which means that self-signed certificates must be imported from the certification file rather than the browser. To do so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 +msgid "open the Windows File Explorer and locate the downloaded certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:143 +msgid "right-click on the certification file and click :guilabel:`Install Certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 +msgid "select where to install the certificate and for whom - either for the :guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, click :guilabel:`Next`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:148 +msgid "on the `Certificate Store` screen, tick :guilabel:`Place all certificates in the following store`, click :guilabel:`Browse...`, and select :guilabel:`Trusted Root Certification Authorities`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:155 +msgid "click :guilabel:`Finish`, accept the pop-up security window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 +msgid "restart the computer to make sure that the changes are applied." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 +msgid "Linux" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:162 +msgid "open Chrome;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 +msgid "go to :menuselection:`Settings --> Privacy and security --> Security --> Manage certificates`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +msgid "go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select the exported certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:167 +msgid "accept all warnings;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 +msgid "click :guilabel:`ok`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:169 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 +msgid "restart your browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 +msgid "open Firefox;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 +msgid "go to :menuselection:`Settings --> Privacy & Security --> Security --> View Certificates... --> Import`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 +msgid "select the exported certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:178 +msgid "tick the checkboxes and validate;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 +msgid "Mac OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:183 +msgid "To secure the connection on a Mac:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:185 +msgid "open Safari and navigate to your printer's IP address. Doing so leads to a warning page;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +msgid "on the warning page, go to :menuselection:`Show Details --> visit this website --> Visit Website`, validate;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 +msgid "reboot the printer so you can use it with any other browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:190 +msgid "Android OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 +msgid "To import an SSL certificate into an Android device, first create and export it from a computer. Next, transfer the `.crt` file to the device using email, Bluetooth, or USB. Once the file is on the device," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:196 +msgid "open the settings and search for `certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 +msgid "click :guilabel:`Certificate AC` (Install from device storage);" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:198 +msgid "select the certificate file to install it on the device." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 +msgid "The specific steps for installing a certificate may vary depending on the version of Android and the device manufacturer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:206 +msgid "If you need to export SSL certificates from an operating system or web browser that has not been mentioned, search for `export SSL certificate` + `the name of your browser or operating system` in your preferred search engine." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:209 +msgid "Similarly, to import SSL certificates from an unmentioned OS or browser, search for `import SSL certificate root authority` + `the name of your browser or operating system` in your preferred search engine." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 +msgid "Check if the certificate was imported correctly" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:216 +msgid "To confirm your printer's connection is secure, connect to its IP address using HTTPS. For example, navigate to `https://192.168.1.25` in your browser. If the SSL certificate has been applied correctly, you should no longer see a warning page, and the address bar should display a padlock icon, indicating that the connection is secure." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:3 msgid "Secure connection (HTTPS)" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/https.rst:5 +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:5 msgid "If **Direct Devices** is enabled in a Point of Sale settings (for example, if you use an ePos printer), HTTP becomes the default protocol." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/https.rst:9 +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:9 msgid "Force your Point of Sale to use a secure connection (HTTPS)" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/https.rst:11 +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:11 msgid "Add a new **key** in the **System Parameters** to force your Point of Sale to use a secure connection with the HTTPS protocol." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/https.rst:14 +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:14 msgid "To do so, activate the :ref:`developer mode `, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters`, then create a new parameter, add the following values and click on *Save*." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/https.rst:18 +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:18 msgid "**Key**: `point_of_sale.enforce_https`" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/https.rst:19 +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:19 msgid "**Value**: `True`" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/https.rst:22 +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:22 msgid ":doc:`epos_ssc`" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/register.rst:3 -msgid "Register customers" +#: ../../content/applications/sales/point_of_sale/employee_login.rst:3 +msgid "Log in with employee" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/register.rst:5 -msgid "Registering your customers will give you the ability to grant them various privileges such as discounts, loyalty program, specific communication. It will also be required if they want an invoice and registering them will make any future interaction with them faster." +#: ../../content/applications/sales/point_of_sale/employee_login.rst:5 +msgid "With Odoo *Point of Sale*, you can manage multiple cashiers. This feature allows you to keep track of who is working, when and how much each cashier made for that session." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/register.rst:11 -msgid "Create a customer" +#: ../../content/applications/sales/point_of_sale/employee_login.rst:9 +msgid "There are three ways to switch cashiers in Odoo: by *selecting the cashier*, by *entering a PIN code* or by *scanning a barcode*." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/register.rst:13 -msgid "From your session interface, use the customer button." +#: ../../content/applications/sales/point_of_sale/employee_login.rst:13 +msgid "To manage multiple cashiers, you need several employees (at least two)." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/register.rst:18 -msgid "Create a new one by using this button." +#: ../../content/applications/sales/point_of_sale/employee_login.rst:18 +msgid "Set up log in with employees" msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/register.rst:23 -msgid "You will be invited to fill out the customer form with their information." +#: ../../content/applications/sales/point_of_sale/employee_login.rst:20 +msgid "To enable the feature, go to your *PoS settings* and check log in with employees on your *PoS form*. Then, add the employees that have access to the cash register." msgstr "" -#: ../../content/applications/sales/point_of_sale/overview/register.rst:29 -msgid "Use the save button when you are done. You can then select that customer in any future transactions." +#: ../../content/applications/sales/point_of_sale/employee_login.rst:27 +msgid "Now, you can switch cashier easily." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment.rst:5 -msgid "Payment Terminals" +#: ../../content/applications/sales/point_of_sale/employee_login.rst:30 +msgid "Switch without pin codes" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:3 +#: ../../content/applications/sales/point_of_sale/employee_login.rst:32 +msgid "The easiest way to switch cashiers is without a code. To do so, click on the cashier name in your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:38 +msgid "Now, you just have to click on your name." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:46 +msgid "Switch cashier with pin codes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:48 +msgid "You can set a pin code on each cashier. To set up a pin code, go to the employee form and add a security PIN, in the *HR settings tab*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:54 +msgid "Now, when switching cashier, a PIN password will be asked." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:62 +msgid "Switch cashier with barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:64 +msgid "You can ask your employees to log themselves with their badges. To do so, set up a barcode at the same place you add the PIN code. Print the badge and when they will scan it, the cashier will be switched to that employee." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:73 +msgid "Find who was the cashier" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:75 +msgid "Once you have closed your *PoS session*, you can have an overview of the amount each cashier sold for. To do so, go to the orders menu." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:81 +msgid "Now, you can open the order and have a summary of the sold products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:5 +msgid "Payment methods" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:7 +msgid "To add a payment method, you first need to create it. Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods --> Create`. Set a name and select a :doc:`payment terminal ` for card payments or check :guilabel:`Cash` for cash payments." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:-1 +msgid "Creating a new payment method for a POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:15 +msgid ":doc:`payment_methods/terminals`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:17 +msgid "Now, you can select the payment method in your POS settings. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select a POS for which you wish to make the payment method available. Click :guilabel:`Edit` and add the payment method under the :guilabel:`Payments` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:5 +msgid "Payment terminals" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:7 +msgid "Connecting and integrating a payment terminal with your POS system allows you to accept multiple payment options, including credit and debit cards, making the payment process more efficient." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 +msgid "Go to the :doc:`application settings <../configuration>`, scroll down to the :guilabel:`Payment Terminals` section, and tick your terminal's checkbox." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:-1 +msgid "checkbox in the settings to enable a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:19 +msgid "Then, follow the corresponding documentation to configure your device:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21 +msgid ":doc:`Adyen configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22 +msgid ":doc:`Ingenico configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23 +msgid ":doc:`SIX configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24 +msgid ":doc:`Vantiv configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26 +msgid "Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to the POS <../payment_methods>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3 msgid "Adyen" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:5 msgid "Connecting an **Adyen payment terminal** allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:11 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:9 +msgid "Adyen works only with businesses processing **more** than **10 million annually** or invoicing a **minimum** of **1,000** transactions **per month**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:15 msgid "Start by creating your Adyen account on `Adyen's website `_. Then, board your terminal following the steps described on your terminal's screen." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:19 msgid "`Adyen Docs - Payment terminal quickstart guides `_." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:19 -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:36 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:23 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:36 msgid "Configure the payment method" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:21 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:25 msgid "First, go to :menuselection:`Point of Sale --> Configuration --> Settings --> Payment Terminals`, and enable :guilabel:`Adyen`. Then, go to :menuselection:`Configuration --> Payment Methods` and create a new payment method. Select :guilabel:`Adyen` in the :guilabel:`Use a Payment Terminal` field." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:27 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:31 msgid "The selected journal **must** be a bank journal for the :guilabel:`Use a payment terminal` field to appear." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:30 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:34 msgid "Finally, fill the mandatory fields with an :guilabel:`Adyen API key`, and an :guilabel:`Adyen Terminal Identifier`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:34 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:38 msgid "Generate an Adyen API key" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:36 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40 msgid "The **Adyen API key** is a key used to authenticate your requests. To generate an API key, go to your **Adyen account**." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:39 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:43 msgid "Then, go to :menuselection:`Developers --> API credentials`. Create a new credential or click on an existing one." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:42 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:46 msgid "Click on :guilabel:`Generate an API key` and copy-paste that key onto the Odoo mandatory field." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:45 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:49 msgid "`Adyen Docs - API credentials `_." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:49 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:53 msgid "Locate the Adyen terminal identifier" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:51 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:55 msgid "The **Adyen Terminal Identifier** is your terminal's serial number, which is used to identify the hardware." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:54 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:58 msgid "To find this number, go to your **Adyen account**. Then, go to :menuselection:`Point of Sale --> Terminals`, select the terminal to link, and copy-paste its serial number onto the Odoo mandatory field." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:59 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:63 msgid "Set the Event URLs" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:61 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:65 msgid "For Odoo to know when a payment is made, you must set the terminal **Event URLs**. To do so," msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:63 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:67 msgid "log in to `Adyen's website `_;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:64 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:68 msgid "go to :menuselection:`Adyen's dashboard --> Point of Sale --> Terminals` and select the connected terminal;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:66 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:70 msgid "from the terminal settings, click :guilabel:`Integrations`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:67 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:71 msgid "set the :guilabel:`Switch to decrypted mode to edit this setting` field as :guilabel:`Decrypted`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:68 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:72 msgid "click the **pencil icon** button and enter your server address, followed by `/pos_adyen/notification` in the :guilabel:`Event URLs` field; and" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:70 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:74 msgid "click :guilabel:`Save` at the bottom of the screen to save the changes." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:73 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:77 msgid "Add a new payment method" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:75 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:79 msgid "To add a new **payment method** to a point of sale, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, select the POS and go to :menuselection:`Payments --> Payment Methods`, and add your new method for Adyen." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:80 -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:53 msgid "Pay with a payment terminal" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:82 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:86 msgid "When processing a payment, select :guilabel:`Adyen` as the payment method. Check the amount and click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:0 -msgid "In case of connexion issues between Odoo and the payment terminal, force the payment by clicking on :guilabel:`Force Done`, which allows you to validate the order." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 +msgid "In case of connection issues between Odoo and the payment terminal, force the payment by clicking on :guilabel:`Force Done`, which allows you to validate the order." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:0 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 msgid "This option is only available after receiving an error message informing you that the connection failed." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:91 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:95 msgid "To cancel the payment request, click on :guilabel:`cancel`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:3 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:3 msgid "Ingenico" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:5 msgid "Connecting a payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:8 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:8 msgid "Please note that Ingenico is currently only available for customers in the Benelux." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 msgid "Connect an IoT Box" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:17 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:17 msgid "Connecting an Ingenico Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to the :doc:`IoT documentation `." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:22 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:22 msgid "Configure the Lane/5000 for Ingenico BENELUX" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:24 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:24 msgid "Click on the F button of the terminal, then go in the :menuselection:`PoS Menu --> Settings` and enter the settings password." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:27 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27 msgid "Now, click on connection change and TCP/IP. Type the IP of your *IoT Box* (you can find it on the form view of your IoT Box). Then, enter 9000 as port. The terminal will restart. Once it is done, go on your *IoT Box* form in Odoo and verify that the terminal has been found." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:38 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:38 msgid "First, go in the general settings of the POS app, and activate the Ingenico setting." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:44 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:44 msgid "Go 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 Ingenico, select the payment terminal option Ingenico, and select your payment terminal device." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:55 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55 msgid "In your *PoS interface*, when processing a payment, select a *Payment Method* using a payment terminal. Check that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. When the payment is successful, the status will change to *Payment Successful*." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:64 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:64 msgid "If you want to cancel the payment request, click on cancel. You can still retry to send the payment request." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:67 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:67 msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connection between the terminal and Odoo has issues." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:73 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:73 msgid "This option will only be available if you received an error message telling you the connection failed." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:76 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:76 msgid "Once your payment is processed, on the payment record, you’ll find the type of card that has been used and the transaction ID." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:3 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:3 msgid "SIX" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:5 msgid "Connecting a SIX payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:9 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9 msgid "Starting in July 2022, it will **not** be possible anymore to connect and use a Six payment terminal in PoS." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:11 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:11 msgid "Even though Worldline has recently acquired SIX Payment Services and both companies use Yomani payment terminals, the firmware they run is different. Terminals received from Worldline are therefore not compatible with this integration." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:19 -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:16 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:16 msgid "Configure the Payment Method" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:21 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:21 msgid "First, make sure that the :guilabel:`POS Six` module is installed. For this, go to :guilabel:`Apps`, remove the :guilabel:`Apps` filter, and search for *POS Six*." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:None +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 msgid "The POS Six module." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:28 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:28 msgid "Back in :menuselection:`Point of Sale --> Configuration --> Payment Methods`, create a new payment method for SIX, select the payment terminal option :guilabel:`SIX`, and enter the payment terminal IP address." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:None +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 msgid "Create a new payment method for the SIX payment terminal." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:37 -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:40 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:37 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:40 msgid "Pay with a Payment Terminal" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:39 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:39 msgid "In the :abbr:`PoS (Point of Sale)` interface, at the moment of the payment, select a payment method using a payment terminal. Verify that the amount in the tendered column is the one that has to be sent to the payment terminal and click on :guilabel:`Send`. To cancel the payment request, click on :guilabel:`Cancel`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:None +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 msgid "The PoS interface." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:48 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:48 msgid "When the payment is done, the status will change to :guilabel:`Payment Successful`. If needed, reverse the last transaction by clicking on :guilabel:`Reverse`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:None +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 msgid "The Reverse button on the PoS interface." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/six.rst:55 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55 msgid "If there is any issue with the payment terminal, you can still force the payment using the :guilabel:`Force Done` button. This will allow you to validate the order in Odoo even if there are connection issues between the payment terminal and Odoo." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:3 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:3 msgid "Vantiv" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:5 msgid "Connecting a Vantiv payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:9 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:9 msgid "Please note MercuryPay only operates with US and Canadian banks, making this procedure only suitable for North American businesses." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:18 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:18 msgid "First, go in the general settings of the POS app, and activate the Vantiv setting." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:24 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:24 msgid "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." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:32 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:32 msgid "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." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:42 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:42 msgid "In your PoS interface, at the moment of the payment, select your Vantiv payment method and… that’s all." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant.rst:5 -msgid "Restaurant Features" +#: ../../content/applications/sales/point_of_sale/pricing.rst:5 +msgid "Pricing features" msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 -msgid "Print the Bill" +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:3 +msgid "Cash rounding" msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:5 -msgid "Use the *Bill Printing* feature to print the bill before the payment. This is useful if the bill is still subject to evolve and is thus not the definitive ticket." +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:5 +msgid "**Cash rounding** is required when the lowest physical denomination of currency, or the smallest coin, is higher than the minimum unit of account." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 -msgid "Configure Bill Printing" +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:9 +msgid "For example, some countries require their companies to round up or down the total amount of an invoice to the nearest five cents, when the payment is made in cash." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12 -msgid "To activate *Bill Printing*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface." +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:13 +msgid "Each point of sale in Odoo can be configured to apply cash rounding to the totals of its bills or receipts." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:15 -msgid "Under the Bills & Receipts category, you will find *Bill Printing* option." +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:19 +msgid "Go to :menuselection:`Point of Sale --> Configuration --> Settings` and enable *Cash Rounding*, then click on *Save*." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:22 -msgid "Split a Bill" +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:25 +msgid "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the point of sale you want to configure, and enable the *Cash Rounding* option." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:24 -msgid "On your PoS interface, you now have a *Bill* button." +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:29 +msgid "To define the **Rounding Method**, open the drop-down list and click on *Create and Edit...*." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:29 -msgid "When you use it, you can then print the bill." +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:32 +msgid "Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*, then save both the Rounding Method and your Point of Sale settings." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:3 -msgid "Using fiscal positions in PoS" +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:39 +msgid "All total amounts of this point of sale now add a line to apply the rounding according to your settings." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:5 +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:46 +msgid "Odoo Point of Sale only supports the :guilabel:`Add a rounding line` rounding strategy." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:3 +msgid "Discount tags (barcode scanner)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:5 +msgid "If you want to sell your products with a discount, for a product getting close to its expiration date for example, you can use discount tags. They allow you to scan discount barcodes." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:10 +msgid "To use discount tags you will need to use a barcode scanner." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:13 +msgid "Barcode Nomenclature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:15 +msgid "To use discounts tags, we need to learn about barcode nomenclature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:17 +msgid "Let's say you want to have a discount for the product with the following barcode:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:23 +msgid "You can find the *Default Nomenclature* under the settings of your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:32 +msgid "Let's say you want 50% discount on a product you have to start your barcode with 22 (for the discount barcode nomenclature) and then 50 (for the %) before adding the product barcode. In our example, the barcode would be:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:41 +msgid "Scan the products & tags" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:43 +msgid "You first have to scan the desired product (in our case, a lemon)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:48 +msgid "And then scan the discount tag. The discount will be applied and you can finish the transaction." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:3 +msgid "Discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:5 +msgid "By offering discounts, you can entice your customers and drastically increase your revenue. It is vital to offer discounts, whether they are time-limited, seasonal or manually given." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:9 +msgid "To manage discounts, Odoo has powerful features that help set up a pricing strategy tailored to every business." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:13 +msgid "Apply manual discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:15 +msgid "If you seldom use discounts, applying manual ones might be the easiest solution for your Point of Sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:18 +msgid "You can either apply a discount on the whole order or on specific products inside an order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:22 +msgid "Apply a discount on a product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:24 +msgid "From your PoS session interface, use the *Disc* button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:-1 +msgid "View of the discount button for manual discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:30 +msgid "Then, you can input a discount over the product that is currently selected." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:34 +msgid "Apply a global discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:36 +msgid "To apply a discount on the whole order, go to :menuselection:`Point of Sales --> Configuration --> Point of Sale` and select your PoS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:39 +msgid "Once on your PoS form, select *Global Discounts*, under the *Pricing* category." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:-1 +msgid "View of the feature to enable for global discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:45 +msgid "Now, you have a new *Discount* button appearing on your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:-1 +msgid "View of the button to use for global discount via the pos interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:51 +msgid "Click on it and enter the wanted discount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:-1 +msgid "View of the discount offered in the payment summary" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:58 +msgid "On this example, there is a global discount of 50% as well as a specific 50% discount on oranges." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:62 +msgid "Apply time-limited discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:64 +msgid "To activate time-limited discounts, you must activate the *Pricelists* feature. To do so, go to :menuselection:`Point of Sales --> Configuration --> Point of Sale` and open your PoS. Then, enable the pricelist feature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:-1 +msgid "View of the pricelist feature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:73 +msgid "Once activated, you must choose the pricelists you want to make available in the PoS and define a default one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:77 +msgid "Create a pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:79 +msgid "By default, Odoo has a *Public Pricelist* configured. To create more, go to :menuselection:`Point of Sale --> Products --> Pricelists`. Then click on create." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:83 +msgid "When creating a pricelist, you can set several criteria to use a specific price: period, min. quantity, etc. You can also decide to apply that pricelist on specific products or on the whole range." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:-1 +msgid "View of a time-limited pricelist for two products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:92 +msgid "Using a pricelist with the PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:94 +msgid "On the PoS interface, a new button appears. Use it to select a pricelist." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:-1 +msgid "View of the button to use for time-limited discounts via the pos interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:101 +msgid "Click on it to instantly update the prices with the selected pricelist. Then, you can finalize the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:3 +msgid "Tax rates (fiscal positions)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:5 msgid "In Odoo, *Fiscal Positions* let you apply different taxes based on the customer location. In a *Point of Sale*, such as a restaurant, it can be used to apply different taxes depending if the customer eats in or takes away." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:11 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:11 msgid "Set up fiscal positions for PoS" msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:13 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:13 msgid "To enable this feature, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and check *Fiscal Position per Order*. Now, you can choose the fiscal positions you want for your *PoS*." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:21 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:21 msgid "You need to create your fiscal positions before using this feature." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:24 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:24 msgid "Using fiscal positions" msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:26 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:26 msgid "Once on your *PoS* interface, click on the *Tax* button. Now, choose the fiscal position you need for the current order." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:33 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:33 msgid "Set up a default fiscal position" msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:35 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:35 msgid "If you want to use a default fiscal position, meaning that a preexisting value is always automatically assigned, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and enable *Fiscal Position*. Now, choose one to set as the default one." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:43 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:43 msgid "Now, the *tax* button is replaced by a *on site* button when on the *PoS* interface." msgstr "" +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:3 +msgid "Loyalty programs" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:5 +msgid "Encourage your customers to continue to shop at your point of sale with a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:11 +msgid "To activate the *Loyalty Program* feature, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface. Under the Pricing features, select *Loyalty Program*" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:19 +msgid "From there you can create and edit your loyalty programs." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:24 +msgid "You can decide what type of program you wish to use, if the reward is a discount or a gift, make it specific to some products or cover your whole range. Apply rules so that it is only valid in specific situation and everything in between." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:30 +msgid "Use the loyalty program in your PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:32 +msgid "When a customer is set, you will now see the points they will get for the transaction and they will accumulate until they are spent. They are spent using the button *Rewards* when they have enough points according to the rules defined in the loyalty program." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:40 +msgid "You can see the price is instantly updated to reflect the pricelist. You can finalize the order in your usual way." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:44 +msgid "If you select a customer with a default pricelist, it will be applied. You can of course change it." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:3 +msgid "Pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:5 +msgid "You probably know the concept of happy hour: during a certain period of time, the barman gives a discount on some drinks (usually 50% off or a buy one get one free). When the period is over, prices go back to normal. But how does that relate with Odoo?" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:10 +msgid "In Odoo, you can set up happy hours. It’s one of the many possible uses of *Pricelists*. Those *Pricelists* allow the creation of multiple prices for the same product: a regular one and a special one for happy hours. Available in the *PoS* app, those are really convenient." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:17 +msgid "Set up Pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:19 +msgid "To set up a *Pricelist*, go to :menuselection:`Point of Sale --> Configuration --> Configuration` and enable the *Pricelist* feature. Then, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and enable *Pricelist* for the *PoS*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:26 +msgid "Now, you can create *Pricelists* by clicking on the *Pricelists* link. Then, set it up by choosing the product category you want to include in your happy hour and the discount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:33 +msgid "Go back to your *PoS* settings and add the Happy Hour pricelist to the list. You can even choose a default pricelist if needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:39 +msgid "From now on, on the *PoS* interface, a new button is available, allowing you to choose among the different *pricelists* you added before." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:46 +msgid ":doc:`../../sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:3 +msgid "Receipts and invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:6 +msgid "Reprint receipts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:8 +msgid "Use the *Reprint receipt* feature if you have the need to reprint a ticket." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:13 +msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale`. and select your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:16 +msgid "Under the Bills & Receipts category, you will find *Reprint Receipt* option." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:20 +msgid "In order to allow the option reprint receipt, you need to activate the receipt printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:25 +msgid "Reprint a receipt" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:27 +msgid "On your PoS interface, you now have a *Reprint receipt* button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:31 +msgid "When you use it, you can then reprint your last receipt." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:38 +msgid "Invoice from the PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:40 +msgid "Some of your customers might request an invoice when buying from your Point of Sale, you can easily manage it directly from the PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:44 +msgid "Activate invoicing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46 +msgid "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select your Point of Sale:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:51 +msgid "Under the *Bills & Receipts* you will see the invoicing option, tick it. Don't forget to choose in which journal the invoices should be created." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:58 +msgid "Select a customer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:60 +msgid "From your session interface, use the customer button" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:64 +msgid "You can then either select an existing customer and set it as your customer or create a new one by using this button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:69 +msgid "You will be invited to fill out the customer form with its information." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:72 +msgid "Invoice your customer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:74 +msgid "From the payment screen, you now have an invoice option, use the button to select it and validate." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:79 +msgid "You can then print the invoice and move on to your next order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:82 +msgid "Retrieve invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:84 +msgid "Once out of the PoS interface (:menuselection:`Close --> Confirm` on the top right corner) you will find all your orders in :menuselection:`Point of Sale --> Orders --> Orders` and under the status tab you will see which ones have been invoiced. When clicking on a order you can then access the invoice." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:3 +#: ../../content/applications/sales/subscriptions/reporting.rst:5 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:6 +msgid "View statistics" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:8 +msgid "To access your statistics, go to :menuselection:`Point of Sale --> Reporting --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis (:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:12 +msgid "These statistics are available in graph or pivot view that you can filter or group depending on your needs." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:5 +msgid "Restaurant features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:7 +msgid "Managing a restaurant or a bar comes with specific needs. The Point of Sale application provides various features that allow performing all the required tasks in such businesses." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:10 +msgid "Once the POS is set to be used in a restaurant or a bar, you can:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:12 +msgid ":doc:`organize your floors and tables to reflect your interior `;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:13 +msgid ":ref:`take orders `;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:14 +msgid ":doc:`communicate with the kitchen or the bar through the POS `;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:15 +msgid ":doc:`print bills in advance and split them `;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:16 +msgid ":doc:`collect tips `; and" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:17 +msgid ":doc:`set different taxes for takeaway food `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:22 +msgid "To activate the features, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select your POS, and click :menuselection:`Edit --> Is a Bar/Restaurant --> Save`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:26 +msgid "These specific features can be identified by the cutlery-shaped icon located to the right of the feature name." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 +msgid "Bills" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:5 +msgid "Typical practices in restaurants or bars are to request the bill before proceeding to payment or splitting it based on the items ordered. Odoo POS provides two features to perform these tasks seamlessly: **Bill Printing** and **Bill Splitting**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12 +msgid "To activate the bill printing and splitting features, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your POS. Then, scroll down to the :guilabel:`Bills & Receipts` section and enable :guilabel:`Bill Printing` and :guilabel:`Bill Splitting`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:-1 +msgid "activate the bill printing and bill splitting features in the POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:21 +msgid "Bill printing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:23 +msgid "From an open session, click :menuselection:`Bill --> Print` at any moment to generate and print a bill." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:27 +msgid "The printed bill is **not** final and will be updated to reflect any changes to the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:30 +msgid "Bill splitting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:32 +msgid "From an open session, click :guilabel:`Split` to select the items to regroup. Once everything is selected, click :guilabel:`Payment` and proceed to checkout for these items. Repeat for each guest." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:36 +msgid "Once you return to the table, the selected items are no longer on order, as they have been paid for." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:38 +msgid "The feature is available as soon as at least two items are ordered." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:41 +msgid ":doc:`floors_tables`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:3 +msgid "Floors and tables management" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:6 +msgid "Add a floor" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:8 +msgid "Once your *Point of Sale* has been configured, select *Table Management* under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, click on *Floors* to create and name your floor and tables." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1 +msgid "View of the table management feature. Way to manage and create floors for a pos" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1 +msgid "Backend view of a restaurant floor. Table name and number of sits for each table" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:21 +msgid "Don’t forget to link your floor to your point of sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:24 +msgid "Add tables" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:26 +msgid "To add tables, you can also open your PoS interface to see your floor(s)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1 +msgid "View of the floors menu to manage several floors at the same time" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:33 +msgid "Then, click on *Edit Mode* (pencil icon on the upper right corner) to be allowed to create, move, modify tables, etc." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1 +msgid "View of the floor management. Add tables, the number of sits, their name and their shape" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:41 +msgid "To make your table easier to be found, you can rename them, change their shape, size or even color. It is also possible to add the maximum number of sits the table can have." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:48 +msgid "Register your table(s) orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:50 +msgid "To register an order, click on the respective table. By doing so, you are taken to your main interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1 +msgid "View of the pos interface to register orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:58 +msgid "Transfer customer(s)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:60 +msgid "If your customers want to move to another table after they already ordered, use the transfer button. This way, the order is also moved to the new table." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:64 +msgid "To do so, select the table your customer is currently on." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1 +msgid "View of the restaurant tables, one having a pending order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:70 +msgid "Now, click on the transfer button and select the table to which you are transferring your customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1 +msgid "View of the pos interface and transfer button. How to transfer customers from one table\n" +"to another" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:79 +msgid "Register an additional order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:81 +msgid "When registering an order, use the + button to simultaneously proceed to another one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:84 +msgid "Then, you can shift between your orders and process the payment when needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1 +msgid "View of the - button, allowing employees to close/remove an order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:92 +msgid "The - button allows you to remove the order you are currently on." +msgstr "" + #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:3 -msgid "Print orders at the kitchen or bar" +msgid "Orders printing" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:5 @@ -2389,165 +2851,8 @@ msgstr "" msgid "When you press it, it will print the order on your kitchen/bar printer." msgstr "" -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:3 -msgid "Manage your tables" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:5 -msgid "Restaurants have specific needs that shops don’t have. That’s why Odoo gives restaurant owners several unique features to help them manage their business in the best possible way." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:9 -msgid "Floor and table management, bill splitting, or even the possibility to print orders from the kitchen, everything is there to help your business shine and your employees to work efficiently." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:16 -msgid "To activate the bar/restaurant features, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and open your PoS. Now, select *Is a Bar/Restaurant*." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "Restaurant set up. Enabling the is a bar/Restaurant feature on a PoS" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:24 -msgid "New features are shown with a fork and a knife next to it, indicating that they are restaurant-specific." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "Several restaurant features. Bill printing, bill splitting and tips" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:32 -msgid "Add a floor" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:34 -msgid "Once your *Point of Sale* has been configured, select *Table Management* under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, click on *Floors* to create and name your floor and tables." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "View of the table management feature. Way to manage and create floors for a pos" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "Backend view of a restaurant floor. Table name and number of sits for each table" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:47 -msgid "Don’t forget to link your floor to your point of sale." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:50 -msgid "Add tables" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:52 -msgid "To add tables, you can also open your PoS interface to see your floor(s)." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "View of the floors menu to manage several floors at the same time" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:59 -msgid "Then, click on *Edit Mode* (pencil icon on the upper right corner) to be allowed to create, move, modify tables, etc." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "View of the floor management. Add tables, the number of sits, their name and their shape" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:67 -msgid "To make your table easier to be found, you can rename them, change their shape, size or even color. It is also possible to add the maximum number of sits the table can have." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:72 -msgid "Register your table(s) orders" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:74 -msgid "To register an order, click on the respective table. By doing so, you are taken to your main interface." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "View of the pos interface to register orders" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:82 -msgid "Transfer customer(s)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:84 -msgid "If your customers want to move to another table after they already ordered, use the transfer button. This way, the order is also moved to the new table." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:88 -msgid "To do so, select the table your customer is currently on." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "View of the restaurant tables, one having a pending order" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:94 -msgid "Now, click on the transfer button and select the table to which you are transferring your customer." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "View of the pos interface and transfer button. How to transfer customers from one table\n" -"to another" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:103 -msgid "Register an additional order" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:105 -msgid "When registering an order, use the + button to simultaneously proceed to another one." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:108 -msgid "Then, you can shift between your orders and process the payment when needed." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None -msgid "View of the - button, allowing employees to close/remove an order" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:116 -msgid "The - button allows you to remove the order you are currently on." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:3 -msgid "Offer a bill-splitting option" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:5 -msgid "Offering an easy bill splitting solution to your customers will leave them with a positive experience. That's why this feature is available out-of-the-box in the Odoo Point of Sale application." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:12 -msgid "To activate the *Bill Splitting* feature, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:16 -msgid "Under the Bills & Receipts category, you will find the Bill Splitting option." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:23 -msgid "Split a bill" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:25 -msgid "In your PoS interface, you now have a *Split* button." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:30 -msgid "When you use it, you will be able to select what that guest should had and process the payment, repeating the process for each guest." -msgstr "" - #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:3 -msgid "Integrate a tip option into payment" +msgid "Tips" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:5 @@ -2579,7 +2884,7 @@ msgid "Add the tip your customer wants to leave and process to the payment." msgstr "" #: ../../content/applications/sales/point_of_sale/shop.rst:5 -msgid "Shop Features" +msgid "Shop features" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:3 @@ -2594,7 +2899,7 @@ msgstr "" msgid "To use a barcode scanner, you must enable the feature in the Inventory app. Go to :menuselection:`Inventory --> Configuration --> Settings`, in the :guilabel:`Barcode` section, tick :guilabel:`Barcode Scanner` and save." msgstr "" -#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:None +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:-1 msgid "barcode setting in the Inventory application" msgstr "" @@ -2647,19 +2952,15 @@ msgid "You can also enter the barcode number manually in the search bar to look msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:58 -msgid ":doc:`Get started <../overview/getting_started>`" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:61 msgid "Log employees" msgstr "" -#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:63 +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:60 msgid "You can also use a barcode scanner to log your employees. To do so, :ref:`restrict access ` to the POS and :ref:`use barcodes to log your employees in ` your POS." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:3 -msgid "Set-up Cash Control in Point of Sale" +msgid "Cash control" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:5 @@ -2710,206 +3011,6 @@ msgstr "" msgid "If you use the *Take Money Out* option to take out your transactions for this session, you now have a zero-sum difference and the same closing balance as your opening balance. You cashbox is ready for the next session." msgstr "" -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:3 -msgid "Cash Rounding" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:5 -msgid "**Cash rounding** is required when the lowest physical denomination of currency, or the smallest coin, is higher than the minimum unit of account." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:9 -msgid "For example, some countries require their companies to round up or down the total amount of an invoice to the nearest five cents, when the payment is made in cash." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:13 -msgid "Each point of sale in Odoo can be configured to apply cash rounding to the totals of its bills or receipts." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:19 -msgid "Go to :menuselection:`Point of Sale --> Configuration --> Settings` and enable *Cash Rounding*, then click on *Save*." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:25 -msgid "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the point of sale you want to configure, and enable the *Cash Rounding* option." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:29 -msgid "To define the **Rounding Method**, open the drop-down list and click on *Create and Edit...*." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:32 -msgid "Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*, then save both the Rounding Method and your Point of Sale settings." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:39 -msgid "All total amounts of this point of sale now add a line to apply the rounding according to your settings." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:46 -msgid "Odoo Point of Sale only support the *Add a rounding line* rounding strategies and *Half-up* rounding methods." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:3 -msgid "Invoice from the PoS interface" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:5 -msgid "Some of your customers might request an invoice when buying from your Point of Sale, you can easily manage it directly from the PoS interface." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:9 -msgid "Activate invoicing" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:11 -msgid "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select your Point of Sale:" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:17 -msgid "Under the *Bills & Receipts* you will see the invoicing option, tick it. Don't forget to choose in which journal the invoices should be created." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:25 -msgid "Select a customer" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:27 -msgid "From your session interface, use the customer button" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:32 -msgid "You can then either select an existing customer and set it as your customer or create a new one by using this button." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:38 -msgid "You will be invited to fill out the customer form with its information." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:41 -msgid "Invoice your customer" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:43 -msgid "From the payment screen, you now have an invoice option, use the button to select it and validate." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:49 -msgid "You can then print the invoice and move on to your next order." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:52 -msgid "Retrieve invoices" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:54 -msgid "Once out of the PoS interface (:menuselection:`Close --> Confirm` on the top right corner) you will find all your orders in :menuselection:`Point of Sale --> Orders --> Orders` and under the status tab you will see which ones have been invoiced. When clicking on a order you can then access the invoice." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:3 -msgid "Log in with employee" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:5 -msgid "With Odoo *Point of Sale*, you can manage multiple cashiers. This feature allows you to keep track of who is working, when and how much each cashier made for that session." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:9 -msgid "There are three ways to switch cashiers in Odoo: by *selecting the cashier*, by *entering a PIN code* or by *scanning a barcode*." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:13 -msgid "To manage multiple cashiers, you need several employees (at least two)." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:18 -msgid "Set up log in with employees" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:20 -msgid "To enable the feature, go to your *PoS settings* and check log in with employees on your *PoS form*. Then, add the employees that have access to the cash register." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:27 -msgid "Now, you can switch cashier easily." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:30 -msgid "Switch without pin codes" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:32 -msgid "The easiest way to switch cashiers is without a code. To do so, click on the cashier name in your PoS interface." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:38 -msgid "Now, you just have to click on your name." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:46 -msgid "Switch cashier with pin codes" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:48 -msgid "You can set a pin code on each cashier. To set up a pin code, go to the employee form and add a security PIN, in the *HR settings tab*." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:54 -msgid "Now, when switching cashier, a PIN password will be asked." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:62 -msgid "Switch cashier with barcodes" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:64 -msgid "You can ask your employees to log themselves with their badges. To do so, set up a barcode at the same place you add the PIN code. Print the badge and when they will scan it, the cashier will be switched to that employee." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:73 -msgid "Find who was the cashier" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:75 -msgid "Once you have closed your *PoS session*, you can have an overview of the amount each cashier sold for. To do so, go to the orders menu." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:81 -msgid "Now, you can open the order and have a summary of the sold products." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:3 -msgid "Reprint Receipts" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:5 -msgid "Use the *Reprint receipt* feature if you have the need to reprint a ticket." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:10 -msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale`. and select your PoS interface." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:13 -msgid "Under the Bills & Receipts category, you will find *Reprint Receipt* option." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:17 -msgid "In order to allow the option reprint receipt, you need to activate the receipt printer." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:23 -msgid "Reprint a receipt" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:25 -msgid "On your PoS interface, you now have a *Reprint receipt* button." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:30 -msgid "When you use it, you can then reprint your last receipt." -msgstr "" - #: ../../content/applications/sales/rental.rst:3 msgid "Rental" msgstr "" @@ -2938,7 +3039,7 @@ msgstr "" msgid "Go to :menuselection:`Rental --> Products`, select or create a product, and click on the product's *Rental* tab. Under *Rental Pricing*, click on *Add a price*. Then choose a *Unit* of time (hours, days, weeks, or months), a *Duration*, and a *Price*. You can add as many price lines as necessary, usually to give out discounts for longer rental durations." msgstr "" -#: ../../content/applications/sales/rental.rst:None +#: ../../content/applications/sales/rental.rst:-1 msgid "Example of rental pricing configuration in Odoo Rental" msgstr "" @@ -2998,7 +3099,7 @@ msgstr "" msgid "You can ask your customers to sign a rental agreement outlining the arrangement between you and your customers before they pick up products to make sure your products are returned on time and in their original condition. To do so, go to :menuselection:`Rental --> Configuration --> Settings`, activate *Digital Documents*, and *Save*." msgstr "" -#: ../../content/applications/sales/rental.rst:None +#: ../../content/applications/sales/rental.rst:-1 msgid "Digital Documents settings in Odoo Rental" msgstr "" @@ -3026,7 +3127,7 @@ msgstr "" msgid "You can print and give your customers receipts when they pick up and/or return products. To do so, open any rental order, click on *Print* and select *Pickup and Return Receipt*. Odoo then generates a PDF detailing all information about the current status of the rented items: which were picked up, when they are expected to be returned, which were returned, and potential rental delay costs." msgstr "" -#: ../../content/applications/sales/rental.rst:None +#: ../../content/applications/sales/rental.rst:-1 msgid "Printing a Pickup and Return receipt in Odoo Rental" msgstr "" @@ -3114,7 +3215,6 @@ msgstr "" msgid "**Shipping**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:34 #: ../../content/applications/sales/sales/amazon_connector/features.rst:34 msgid "Charges" msgstr "" @@ -3686,7 +3786,7 @@ msgstr "" msgid "The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`. Click on *Generate Token* to retrieve your **Verification Token**." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:None +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 msgid "Button to generate an eBay verification token in Odoo" msgstr "" @@ -3698,7 +3798,7 @@ msgstr "" msgid "Log in on the `developer portal of eBay `_ and go to **Alerts & Notifications**." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:None +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 msgid "Overview of the Alerts & Notifications dashboard of eBay" msgstr "" @@ -3722,7 +3822,7 @@ msgstr "" msgid "A verification token" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:None +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 msgid "Dedicated fields to enter the endpoint details" msgstr "" @@ -3742,7 +3842,7 @@ msgstr "" msgid "You should get the following confirmation message: \"A test notification was sent successfully!\"" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:None +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 msgid "Button to send test notification" msgstr "" @@ -3791,107 +3891,204 @@ msgid "Invoicing Method" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:3 -msgid "Request a down payment" +msgid "Down payments" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:5 -msgid "A down payment is a partial payment made by the buyer when a sales contract is concluded. This implies both parties' full commitment (seller and buyer) to honor the contract. With a down payment, the buyers show their will to acquire the product and agree to pay the rest later, while the sellers are obliged to provide the goods by accepting it." +msgid "A down payment is a partial payment made by the buyer when a sales contract is concluded. This implies both parties' (seller and buyer) full commitment to honor the contract." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:10 -msgid "Sometimes a down payment is required for expensive orders or projects. That way, you can protect yourself and make sure that your customer is reliable." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:8 +msgid "With a down payment, the buyer pays a portion of the total amount owed while agreeing to pay the remaining amount at a later date. In turn, the seller provides goods or services to the buyer after accepting the down payment, trusting that the remaining amount will be paid later on." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:14 -msgid "First time you request a down payment" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:13 +msgid "Initial down payment request" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:16 -msgid "When a sales order is confirmed, you then have the possibility to create an invoice. Invoices are automatically created in drafts so that you can review them before validation. To create an invoice, Odoo Sales offers you 3 options:" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:15 +msgid "When a sales order is confirmed, the option to create an invoice becomes available, via the :guilabel:`Create Invoice` button, located in the upper-left corner of the sales order form. When clicked, a :guilabel:`Create invoices` pop-up appears." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:20 -msgid "Regular invoice" -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:21 -msgid "Down payment (percentage)" +msgid "Invoices are automatically created in drafts, so they can be reviewed before validation." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:22 -msgid "Down payment (fixed amount)" +msgid "On the :guilabel:`Create invoices` pop-up, there are 3 options to choose from in the :guilabel:`Create Invoice` field:" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:24 -msgid "In terms of down payment, it can either be a fixed amount or a percentage of the total amount. The first time you request a down payment, you can set a percentage or a fixed amount of your choice, and select the right income account and taxes. These settings will be reused for future down payments." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 +msgid ":guilabel:`Regular invoice`" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None -msgid "How can you do a down payment on Odoo Sales?" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 +msgid "If :guilabel:`Regular Invoice` is selected the other fields disappear, as they only pertain to down payment configurations." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 +msgid ":guilabel:`Down payment (percentage)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 +msgid ":guilabel:`Down payment (fixed amount)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:32 +msgid "In terms of a down payment, it can either be a fixed amount or a percentage of the total amount." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 -msgid "When you request your first down payment, a new product called **Down payment** will be created. This product will be registered as a **service** product with an invoicing policy of **ordered quantities**. As a reminder, you can edit this product and modify it at any time. Please note that if you choose **delivered quantities** as invoicing policy, **you will not be able to create an invoice**." +msgid "Once the desired down payment option is selected in the :guilabel:`Create Invoice` field, designate the desired amount (either as a percentage or fixed amount) in the :guilabel:`Down Payment Amount` field." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:41 -msgid "Basic sales flow using down payments" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:38 +msgid "Then, select the appropriate income account for the invoice in the :guilabel:`Income Account` field, and add a tax amount, if necessary, in the :guilabel:`Customer Taxes` field. These settings will be reused for future down payments." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:43 -msgid "For this first example, we will use a 50% amount down payment with a product using **ordered quantities** as invoicing policy. Make sure to check out our documentation about invoicing policies here: :doc:`invoicing_policy` , before requesting your first down payment. When it comes to create and view the invoice, you will only have access to a draft invoice mentioning the down payment (as you can see below)." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "How to configure a down payment on Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None -msgid "What is a basic sales flow using down payments on Odoo Sales (1)?" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:47 +msgid "When a down payment is first requested, a new product called :guilabel:`Down payment` is created. This product is registered as a :guilabel:`Service` product, with an invoicing policy of :guilabel:`Ordered quantities`. This product can be edited and modified at any time." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:53 -msgid "There, you can post the invoice and register the payment of your customer. But, we all know that in real life this flow does not happen immediately. So, for now, you can return to the sales order. There, you will have the possibility to see the order as a customer with the **Customer preview** button or to reach easily the previous draft invoice with the **Invoice** button. In any case, the down payment will be mentioned on both (sales order and draft invoice)." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:52 +msgid "If :guilabel:`Delivered quantities` is chosen as the invoicing policy, an invoice will **not** be able to be created." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None -msgid "What is a basic sales flow using down payments on Odoo Sales (2)?" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:56 +msgid "Request a 50% down payment" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:63 -msgid "To complete the flow, when the customer wants to pay the rest of his sales order, you must create another invoice. Once again, you will have the choice to make another down payment or to deduct all the down payments and so, paying the rest of the invoice as a regular invoice." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:58 +msgid "For the following example, the flow involves a 50% amount down payment on a product with :guilabel:`Ordered quantities` as the invoicing policy." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None -msgid "What is a basic sales flow using down payments on Odoo Sales (3)?" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:62 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:184 +msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:71 -msgid "This flow is also possible with a down payment taking into account a fixed amount." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:64 +msgid "When the order is confirmed (via the :guilabel:`Confirm` button), it's time to create/view the invoice, by clicking :guilabel:`Create Invoice`." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:74 -msgid "Be careful that if you do a down payment with a product using **delivered quantities** as invoicing policy, you won’t be able to deduct all the down payments when it comes to invoicing your customer. Indeed, you have to deliver a product before creating the final invoice. If nothing has been delivered, you create a **credit note** that cancels the draft invoice created after the down payment. To do so, you have to install the **Inventory App** to confirm the delivery. Otherwise, you can enter the delivered quantity manually on the sales order." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:67 +msgid "Then, on the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down Payment Amount` field. Lastly, click :guilabel:`Create and View Invoice` to create and view the invoice." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:82 -msgid "Modify the income account and customer taxes" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "Create invoices pop up window in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:75 +msgid "Doing so reveals the draft invoice, which mentions the down payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "A sample draft invoice with down payment mentioned in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:81 +msgid "From there, the invoice can be confirmed/posted, and the payment can be registered. Return to the sales order, via the breadcrumbs." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:84 -msgid "From the products list, search for the **Down Payment** product." +msgid "On the sales order, the option to view what the customer will see is available, via the :guilabel:`Customer Preview` smart button, and the :guilabel:`Invoice` button reveals the drafted invoice. In either case, the down payment is mentioned on both the sales order and draft invoice." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None -msgid "Creation of a down payment product on Odoo Sales" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "How the down payment is mentioned on the sales order in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:90 -msgid "You can edit it and under the **General Information Tab** you will be able to change the customer taxes. Now, to change the income account, you will need to install the **Accounting App** to have the possibility to see the **Accounting Tab** on the product form." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:92 +msgid "To confirm and register the first payment of the down payment, click the :guilabel:`Invoices` smart button to return to the invoice. On the :guilabel:`Customer Invoice` page, click :guilabel:`Confirm`, then :guilabel:`Register Payment` to open a :guilabel:`Register Payment` pop-up form." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "How the register payment pop up looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:101 +msgid "On this form, select the appropriate :guilabel:`Journal` and confirm that the down payment amount is correct in the :guilabel:`Amount` field. Then, make any other modifications to the other fields, if necessary, before clicking :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 +msgid "Odoo returns to the invoice, which now has a green :guilabel:`In Payment` banner visible in the upper-right corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "How the initial down payment invoice has a green paid banner in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112 +msgid "Now, when the customer wants to pay the remaining amount of the order, another invoice must be created. To do that, return to the sales order, and click :guilabel:`Create Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:115 +msgid "On the :guilabel:`Create invoices` pop-up window, there is now an option to :guilabel:`Deduct down payments`, which is selected by default." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "The deduct down payment option on the create invoices pop up in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:122 +msgid "If the remaining amount is ready to be paid, the :guilabel:`Regular Invoice` option should be selected, and the :guilabel:`Deduct down payments` option should *stay* selected. Then, click :guilabel:`Create and View Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 +msgid "Doing so reveals a separate :guilabel:`Invoices` page, listing all the invoices for that specific sales order. Each invoice line item displays all the necessary information related to each invoice, along with the current :guilabel:`Payment Status`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "The down payment invoices page in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:134 +msgid "To complete the flow, select the invoice with the :guilabel:`Not Paid` status, which opens that invoice. On the invoice page, click :guilabel:`Confirm`, then :guilabel:`Register Payment`, and confirm that the remaining :guilabel:`Amount` is correct. Then, click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:138 +msgid "That pop-up window disappears, and a green :guilabel:`In Payment` banner is now present on the invoice. The line items on the invoice show that the total amount has been paid, including mentions of the down payment, and the flow is complete." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:142 +msgid "This flow is also possible with the :guilabel:`Fixed amount` down payment option." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:145 +msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, the down payments will **not** be able to be deducted when it comes time to invoice the customer. This is because, due to the invoicing policy, the product(s) would have to be delivered *before* creating the final invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:150 +msgid "If nothing has been delivered, a :guilabel:`Credit Note` is created, which cancels the draft invoice that was created after the down payment. To utilize the :guilabel:`Credit Note` option, the *Inventory* application must be installed, in order to confirm the delivery. Otherwise, the delivered quantity can be entered manually directly on the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:156 +msgid "Income account and customer taxes modifications" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158 +msgid "To adjust the income account and customer taxes attached to a down payment, navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> Products --> Products`), search for the `Down Payment` product in the search bar, and select it to reveal the product detail page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:162 +msgid "On the :guilabel:`Down Payment` product page, click :guilabel:`Edit`, then scroll down to the :guilabel:`General Information` tab. In this tab, the customer taxes can be modified in the :guilabel:`Customer Taxes` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 msgid "How to modify the income account link to down payments" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 -msgid ":doc:`invoicing_policy`" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 +msgid "To change or adjust the income account attached to the :guilabel:`Down Payment` product page, the *Accounting* app **must** be installed. With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes available on the product page. That tab will **not** be accessible without the *Accounting* app installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:175 +msgid "In the :guilabel:`Accounting` tab, the income account can be changed in the :guilabel:`Income Account` field, in the :guilabel:`Receivables` section. Once all desired changes are complete, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:3 @@ -3988,7 +4185,7 @@ msgstr "" msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and under **Invoicing policy** choose the rule you want to apply." msgstr "" -#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:None +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:-1 msgid "How to choose your invoicing policy on Odoo Sales?" msgstr "" @@ -4004,7 +4201,7 @@ msgstr "" msgid "From any product page, under the **Sales tab**, you will find the invoicing policy, which can be manually changed." msgstr "" -#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:None +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:-1 msgid "How to change your invoicing policy on a product form on Odoo Sales?" msgstr "" @@ -4032,7 +4229,7 @@ msgstr "" msgid "Once the quotation is confirmed and that the status went from **Quotation sent** to **Sales order**, you are able to see your delivered and invoiced quantities directly from your sales order (it is true for both rules)." msgstr "" -#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:None +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:-1 msgid "How to see your delivered and invoiced quantities on Odoo Sales?" msgstr "" @@ -4081,29 +4278,60 @@ msgid "You can then invoice that first milestone." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:3 -#: ../../content/applications/sales/sales/invoicing/proforma.rst:22 -msgid "Send a pro-forma invoice" +msgid "Pro-forma invoices" msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:5 -msgid "A pro-forma invoice is an abridged or estimated invoice in advance of a delivery of goods. It notes the kind and quantity of goods, their value, and other important information such as weight and transportation charges. Pro-forma invoices are commonly used as preliminary invoices with a quotation, or for customs purposes in importation. They differ from a normal invoice in not being a demand or request for payment." +msgid "A *pro-forma invoice* is an abridged or estimated invoice sent in advance of a delivery of goods. It notes the kind and quantity of goods, their value, and other important information, such as weight and transportation charges." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:13 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:9 +msgid "Pro-forma invoices are commonly used as preliminary invoices with a quotation. They are also used for customs purposes during importation. They differ from a normal invoice in that they are not a demand (or request) for payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:14 #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 msgid "Activate the feature" msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:15 -msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Pro-Forma Invoice* feature." +#: ../../content/applications/sales/sales/invoicing/proforma.rst:16 +msgid "In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature **must** be activated. To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Quotations & Orders` section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, click :guilabel:`Save` to save all changes." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:24 -msgid "From any quotation or sales order, you know have an option to send a pro-forma invoice." +#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1 +msgid "The Pro-Forma Invoice feature setting in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:30 -msgid "When you click on send, Odoo will send an email with the pro-forma invoice in attachment." +#: ../../content/applications/sales/sales/invoicing/proforma.rst:26 +msgid "Send a pro-forma invoice" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:28 +msgid "With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send a pro-forma invoice is now available on any quotation or sales order, via the :guilabel:`Send Pro-Forma Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1 +msgid "The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:35 +msgid "When the :guilabel:`Send Pro-Forma Invoice` button is clicked, an email pop-up appears. The :guilabel:`Recipients` field is auto-populated with the customer from the sales order or quotation. Then, if needed, modify the :guilabel:`Subject` field and the body of the email. The pro-forma invoice is automatically added as an attachment to the email." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:40 +msgid "When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with the attached pro-forma invoice, to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1 +msgid "The email pop-up window that appears with pro-forma invoice attached in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:48 +msgid "To preview what the pro-forma invoice looks like, click on the PDF at the bottom of the email pop-up window *before* clicking :guilabel:`Send`. When clicked, the pro-forma invoice is downloaded instantly. Open that PDF to view (and review) the pro-forma invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:0 +msgid "Sample pro-forma invoice PDF from Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/subscriptions.rst:3 @@ -4523,7 +4751,7 @@ msgstr "" msgid "To use product variants, go to :menuselection:`Sales --> Configuration --> Settings --> Product Catalog`, and enable the :guilabel:`Variants` feature. Finally, click :guilabel:`Save` to apply the setting." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:None +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 msgid "Activating product variants." msgstr "" @@ -4543,7 +4771,7 @@ msgstr "" msgid "To create a new attribute, click :guilabel:`Create`. First, choose an attribute name, such as \"Color\" or \"Size.\"" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:None +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 msgid "Attribute creation window." msgstr "" @@ -4563,7 +4791,7 @@ msgstr "" msgid ":guilabel:`Color`: options appear as small colored squares, which reflect any HTML color codes set." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:None +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 msgid "Display Types on Product Configurator." msgstr "" @@ -4607,7 +4835,7 @@ msgstr "" msgid "A color code can be selected either by dragging the slider around or by entering a specific HTML color code (e.g. #FF0077)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:None +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 msgid "Selecting a color." msgstr "" @@ -4671,7 +4899,7 @@ msgstr "" msgid "In the :guilabel:`Exclude for` section, click :guilabel:`Add a line` and select any product(s) and/or specific attribute values that are currently unavailable. Finally, click :guilabel:`Save` to apply the setting, and Odoo will automatically show the product variant as unavailable on the eCommerce page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:None +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 msgid "Excluding attributes." msgstr "" @@ -4691,7 +4919,7 @@ msgstr "" msgid "Then, click on a variant value, and :guilabel:`Edit`. In the :guilabel:`Value Price Extra` field, type in the additional cost for this particular value. This amount is added to the standard price. Finally, click :guilabel:`Save` to apply the extra price to the value." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:None +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 msgid "Value Price Extra setting." msgstr "" @@ -4747,7 +4975,7 @@ msgstr "" msgid "On the validated delivery order, click :guilabel:`Return` to open the :guilabel:`Reverse Transfer` pop-up window. By default, the :guilabel:`Quantity` matches the validated quantities from the delivery order. Update the quantities if necessary. Click on the trash icon next to a line item to remove it from the return." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:None +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 msgid "The \"Reverse Transfer\" pop-up window, to make a return before invoicing the customer." msgstr "" @@ -4755,7 +4983,7 @@ msgstr "" msgid "Next, click :guilabel:`Return` to confirm the return. This generates a new warehouse operation for the incoming returned product(s). Upon receiving the return, the warehouse team validates the warehouse operation. Then, on the original sales order, the :guilabel:`Delivered` quantity will reflect the difference between the initial validated quantities and the returned quantities." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:None +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 msgid "The updated \"Delivered\" quantity on the sales order after the reverse transfer." msgstr "" @@ -4783,7 +5011,7 @@ msgstr "" msgid "To process a refund, navigate to the relevant invoice (from the sales order, click on the :guilabel:`Invoices` smart button). Click :guilabel:`Add Credit Note` from the validated invoice." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:None +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 msgid "The \"Credit Note\" pop-up window, to issue a credit to the customer after invoicing." msgstr "" @@ -4819,7 +5047,7 @@ msgstr "" msgid "With Odoo Sales, it is possible to instantly add an **Expiration Date** from the quotation or the sales order." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:None +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:-1 msgid "How to configure deadlines on Odoo Sales?" msgstr "" @@ -4831,7 +5059,7 @@ msgstr "" msgid "It is also possible to add a deadline to every quotation template created. Whenever a specific quotation template is used in a quote, its associated deadline will be automatically applied. Be sure to check out our documentation about :doc:`quote_template` to excel in their use." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:None +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:-1 msgid "How to use deadline in a quotation template on Odoo Sales?" msgstr "" @@ -4863,7 +5091,7 @@ msgstr "" msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the **Customer Addresses** feature." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:None +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 msgid "How to enable different customer addresses on Odoo Sales?" msgstr "" @@ -4875,7 +5103,7 @@ msgstr "" msgid "When you create a quotation, you must add a customer. This customer can be a company or a person with specific billing and shipping addresses already defined and registered in the system, or it can be a new customer. In this case, you have to **Create and edit** the contact form for your new customer and link it, if necessary, to a company. In this contact form, you will be able to add, delete and modify invoice and delivery addresses." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:None +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 msgid "How to add addresses from a quotation on Odoo Sales?" msgstr "" @@ -4891,7 +5119,7 @@ msgstr "" msgid "Previously, we talked about the contact form that you can fill in directly from a quotation or a sales order to add billing and shipping addresses to customers. But, if you go to :menuselection:`Sales --> Orders --> Customers`, you can create or modify every customer you want and add, delete or modify invoice and delivery addresses instantly there, before creating a quotation." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:None +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 msgid "How to add addresses from a contact form on Odoo Sales?" msgstr "" @@ -4903,7 +5131,7 @@ msgstr "" msgid "Like for the previous example, go to :menuselection:`Sales --> Orders --> Customers` and create a new customer. There, you can add company information but, more importantly, you can enter billing and shipping addresses under the **Contacts & Addresses** tab." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:None +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 msgid "How to manage different customer addresses on Odoo Sales?" msgstr "" @@ -4911,7 +5139,7 @@ msgstr "" msgid "Once done, you can return to your Sales dashboard and create a new quotation. Now, if you enter your new customer, you will see that the other fields will fill in by themself with the information previously saved for billing and shipping addresses." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:None +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 msgid "Automatic quotation fields filling on Odoo Sales" msgstr "" @@ -4935,7 +5163,7 @@ msgstr "" msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the **Online Payment** feature." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:None +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 msgid "How to enable online payment on Odoo Sales?" msgstr "" @@ -4955,7 +5183,7 @@ msgstr "" msgid "After opening quotations from their received email, your customers will have different possibilities to make their online payments. For example:" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:None +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 msgid "How to register a payment on Odoo Sales?" msgstr "" @@ -4991,7 +5219,7 @@ msgstr "" msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the **Online Signature** feature." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:None +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:-1 #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 msgid "How to enable online signature on Odoo Sales?" msgstr "" @@ -5008,7 +5236,7 @@ msgstr "" msgid "When you send quotations to clients, they can instantly accept and sign it online. When they click on **Sign & Pay**, they have the choice to draw their own signature, automatically fill in the field with an automated signature or load a file from their computer. Here below, it is an example of an automated signature:" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:None +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:-1 msgid "How to confirm an order with a signature on Odoo Sales?" msgstr "" @@ -5036,7 +5264,7 @@ msgstr "" msgid "With Odoo Sales, it is possible to add or modify optional products directly on quotations (under the **Optional Products** tab, as you can see below)." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:None +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 msgid "How to add optional products to your quotations on Odoo Sales" msgstr "" @@ -5052,7 +5280,7 @@ msgstr "" msgid "In practice, your customers will be able to add different optional products to their order by using associated carts, with a user-friendly layout. More than that, if a customer selects all the optional products suggested, these additional items will automatically fill in the quotation managed by the salesman." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:None +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 msgid "How to select optional products on Odoo Sales" msgstr "" @@ -5060,7 +5288,7 @@ msgstr "" msgid "Like this, salespeople will see each movement made by the customer and tracking the order will be all the better." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:None +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 msgid "How to follow each movement made by your customers on Odoo Sales" msgstr "" @@ -5076,7 +5304,7 @@ msgstr "" msgid "For quotation templates, you also have an **Optional Products** tab where you can add related products or services." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:None +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 msgid "How to add optional products to your quotation templates on Odoo Sales" msgstr "" @@ -5096,7 +5324,7 @@ msgstr "" msgid "To enable product variants on quotations and sales orders, go to :menuselection:`Sales --> Configuration --> Settings --> Product Catalog` and activate one or both of the :guilabel:`Product Configurator` and :guilabel:`Variant Grid Entry` settings. Finally, click :guilabel:`Save` to apply the settings." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:None +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 msgid "Activating entry type settings." msgstr "" @@ -5104,7 +5332,7 @@ msgstr "" msgid "After saving the settings, configure the product form. Head over to :menuselection:`Sales --> Products --> Products` and select any product (or click :guilabel:`Create` to create a new one). On the product form, click :guilabel:`Edit`, and then click on the :guilabel:`Variants` tab. Under :guilabel:`Sales Variant Selection`, choose either :guilabel:`Product Configurator` or :guilabel:`Order Grid Entry`. This selection determines which method is used to add the product to quotations or sales orders. Finally, click :guilabel:`Save` to apply the setting." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:None +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 msgid "Sales variant selection." msgstr "" @@ -5124,7 +5352,7 @@ msgstr "" msgid "The :guilabel:`Product Configurator` lets salespeople choose exactly which product variant to add to the quotation or sales order using a format similar to online shopping. Color options display any HTML color codes set up in the :guilabel:`Color` attribute. Features with an additional cost will display the additional cost next to their name. Once the desired product variant attributes are selected, click :guilabel:`Add` to add the product variant to the quotation or sales order." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:None +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 msgid "Product Configurator and Price Extras." msgstr "" @@ -5144,7 +5372,7 @@ msgstr "" msgid ":guilabel:`Variant Grid Entry` displays a grid of every variant available for the selected product. Choose the exact quantities of each product variant for a quotation or sales order by typing in the number or using the arrows. :guilabel:`Not Available` is displayed when a particular variant has been deactivated in the database. Once all the product variants and their quantities have been set, click :guilabel:`Confirm` to add them to the quotation or sales order." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:None +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 msgid "Variant Grid Entry pop-up." msgstr "" @@ -5152,7 +5380,7 @@ msgstr "" msgid "Each product variant appears as an individual line item on the quotation or sales order, because each of these items has its own stock." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:None +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 msgid "Line items for grid variants." msgstr "" @@ -5168,7 +5396,7 @@ msgstr "" msgid "To enable this feature, go to :menuselection:`Sales --> Configuration --> Settings` and activate **Quotation Templates**." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:None +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 msgid "How to enable quotation templates on Odoo Sales?" msgstr "" @@ -5176,7 +5404,7 @@ msgstr "" msgid "For even more convenience, it is also recommended to add the **Quotation Builder** feature which will help you design your quotation templates very easily. This option will automatically install the Odoo Website App." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:None +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 msgid "How to enable quotation builder on Odoo Sales?" msgstr "" @@ -5193,7 +5421,7 @@ msgstr "" msgid "You can create a new template or edit an existing one. Once named, you will be able to select products and quantities as well as the expiration time of the quotation." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:None +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 msgid "Create a new quotation template on Odoo Sales" msgstr "" @@ -5205,7 +5433,7 @@ msgstr "" msgid "You will have the possibility to design your template and edit the customer interface in order to manage what clients will see before accepting and paying the quotation. For example, you will be able to describe your company, your services and your products. To do so, you can click on **Edit** and you will be brought to the quotation builder." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:None +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 msgid "Design your quotation template on Odoo Sales" msgstr "" @@ -5213,7 +5441,7 @@ msgstr "" msgid "You can easily edit the content of your template by dragging & dropping different building blocks to organize your quotation. For example, you can add a content block to describe your products." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:None +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 msgid "Drag & drop building blocks to create your quotation template on Odoo Sales" msgstr "" @@ -5225,7 +5453,7 @@ msgstr "" msgid "When creating a quotation, you can choose a specific template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:None +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 msgid "Select a specific template on Odoo Sales" msgstr "" @@ -5241,7 +5469,7 @@ msgstr "" msgid "Templates facilitate the confirmation process by allowing customers to sign electronically or to pay online. You can activate these two options directly in the quotation template itself." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:None +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 msgid "Allow your customers to sign electronically or to pay online on Odoo Sales" msgstr "" @@ -5275,7 +5503,7 @@ msgstr "" msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and activate *Default Terms & Conditions*." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:None +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 msgid "How to enable Default Terms & Conditions on Odoo Sales?" msgstr "" @@ -5291,7 +5519,7 @@ msgstr "" msgid "In the settings of the **Invoicing App**, you have the possibility to insert your default terms and conditions." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:None +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 msgid "Default Terms & Conditions on quotation on Odoo Sales" msgstr "" @@ -5307,7 +5535,7 @@ msgstr "" msgid "According to your business needs, you can specify your terms and conditions on your quotation templates. This is interesting if you have different terms and conditions within your company." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:None +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 msgid "Add Default Terms & Conditions to your quotation templates on Odoo Sales" msgstr "" @@ -5327,7 +5555,7 @@ msgstr "" msgid "Use the **Website App** and create your own general terms and conditions page. For example, here is the Odoo terms and conditions page:" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:None +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 msgid "General Terms & Conditions on your website" msgstr "" @@ -5335,7 +5563,7 @@ msgstr "" msgid "You can refer to this page in the footer of all your documents. The layout is available in the **General Settings** under the **Business Documents** category. For example, this footer appears in every document from Odoo." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:None +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 msgid "General Terms & Conditions in your business documents" msgstr "" @@ -5347,7 +5575,7 @@ msgstr "" msgid "Attach an external document with your general terms and conditions when you are about to send your quotation by email to your customers." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:None +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 msgid "General Terms & conditions as attachment in your email" msgstr "" @@ -5359,7 +5587,7 @@ msgstr "" msgid "Create and edit email templates to set a default attachment for all quotation emails that you will send in the future. To do so, you have to go to :menuselection:`Sales --> Configuration --> Quotation templates` and create a new quotation template or modify an existing one. Under the confirmation tab, you are now able to activate online signatures, online payments and to set a confirmation mail in which you have the possibility to configure the default attachment. There, you can put your general terms & conditions." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:None +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 msgid "General Terms & conditions as attachment in your quotation templates" msgstr "" @@ -5407,8 +5635,7 @@ msgstr "" msgid "Go to :menuselection:`Subscriptions --> Subscription products` to learn how you can configure your own subscription products. You have the possibility to create a new product or edit an existing one. Once named, be careful to select the option *Can be sold* and deselect *Can be purchased*. For the product type, it is recommended to use *Service* for subscription products as they are non-material products that you provide to your customers. Finally, you can adapt your prices and also add an internal reference." msgstr "" -#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:None -#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:0 +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:-1 #: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:0 msgid "View of a subscription product form in Odoo Subscriptions" msgstr "" @@ -5484,7 +5711,7 @@ msgstr "" msgid "Go to :menuselection:`Subscriptions --> Configuration --> Subscription templates`. By default, Odoo suggests you two types of subscription (MON - Monthly subscription *vs* YEA - Yearly subscription). You can also create your own ones." msgstr "" -#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:None +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:-1 msgid "Default subscription templates on Odoo Subscriptions" msgstr "" @@ -5496,7 +5723,7 @@ msgstr "" msgid "You can create a new template or edit an existing one. The first thing you need to do is give your template a name. After that, choose an *Invoicing period* and specify whether you would like to invoice your customers per *Days*, *Weeks*, *Months* or *Years*. On *Duration*, determine if the subscription must go on *Forever* (until it’s manually closed), or for a *Fixed amount* of time. Among the payment options, an additional field called *Invoice email* appears when you choose *Send*, *Send & try to charge* or *Send after successful payment*. This field allows you to add an invoice email template to your subscription templates." msgstr "" -#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:None +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:-1 msgid "Create your own subscription templates on Odoo Subscriptions" msgstr "" @@ -5562,7 +5789,7 @@ msgstr "" msgid "The following example shows how to create a new automatic alert to send satisfaction surveys to your customers, by email, after one month of subscription. To do so, go to :menuselection:`Subscriptions --> Configuration --> Alerts`, and create a new alert." msgstr "" -#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:None +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:-1 msgid "New automatic alert in Odoo Subscriptions" msgstr "" @@ -5586,7 +5813,7 @@ msgstr "" msgid "As a result, this alert will send a rating survey after one month, to the customers who have purchased that specific product. The survey will appear in the chatter of your respective subscription." msgstr "" -#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:None +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:-1 msgid "Satisfaction survey in Odoo Subscriptions" msgstr "" @@ -5598,7 +5825,7 @@ msgstr "" msgid "By default, Odoo suggests you an automatic alert called *Take action on less satisfied clients*." msgstr "" -#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:None +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:-1 msgid "Modify an existing automatic alert in Odoo Subscriptions" msgstr "" @@ -5614,10 +5841,6 @@ msgstr "" msgid ":doc:`../../subscriptions/reporting/subscription_reports`" msgstr "" -#: ../../content/applications/sales/subscriptions/reporting.rst:5 -msgid "Reporting" -msgstr "" - #: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:3 msgid "Generate subscription reports" msgstr "" @@ -5638,7 +5861,7 @@ msgstr "" msgid "**Annual Run-Rate (ARR)**: ARR is the yearly version of MRR, which is based on the current MRR, to estimate the coming year's performance. However, this estimation does not take variations and growth into account." msgstr "" -#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:None +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:-1 msgid "Difference between MRR and ARR in Odoo Subscriptions" msgstr "" @@ -5702,7 +5925,7 @@ msgstr "" msgid "Go to :menuselection:`Subscriptions --> Reporting --> Subscriptions`. From there, you can change the *Measures*. By default, Odoo uses the *Monthly Recurring Revenue*. In addition to that, you can choose *Quantity*, *Recurring Price*, *Yearly Recurring Revenue* and *Count*. For this example, *Quantity* is added. This way, you can review both of these measures at the same time. You can even *Group By Start Date* and, more precisely, by *Week*, to get a clear view of your report." msgstr "" -#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:None +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:-1 msgid "Subscriptions analysis report in Odoo Subscriptions" msgstr "" @@ -5714,7 +5937,7 @@ msgstr "" msgid "Go to :menuselection:`Subscriptions --> Reporting --> Retention`. The default measure applied is *Count*, but you can change to the appropriate one for you. For the example below, *Monthly Recurring Revenue* was chosen, and the *Month* periodicity remains intact. By using these criteria, you can see the progression of the retention from its start." msgstr "" -#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:None +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:-1 msgid "Retention analysis report in Odoo Subscriptions" msgstr "" @@ -5726,7 +5949,7 @@ msgstr "" msgid "Go to :menuselection:`Subscriptions --> Reporting --> Revenue KPIs`. From there, you can check different KPIs: *Monthly Recurring Revenue*, *Net Revenue*, *Non-Recurring Revenue*, *Revenue per Subscription*, *Annual Run-Rate*, *Lifetime Value*, and more. You can also filter this information on subscriptions, companies, and sales teams. This is useful if you are looking for specific information." msgstr "" -#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:None +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:-1 msgid "Revenue KPIs report in Odoo Subscriptions" msgstr "" @@ -5734,7 +5957,7 @@ msgstr "" msgid "The example below shows the *Monthly Recurring Revenue* detailed report. At the moment, there is no data, which is the typical scenario for a new business. But, as your company grows over the months, these graphs get populated with more and more data. Once again, you can filter these specific KPIs on subscriptions, companies, and sales teams." msgstr "" -#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:None +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:-1 msgid "Detailed MRR report in Odoo Subscriptions" msgstr "" @@ -5746,7 +5969,7 @@ msgstr "" msgid "Go to :menuselection:`Subscriptions --> Reporting --> Salesperson Dashboard`. This page gives you a summary of your *Monthly Recurring Revenue*, *Non-Recurring Revenue*, *Subscription modifications*, and *Non-Recurring Invoices* for each of your salespeople. You can choose the period you want to apply and the salesperson you want to analyze." msgstr "" -#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:None +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:-1 msgid "Salesperson dashboard report in Odoo Subscriptions" msgstr "" @@ -5778,7 +6001,7 @@ msgstr "" msgid "Go to :menuselection:`Subscriptions --> Configuration --> Subscription templates`. From there, you can create a new *Subscription template* or modify an existing one. When editing your template, underneath the Invoicing tab, you have the possibility to activate the option *Closable by customer*. Once enabled, this option gives your customers the right to close their own subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:-1 msgid "Configuration to close your subscription with Odoo Subscriptions" msgstr "" @@ -5798,7 +6021,7 @@ msgstr "" msgid "Once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to close the subscription." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:-1 msgid "Close your subscription from an administration point of view with Odoo Subscriptions" msgstr "" @@ -5806,7 +6029,7 @@ msgstr "" msgid "By using the smart button *Close*, you have to enter a close reason. For example, \"Subscription too expensive\", \"Subscription does not meet my requirements\", \"Subscription reached its end date\", etc. Immediately after confirming your close reason, you can observe that the status of the subscription is now *Closed* and that the close reason is mentioned on the subscription." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:-1 msgid "What happens when you close your subscription with Odoo Subscriptions?" msgstr "" @@ -5818,7 +6041,7 @@ msgstr "" msgid "As previously explained in the *Administrator view* part, from the subscription form, you also have the possibility to visualize what your customers see when managing their subscriptions thanks to the *Customer preview* button. In this example, the customer has the choice to close his/her subscription whenever he/she wants to, due to the *Close Subscription* button." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:-1 msgid "Close your subscription from a customer point of view with Odoo Subscriptions" msgstr "" @@ -5826,7 +6049,7 @@ msgstr "" msgid "By using this button, the customer can specify the reason for cancelling his/her subscription and he/she can even leave a message." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:-1 msgid "What happens when customers close their subscription with Odoo Subscriptions?" msgstr "" @@ -5834,7 +6057,7 @@ msgstr "" msgid "By confirming the cancellation, the customer is redirected to his/her portal. The administrator is informed of this modification. Indeed, the status of the subscription becomes *Closed* and a note appears in the chatter with the new stage, the end date, the close reason, and the closing text added by the customer." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:-1 msgid "What happens when customers close their subscription in Odoo Subscriptions?" msgstr "" @@ -5870,7 +6093,7 @@ msgstr "" msgid "Go to **Odoo Sales** and create a new quotation. Then, choose a customer and add a product. Be careful to select a product that you previously configured as a *Subscription product*." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:-1 msgid "View of a quotation form in Odoo Sales" msgstr "" @@ -5878,7 +6101,7 @@ msgstr "" msgid "When your quotation is ready, you have the possibility to send it to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers to have their confirmation and, then, *Confirm* it in **Odoo Sales**. By clicking on *Customer preview*, you have an idea of what your customers will see when receiving your quotation." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:-1 msgid "Customer preview of a quotation form in Odoo Sales" msgstr "" @@ -5894,7 +6117,7 @@ msgstr "" msgid "Once confirmed, the quotation becomes a sales order and a new button appears, *Subscriptions*. Indeed, a subscription is automatically created." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:-1 msgid "Quotation form in Odoo Sales with a button \"Subscriptions\"" msgstr "" @@ -5902,7 +6125,7 @@ msgstr "" msgid "By clicking on the *Subscriptions* button, you can see that the status of the subscription is *In progress*. From there, you will have three options: :doc:`Renew <../../subscriptions/sales_flow/renewals>`, :doc:`Close <../../subscriptions/sales_flow/closing>` or :doc:`Upsell <../../subscriptions/sales_flow/upselling>` your subscription." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:-1 msgid "Use of the intelligent button \"Subscriptions\" in Odoo Sales" msgstr "" @@ -5946,7 +6169,7 @@ msgstr "" msgid "Before renewing a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../../subscriptions/sales_flow/create_a_quotation>` using subscription products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to renew the subscription. In the Other Info tab, underneath the To Renew section, you can activate the *To renew* option. When activated, a yellow tag automatically appears in the upper right corner of the subscription." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:-1 msgid "Renew your subscription with Odoo Subscriptions" msgstr "" @@ -5986,7 +6209,7 @@ msgstr "" msgid "Finally, if you want to visualize all your subscriptions and easily find those to renew, you can go to your *Subscriptions dashboard* and use the filter *To renew*." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:-1 msgid "List view of all subscriptions and use of the filter to renew in Odoo Subscriptions" msgstr "" @@ -6010,7 +6233,7 @@ msgstr "" msgid "As previously explained, to upsell a subscription to new customers, it is recommended to offer *Discounts*. To activate this option, go to :menuselection:`Sales --> Configuration --> Settings` and, under the *Pricing* category, you have the possibility to grant discounts on sales order lines." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1 msgid "Activation of the discount option in Odoo Sales" msgstr "" @@ -6022,7 +6245,7 @@ msgstr "" msgid "Before upselling a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../../subscriptions/sales_flow/create_a_quotation>` using subscription products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to upsell your subscription." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1 msgid "Upsell your subscription with Odoo Subscriptions" msgstr "" @@ -6030,7 +6253,7 @@ msgstr "" msgid "By using the smart button *Upsell*, you are able to create a new quotation with new subscription products and send it to your customers for approval." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1 msgid "Add products to your subscription via the upsell option in Odoo Subscriptions" msgstr "" @@ -6042,7 +6265,7 @@ msgstr "" msgid "Of course, before sending this new quotation to your customers, you can change the unit price, taxes, and, even the discount you want to offer. The smart button *Customer preview* is useful for mimicking the customer's reaction. In this case, we can confidently say that the customer will *Sign and pay* this new quotation. When it is done, you have to go back in edit mode, confirm the quotation, and click on the smart button *Subscriptions* to visualize all updates. From there, you can see that an additional line has been added to the subscription with the new extra service the customer wanted to purchase." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1 msgid "Visualize all your subscriptions updates with Odoo Subscriptions" msgstr "" @@ -6050,7 +6273,7 @@ msgstr "" msgid "In addition, by clicking on the *Sales* button, you have a summary of your sales orders in a list view." msgstr "" -#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:None +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1 msgid "List view of all sales orders created for a subscription" msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index cd2d6a698..5f2114f99 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,99 +20,94 @@ msgstr "" msgid "Services" msgstr "" -#: ../../content/applications/services/fsm.rst:8 +#: ../../content/applications/services/field_service.rst:8 msgid "Field Service" msgstr "" -#: ../../content/applications/services/fsm.rst:11 +#: ../../content/applications/services/field_service.rst:11 msgid "`Odoo Tutorials: Field Service `_" msgstr "" -#: ../../content/applications/services/fsm/helpdesk.rst:5 -#: ../../content/applications/services/helpdesk.rst:8 -msgid "Helpdesk" +#: ../../content/applications/services/field_service/onsite_interventions.rst:3 +msgid "Onsite interventions planning" msgstr "" -#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:3 -msgid "Plan onsite interventions from helpdesk tickets" +#: ../../content/applications/services/field_service/onsite_interventions.rst:6 +msgid "From a sales order" msgstr "" -#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:5 -msgid "The integration with the Helpdesk app lets your helpdesk team manage intervention requests directly. Planning field service tasks from tickets speeds up your processes." -msgstr "" - -#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:9 -msgid "Configure the helpdesk team" -msgstr "" - -#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:11 -msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select a team and enable *Onsite Interventions*." -msgstr "" - -#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:None -msgid "Onsite interventions setting in Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:18 -msgid "The helpdesk tickets of the team now display the *Plan Intervention* button. Click on it to create a new task under your field service project." -msgstr "" - -#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:None -msgid "Plan intervention from helpdesk ticket in Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/fsm/sales.rst:5 -msgid "Sales" -msgstr "" - -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:3 -msgid "Create onsite interventions from sales orders" -msgstr "" - -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:5 +#: ../../content/applications/services/field_service/onsite_interventions.rst:8 msgid "Allowing your sales team to open onsite interventions creates a seamless experience for your customers. They can receive a quotation they first have to approve before the work even starts." msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:9 -msgid "Configure a product" -msgstr "" - -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:11 +#: ../../content/applications/services/field_service/onsite_interventions.rst:11 msgid "Go to :menuselection:`Field Service --> Configuration --> Products` and create or edit a product." msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:13 -msgid "Under the *General Information* tab, select *Service* as *Product Type*." +#: ../../content/applications/services/field_service/onsite_interventions.rst:13 +msgid "Under the :guilabel:`General Information` tab, select :guilabel:`Service` as :guilabel:`Product Type`." msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:14 -msgid "Under the *Sales* tab, select *Timesheets on tasks* as *Service Invoicing Policy*." +#: ../../content/applications/services/field_service/onsite_interventions.rst:15 +msgid "Under the :guilabel:`Sales` tab, select :guilabel:`Timesheets on tasks` as :guilabel:`Service Invoicing Policy`." msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:15 -msgid "Select *Create a task in an existing project* as *Service Tracking*." +#: ../../content/applications/services/field_service/onsite_interventions.rst:17 +msgid "Select :guilabel:`Create a task in an existing project` as :guilabel:`Service Tracking`." msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:16 -msgid "Select your *Project*." +#: ../../content/applications/services/field_service/onsite_interventions.rst:18 +msgid "Select your :guilabel:`Project`." msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:17 -msgid "If you use them, select your *Worksheet Template* and then click on *Save*." +#: ../../content/applications/services/field_service/onsite_interventions.rst:19 +msgid "If you use them, select your :guilabel:`Worksheet Template`, and save." msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:None +#: ../../content/applications/services/field_service/onsite_interventions.rst:-1 msgid "Product configuration to create tasks from sales orders in Odoo Field Service" msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:23 -msgid "From the *Sales* app, create a quotation with the product and confirm it. A task is automatically set up under your Field Service project. It is directly accessible from the sales order." +#: ../../content/applications/services/field_service/onsite_interventions.rst:25 +msgid "From the :doc:`Sales <../../sales/sales>` app, create a quotation with the product and confirm it. A task is automatically set up under your Field Service project. It is directly accessible from the sales order." msgstr "" -#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:None +#: ../../content/applications/services/field_service/onsite_interventions.rst:-1 msgid "Field Service task on a sales order in Odoo Sales" msgstr "" +#: ../../content/applications/services/field_service/onsite_interventions.rst:34 +msgid "From helpdesk tickets" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:36 +msgid "The integration with the :doc:`Helpdesk <../helpdesk>` app lets your helpdesk team manage intervention requests directly. Planning field service tasks from tickets speeds up your processes." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:40 +msgid "Configure the helpdesk team" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:42 +msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select a team and enable :guilabel:`Onsite Interventions`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:-1 +msgid "Onsite interventions settings in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:49 +msgid "The helpdesk tickets of the team now display the :guilabel:`Plan Intervention` button. Click on it to create a new task under your field service project." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:-1 +msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:8 +msgid "Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk.rst:11 msgid "`Odoo Tutorials: Helpdesk `_" msgstr "" @@ -197,7 +192,7 @@ msgstr "" msgid "Start by navigating to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit` and enable :guilabel:`Ticket closing` by checking the field box." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:None +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1 msgid "Ticket closing feature in Odoo Helpdesk." msgstr "" @@ -217,7 +212,7 @@ msgstr "" msgid "With the ticket closing settings now complete, customers can now view the option to :guilabel:`Close this ticket` when they log into their portal." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:None +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1 msgid "Customer view of ticket closing in Odoo Helpdesk." msgstr "" @@ -229,7 +224,7 @@ msgstr "" msgid "To analyze the tickets that have been closed by customers, go to :menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the :guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set the custom filter parameters to :guilabel:`Closed by partner` and :guilabel:`is true`. Finally, click :guilabel:`Apply`." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:None +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1 msgid "Filter for tickets closed by customers on Odoo Helpdesk's reporting page." msgstr "" @@ -261,7 +256,7 @@ msgstr "" msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and enable *Help Center*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 msgid "Overview of the settings page of a helpdesk team emphasizing the help center feature in\n" "Odoo Helpdesk" msgstr "" @@ -270,7 +265,7 @@ msgstr "" msgid "Create, or edit a forum by clicking on the external link. Among the editing options, choose if you would like the *Forum Mode* to be *Questions*: only one answer is allowed per question or *Discussions*: multiple answers are allowed per question." msgstr "" -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 msgid "Overview of a forum’s settings page in Odoo Helpdesk" msgstr "" @@ -278,8 +273,7 @@ msgstr "" msgid "From now on, logged in users can start their discussions. To keep track of posts, go to :menuselection:`Website --> Forum --> Posts`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 msgid "Overview of the Forums page of a website to show the available ones in Odoo Helpdesk" msgstr "" @@ -299,7 +293,7 @@ msgstr "" msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *eLearning*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 msgid "Overview of the settings page of a customer care team emphasizing the feature elearning in\n" "Odoo Helpdesk" msgstr "" @@ -308,7 +302,7 @@ msgstr "" msgid "Once the structure and content of your course are ready, *Publish* it by clicking on *Unpublished*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 msgid "View of a course being published for Odoo Helpdesk" msgstr "" @@ -316,7 +310,7 @@ msgstr "" msgid "To keep track of your course statistics, go to *eLearning* and *View Course*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 msgid "View of the elearning applications dashboard for Odoo Helpdesk" msgstr "" @@ -348,7 +342,7 @@ msgstr "" msgid "Setting up multiple teams allows you to group tickets by your channels (example: BE/US), or by your support services' types (example: IT, accounting, admin, etc.)." msgstr "" -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:None +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 msgid "View of the helpdesk teams page in Odoo Helpdesk" msgstr "" @@ -372,7 +366,7 @@ msgstr "" msgid "*Balanced*: tickets are assigned to the person with the least amount of tickets so that everyone fairly gets the same amount. Thereby, you ensure that all tickets get to be taken care of." msgstr "" -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:None +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 msgid "View of a helpdesk team settings page emphasizing the productivity and visibility features\n" "in Odoo Helpdesk" msgstr "" @@ -393,7 +387,7 @@ msgstr "" msgid "To set up stages, go to :menuselection:`Helpdesk --> Configuration --> Stages`. Then, create and/or edit stages as you need and set specific teams to use certain stages under *Team*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:None +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 msgid "View of a stage’s setting page emphasizing the option to add teams in Odoo Helpdesk" msgstr "" @@ -401,7 +395,7 @@ msgstr "" msgid "Stages can be shared between one or multiple teams, allowing you to adapt the pipeline to your individual needs. They also apply a visibility and access rule, as other teams are not able to see or use the stage." msgstr "" -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:None +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 msgid "View of a team’s kanban view in Odoo Helpdesk" msgstr "" @@ -421,7 +415,7 @@ msgstr "" msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Ratings on tickets*. The feature automatically adds a default email template on the non-folded *closing stage(s)* of that team." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:None +#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1 msgid "Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature\n" "in Odoo Helpdesk" msgstr "" @@ -430,7 +424,7 @@ msgstr "" msgid "To edit the email template and the stage(s) set as the closing ones, go to the Kanban view of your helpdesk team and click on *Settings*, then on *Edit Stage*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:None +#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1 msgid "Overview of a helpdesk team kanban view emphasizing the menu edit stage in Odoo Helpdesk" msgstr "" @@ -438,7 +432,7 @@ msgstr "" msgid "Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, an email is sent to the customer." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:None +#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1 msgid "View of a standard helpdesk customer review email template for Odoo Helpdesk" msgstr "" @@ -454,7 +448,7 @@ msgstr "" msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Display Rating on Customer Portal*. Now, by clicking on the helpdesk team’s name on their ticket, customers can see its ratings." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:None +#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1 msgid "View of the helpdesk ticket from a user’s portal emphasizing the link to the helpdesk team\n" "in Odoo Helpdesk" msgstr "" @@ -481,7 +475,7 @@ msgstr "" msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, and enable the following features as you want them to be available to your users." msgstr "" -#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:None +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1 msgid "View of a helpdesk teams setting page emphasizing the channels options in Odoo Helpdesk" msgstr "" @@ -497,7 +491,7 @@ msgstr "" msgid "Select *Configure domain name* to be redirected to *Settings* and, from there, enable *External Email Servers* to determine or change your *Alias Domain*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:None +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1 msgid "View of the settings page of a helpdesk team emphasizing the email alias feature\n" "in Odoo Helpdesk" msgstr "" @@ -518,7 +512,7 @@ msgstr "" msgid "Once the feature is activated, get redirected to your website by clicking on *Go to Website*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:None +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1 msgid "View of the settings page of a helpdesk team emphasizing the Go to Website button in\n" "Odoo Helpdesk" msgstr "" @@ -527,7 +521,7 @@ msgstr "" msgid "From the website page customize the form as you like. Then, publish it by clicking on *Unpublished*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:None +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1 msgid "View of the website form to submit a ticket for Odoo Helpdesk" msgstr "" @@ -540,16 +534,16 @@ msgid "Through live interactions with your website visitors, helpdesk tickets ca msgstr "" #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:61 -msgid "Click on your helpdesk team's name - for the example below: *Customer Care* - and :doc:`set up your channel `." +msgid "Click on your helpdesk team's name - for the example below: *Customer Care* - and :doc:`set up your channel `." msgstr "" -#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:None +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1 msgid "View of the settings page of a helpdesk team emphasizing the live chat features and links\n" "in Odoo Helpdesk" msgstr "" #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:68 -msgid "Now, your operators can create tickets by using the :doc:`command ` */helpdesk (subject_of_ticket)*." +msgid "Now, your operators can create tickets by using the :doc:`command ` */helpdesk (subject_of_ticket)*." msgstr "" #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:72 @@ -572,7 +566,7 @@ msgstr "" msgid "3 stars = *Urgent*" msgstr "" -#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:None +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1 msgid "View of a team’s kanban view and the prioritized tasks in Odoo Helpdesk" msgstr "" @@ -613,7 +607,7 @@ msgstr "" msgid "Apply *Time Ranges* if you would like to make comparisons to a *Previous Period* or a *Previous Year*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:None +#: ../../content/applications/services/helpdesk/overview/reports.rst:-1 msgid "View of a helpdesk ticket analysis by team and ticket type in Odoo Helpdesk" msgstr "" @@ -625,7 +619,7 @@ msgstr "" msgid "Get an overview of how many requests each team is closing per day in order to measure their performance. Identify productivity levels to understand how many requests they are able to handle." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:None +#: ../../content/applications/services/helpdesk/overview/reports.rst:-1 msgid "View of a helpdesk ticket analysis by team and close date in Odoo Helpdesk" msgstr "" @@ -641,7 +635,7 @@ msgstr "" msgid "Check if your expectations are met by *measuring* the *Time to close (hours)*. Your customers not only expect fast responses but they also want their issues to be handled quickly." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:None +#: ../../content/applications/services/helpdesk/overview/reports.rst:-1 msgid "View of helpdesk ticket analysis of the hours to close by ticket type and team in\n" "Odoo Helpdesk" msgstr "" @@ -654,7 +648,7 @@ msgstr "" msgid "Save the filters you use the most and avoid having to reconstruct them every time they are needed. To do so, set the groups, filters, and measures needed. Then, go to *Favorites*." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:None +#: ../../content/applications/services/helpdesk/overview/reports.rst:-1 msgid "View of helpdesk ticket analysis emphasizing the option to add a filter as a favorite one\n" "in Odoo Helpdesk" msgstr "" @@ -683,7 +677,7 @@ msgstr "" msgid "Create your policies through the team’s settings page or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:None +#: ../../content/applications/services/helpdesk/overview/sla.rst:-1 msgid "View of an SLA form in Odoo Helpdesk" msgstr "" @@ -699,7 +693,7 @@ msgstr "" msgid "When a ticket has satisfied an SLA policy, the SLA tag appears in green and the deadline field is not shown anymore." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:None +#: ../../content/applications/services/helpdesk/overview/sla.rst:-1 msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk" msgstr "" @@ -711,7 +705,7 @@ msgstr "" msgid "Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply *Filters* and *Group by* to identify tickets that should be prioritized and keep track of upcoming deadlines." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:None +#: ../../content/applications/services/helpdesk/overview/sla.rst:-1 msgid "View of the SLA status analysis page emphasizing the group by option in Odoo Helpdesk" msgstr "" @@ -739,7 +733,7 @@ msgstr "" msgid "Select or create a project under *Timesheet on Ticket*. The selected/created is the one at which employees timesheet on by default. However, it can be ultimately modified on each ticket." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1 msgid "View of a helpdesk team settings page emphasizing the timesheet on ticket and time\n" "reinvoicing features in Odoo Helpdesk" msgstr "" @@ -756,7 +750,7 @@ msgstr "" msgid "Then, go to :menuselection:`Sales --> Products --> Products`, create or edit an existing one, and set its *Product Type* as *Service*." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1 msgid "View of a product's form emphasizing the product type and unit of measure fields in Odoo\n" "Sales" msgstr "" @@ -765,7 +759,7 @@ msgstr "" msgid "Now, select the invoicing management you would like to have under the *Sales* tab. We recommend the following configuration:" msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1 msgid "View of a product form and the invoicing options under the tab sales in Odoo Sales" msgstr "" @@ -789,7 +783,7 @@ msgstr "" msgid "Go to :menuselection:`Sales --> Orders --> Orders` and create one for the helpdesk service product you have previously set up, with the customer who needs the ticket to be opened. Set the number of hours needed to assist the customer and *Confirm* the order." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1 msgid "View of a sales order emphasizing the order lines in Odoo Sales" msgstr "" @@ -801,7 +795,7 @@ msgstr "" msgid "In *Sales*, select the respective sales order to *Create Invoice*." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1 msgid "View of a sales order emphasizing the create invoice button in Odoo Sales" msgstr "" @@ -813,7 +807,7 @@ msgstr "" msgid "Now, in *Helpdesk*, create or edit the respective ticket and link it to the task created by the confirmation of the sales order." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1 msgid "View of a helpdesk ticket emphasizing the field task in Odoo Helpdesk" msgstr "" @@ -825,7 +819,7 @@ msgstr "" msgid "Still on the respective helpdesk ticket, record the hours performed under the *Timesheets* tab." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1 msgid "View of a helpdesk ticket emphasizing the timesheets tab in Odoo Helpdesk" msgstr "" @@ -833,7 +827,7 @@ msgstr "" msgid "Note that the hours recorded on the ticket form are shown on the *Delivered* column in the sales order." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1 msgid "View of a sales order emphasizing the delivered column in Odoo Sales" msgstr "" @@ -894,7 +888,7 @@ msgstr "" msgid "Once the product is added, click :guilabel:`Confirm` to turn the quotation into a sales order." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:-1 msgid "Create a sales order and add a product." msgstr "" @@ -906,7 +900,7 @@ msgstr "" msgid "To record a timesheet, jump back to the Helpdesk ticket by going to the Helpdesk dashboard and clicking :guilabel:`Tickets` on the team's card (or by going to the Projects dashboard and clicking :guilabel:`Tickets` on the project card). Then, click :guilabel:`Edit` and use the :guilabel:`Timesheets` tab to record the time spent on the ticket." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:-1 msgid "Record time spent on a ticket." msgstr "" @@ -922,7 +916,7 @@ msgstr "" msgid "Once a timesheet is recorded, the :guilabel:`Sales Order Item` field will appear on the ticket form. To link the :abbr:`SO (Sales Order)` to the ticket, start on the ticket form and click :guilabel:`Edit`. Next, select the :abbr:`SO (Sales Order)` that was created earlier from the drop-down menu. Odoo will automatically filter the sales orders to only show sales orders that are connected to the ticket's customer. Lastly, click :guilabel:`Save` to connect the ticket and the :abbr:`SO (Sales Order)`." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:None +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:-1 msgid "Link the SO item to the ticket." msgstr "" @@ -999,7 +993,7 @@ msgstr "" msgid "In addition, you can now directly set it when creating a new project." msgstr "" -#: ../../content/applications/services/project/tasks/email_alias.rst:None +#: ../../content/applications/services/project/tasks/email_alias.rst:-1 msgid "In the settings of your project, define the emails alias under the tab email in Odoo Project" msgstr "" @@ -1011,7 +1005,7 @@ msgstr "" msgid "The email can be seen under the name of your project on the dashboard." msgstr "" -#: ../../content/applications/services/project/tasks/email_alias.rst:None +#: ../../content/applications/services/project/tasks/email_alias.rst:-1 msgid "View of the email alias chosen on the dashboard view in Odoo Project" msgstr "" @@ -1031,7 +1025,7 @@ msgstr "" msgid "Activate the :ref:`developer mode `, go to *Timesheets*, and change the *Project* and *Task* set by default, if you like." msgstr "" -#: ../../content/applications/services/timesheets/overview/time_off.rst:None +#: ../../content/applications/services/timesheets/overview/time_off.rst:-1 msgid "View of Timesheets setting enabling the feature record time off in Odoo Timesheets" msgstr "" @@ -1039,7 +1033,7 @@ msgstr "" msgid "Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select or create the needed type, and decide if you would like the requests to be validated or not." msgstr "" -#: ../../content/applications/services/timesheets/overview/time_off.rst:None +#: ../../content/applications/services/timesheets/overview/time_off.rst:-1 msgid "View of a time off types form emphasizing the time off requests and timesheets section in\n" "Odoo Time Off" msgstr "" @@ -1052,7 +1046,7 @@ msgstr "" msgid "On the example below, the user requested *Paid Time off* from July 13th to 15th." msgstr "" -#: ../../content/applications/services/timesheets/overview/time_off.rst:None +#: ../../content/applications/services/timesheets/overview/time_off.rst:-1 msgid "View of the time off request form in Odoo Time Off" msgstr "" @@ -1060,7 +1054,7 @@ msgstr "" msgid "Considering that validation is not required, the requested time off is automatically displayed in *Timesheets*. If validation is necessary, the time is automatically allocated after the responsible person for validating does it so." msgstr "" -#: ../../content/applications/services/timesheets/overview/time_off.rst:None +#: ../../content/applications/services/timesheets/overview/time_off.rst:-1 msgid "Video of timesheets emphasizing the requested time off from the employee in Odoo Timesheets" msgstr "" @@ -1068,7 +1062,7 @@ msgstr "" msgid "Click on the magnifying glass, hovering over the concerned cell, to access all the aggregated data on that cell (day), and see details regarding the project/task." msgstr "" -#: ../../content/applications/services/timesheets/overview/time_off.rst:None +#: ../../content/applications/services/timesheets/overview/time_off.rst:-1 msgid "View of the details of a project/task in Odoo Timeheets" msgstr "" @@ -1116,42 +1110,54 @@ msgstr "" msgid "*Odoo Support does not make changes to your production database without your agreement and gives you the material and knowledge to do it yourself!*" msgstr "" -#: ../../content/services/support/what_can_i_expect.rst:38 -msgid "What kind of support is not included?" +#: ../../content/services/support/what_can_i_expect.rst:37 +msgid ":ref:`upgrade/sla`" msgstr "" -#: ../../content/services/support/what_can_i_expect.rst:40 -msgid "Questions that require us to understand your business processes in order to help you implement your database" +#: ../../content/services/support/what_can_i_expect.rst:38 +msgid ":doc:`/administration/maintain/supported_versions`" msgstr "" #: ../../content/services/support/what_can_i_expect.rst:42 -msgid "Training on how to use our software (we will direct you to our many resources)" -msgstr "" - -#: ../../content/services/support/what_can_i_expect.rst:43 -msgid "Import of documents into your database" +msgid "What kind of support is not included?" msgstr "" #: ../../content/services/support/what_can_i_expect.rst:44 -msgid "Guidance on which configurations to apply inside of an application or the database" +msgid "Questions that require us to understand your business processes in order to help you implement your database" msgstr "" -#: ../../content/services/support/what_can_i_expect.rst:45 -msgid "How to set up configuration models (Examples include: Inventory Routes, Payment Terms, Warehouses, etc)" +#: ../../content/services/support/what_can_i_expect.rst:46 +msgid "Training on how to use our software (we will direct you to our many resources)" msgstr "" #: ../../content/services/support/what_can_i_expect.rst:47 -msgid "Any intervention on your own servers/deployments of Odoo" +msgid "Import of documents into your database" msgstr "" #: ../../content/services/support/what_can_i_expect.rst:48 -msgid "Any intervention on your own third party account (Ingenico, Authorize, UPS, etc)" +msgid "Guidance on which configurations to apply inside of an application or the database" msgstr "" #: ../../content/services/support/what_can_i_expect.rst:49 -msgid "Questions or issues related to specific developments or customizations done either by Odoo or a third party (this is specific only to your database or involving code)" +msgid "How to set up configuration models (Examples include: Inventory Routes, Payment Terms, Warehouses, etc)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:51 +msgid "Any intervention on your own servers/deployments of Odoo" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:52 +msgid "Any intervention on your own third party account (Ingenico, Authorize, UPS, etc)" msgstr "" #: ../../content/services/support/what_can_i_expect.rst:53 +msgid "Questions or issues related to specific developments or customizations done either by Odoo or a third party (this is specific only to your database or involving code)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:57 msgid "You can get this type of support with a `Success Pack `__. With a pack, one of our consultants will analyze the way your business runs and tell you how you can get the most out of your Odoo Database. We will handle all configurations and coach you on how to use Odoo." msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:63 +msgid ":doc:`/administration/upgrade`" +msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index c53c75ee9..b488a0bc8 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-02 07:38+0000\n" +"POT-Creation-Date: 2023-07-06 05:52+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -132,7 +132,7 @@ msgid ":doc:`../maximizing_revenue/pricing`" msgstr "" #: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:31 -msgid ":doc:`../../website/optimize/seo`" +msgid ":doc:`../../website/pages/seo`" msgstr "" #: ../../content/applications/websites/ecommerce/managing_products.rst:5 @@ -215,7 +215,7 @@ msgstr "" msgid "Don't forget to hit *Save* once all variants have been entered." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 msgid "ecommerce product variants values" msgstr "" @@ -227,7 +227,7 @@ msgstr "" msgid "After you hit *Save*, you are able to see all the variants from the product template detail form via the *Variants* smart button." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 msgid "ecommerce product variants smart button" msgstr "" @@ -271,7 +271,7 @@ msgstr "" msgid "You can set a specific public price per variant by clicking on *Configure Variants* in the product detail form (top-left corner). That takes you to the *Product Variant Values* page for that product." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 msgid "ecommerce product variants configure variants" msgstr "" @@ -283,7 +283,7 @@ msgstr "" msgid "The *Value Price Extra* field represents the monetary value that is added to the original product price whenever the corresponding attribute value is selected." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 msgid "ecommerce value price extra" msgstr "" @@ -291,7 +291,7 @@ msgstr "" msgid "This is how the *Value Price Extra* looks on your website:" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 msgid "ecommerce value price extra on the frontend" msgstr "" @@ -307,7 +307,7 @@ msgstr "" msgid "You can disable/archive specific variants so they are no longer available in quotes or on your website (not existing in your stock, deprecated, etc.). Simply select *Archive* in their detail form. You can reactivate them the same way." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 msgid "ecommerce product variants archive" msgstr "" @@ -315,7 +315,7 @@ msgstr "" msgid "To retrieve such items, hit *Archived* in the *Filters* category while searching the variants list." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 msgid "ecommerce product variants archive search" msgstr "" @@ -445,7 +445,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:9 #: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:13 -#: ../../content/applications/websites/website/publish/multi_website.rst:18 +#: ../../content/applications/websites/website/configuration/multi_website.rst:18 msgid "Setup" msgstr "" @@ -577,7 +577,7 @@ msgstr "" msgid "Once you are on the Sales Order page, you will find the payment is confirmed with an automatic note in the *Chatter*." msgstr "" -#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:None +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:-1 msgid "payment is confirmed in the chatter of sales order" msgstr "" @@ -585,7 +585,7 @@ msgstr "" msgid "If the user decides to create an invoice, the payment is directly reconciled. This note in the *Chatter* includes a link to the Payment entry, which contains various details about the transaction, along with a link to the related Journal Entry." msgstr "" -#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:None +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:-1 msgid "page with details surrounding the specific transaction" msgstr "" @@ -617,7 +617,7 @@ msgstr "" msgid "Then activate *Automatic Invoices* and *Save*." msgstr "" -#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:None +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:-1 msgid "example of automatic invoice" msgstr "" @@ -673,257 +673,254 @@ msgstr "" msgid "Collect taxes" msgstr "" -#: ../../content/applications/websites/livechat.rst:8 +#: ../../content/applications/websites/livechat.rst:6 msgid "Live Chat" msgstr "" -#: ../../content/applications/websites/livechat.rst:11 -msgid "`Live Chat: product page `_" -msgstr "" - -#: ../../content/applications/websites/livechat/overview.rst:5 -#: ../../content/applications/websites/website/publish/translate.rst:6 -msgid "Overview" -msgstr "" - -#: ../../content/applications/websites/livechat/overview/get_started.rst:3 -msgid "Get Started with Live Chat" -msgstr "" - -#: ../../content/applications/websites/livechat/overview/get_started.rst:5 +#: ../../content/applications/websites/livechat.rst:8 msgid "Live Chat has the highest satisfaction rating of any communication tool. It allows fast responses and it is accessible and convenient, as your customers can keep doing what they are doing while interacting with you. Remember: your customers want to talk to you, so let's make it easy." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:10 +#: ../../content/applications/websites/livechat.rst:13 +msgid "`Live Chat: product page `_" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:14 +msgid ":doc:`livechat/ratings`" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:15 +msgid ":doc:`livechat/responses`" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:18 msgid "Set up" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:12 +#: ../../content/applications/websites/livechat.rst:20 msgid "Once *Live Chat* is installed on your database, if your website was created with Odoo, the application is automatically added to it. All that is left to do is to go to :menuselection:`Website --> Configuration --> Settings --> Live Chat`." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:None +#: ../../content/applications/websites/livechat.rst:-1 msgid "View of the settings page and the live chat feature for Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:21 +#: ../../content/applications/websites/livechat.rst:28 msgid "Select the channel to be linked to your website or create one on the fly." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:None +#: ../../content/applications/websites/livechat.rst:-1 msgid "View of a live chat channel form for Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:27 +#: ../../content/applications/websites/livechat.rst:33 msgid "For both scenarios, under:" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:30 +#: ../../content/applications/websites/livechat.rst:36 msgid "- **Operators**: add agents to respond to the chat requests. Add as many as you like, and keep in mind that operators that do not show any activity in Odoo for more than 30min are considered disconnected." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:33 +#: ../../content/applications/websites/livechat.rst:39 msgid "- **Options**: set the default text to be shown on the live chat button; an automated welcome message to be seen by visitors when a conversation is initiated, and the text that prompts the user to initiate a chat." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:36 +#: ../../content/applications/websites/livechat.rst:42 msgid "- **Channel Rules**: choose an action for a given URL, and/or per country. In the example below, the chat window automatically pops-up 3 seconds after users (from any country) land on the contact us page." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:None +#: ../../content/applications/websites/livechat.rst:-1 msgid "View of a channel’s rules form for Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:43 +#: ../../content/applications/websites/livechat.rst:48 msgid "GeoIP, which refers to the process of finding a computer terminal’s geographical location by its IP address, must be installed on your server. Otherwise, under *Channel Rules*, countries are not taken into account." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:48 +#: ../../content/applications/websites/livechat.rst:53 msgid "External options" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:51 +#: ../../content/applications/websites/livechat.rst:56 msgid "If your website was not created with Odoo, you can find the code to be added to your own, under the *Widget* tab." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:52 +#: ../../content/applications/websites/livechat.rst:57 msgid "Odoo also offers an URL you can send to users so they can have access to a single live chat page." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:None +#: ../../content/applications/websites/livechat.rst:-1 msgid "View of the widget tab for Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:59 +#: ../../content/applications/websites/livechat.rst:63 msgid "Managing chat requests" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:61 +#: ../../content/applications/websites/livechat.rst:65 msgid "Conversations initiated by visitors pop up as a direct message, and are shown in *Discuss*. Therefore, inquiries can be answered wherever you are in Odoo." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:None +#: ../../content/applications/websites/livechat.rst:-1 msgid "View of the discuss application with a message sent through live chat in Odoo" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:69 +#: ../../content/applications/websites/livechat.rst:72 msgid "Conversations are dispatched based on the current workload of the online operators." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:72 +#: ../../content/applications/websites/livechat.rst:75 msgid "Leave or join a channel" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:74 +#: ../../content/applications/websites/livechat.rst:77 msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel under *Live Chat*, and *Join Channel* or *Leave Channel*." msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:None +#: ../../content/applications/websites/livechat.rst:-1 msgid "View of a channel form and the option to join a channel for Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/get_started.rst:82 -#: ../../content/applications/websites/livechat/overview/responses.rst:48 -msgid ":doc:`ratings`" -msgstr "" - -#: ../../content/applications/websites/livechat/overview/get_started.rst:83 -#: ../../content/applications/websites/livechat/overview/ratings.rst:45 -msgid ":doc:`responses`" -msgstr "" - -#: ../../content/applications/websites/livechat/overview/ratings.rst:3 +#: ../../content/applications/websites/livechat/ratings.rst:3 msgid "Ratings" msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:5 +#: ../../content/applications/websites/livechat/ratings.rst:5 msgid "Giving users the opportunity to rate their interactions can help you improving the experience you offer. That means staying on top of your customers' needs, besides keeping track of your operators’ performances." msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:10 +#: ../../content/applications/websites/livechat/ratings.rst:10 msgid "Customer Rating" msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:12 +#: ../../content/applications/websites/livechat/ratings.rst:12 msgid "Once the user chooses to close the chat window, he can rate his interaction." msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:14 +#: ../../content/applications/websites/livechat/ratings.rst:14 msgid "If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing for an explanation is shown." msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:15 +#: ../../content/applications/websites/livechat/ratings.rst:15 msgid "A copy of the conversation can also be sent by email." msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:None +#: ../../content/applications/websites/livechat/ratings.rst:-1 msgid "View of the chat window from a user’s side for Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:22 +#: ../../content/applications/websites/livechat/ratings.rst:22 msgid "The rating is shown on the chat window itself for the operator." msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:None +#: ../../content/applications/websites/livechat/ratings.rst:-1 msgid "View of a chat window from an operator’s side highlighting a rating for Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:28 +#: ../../content/applications/websites/livechat/ratings.rst:28 msgid "And under :menuselection:`Report --> Customer Ratings`." msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:None +#: ../../content/applications/websites/livechat/ratings.rst:-1 msgid "View of the customer ratings page in Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:35 +#: ../../content/applications/websites/livechat/ratings.rst:35 msgid "Make the rating public" msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:37 +#: ../../content/applications/websites/livechat/ratings.rst:37 msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel form, click on *Go to Website* and on *Unpublished*, to publish the rating of that channel on your website." msgstr "" -#: ../../content/applications/websites/livechat/overview/ratings.rst:None +#: ../../content/applications/websites/livechat/ratings.rst:-1 msgid "View of the public ratings in the website for Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:3 +#: ../../content/applications/websites/livechat/ratings.rst:45 +msgid ":doc:`responses`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:3 msgid "Commands and Canned Responses" msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:5 +#: ../../content/applications/websites/livechat/responses.rst:5 msgid "Using canned responses can help you save time and have a previous, well-thought response, to some of your most common questions and comments." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:9 +#: ../../content/applications/websites/livechat/responses.rst:9 msgid "Use commands" msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:11 +#: ../../content/applications/websites/livechat/responses.rst:11 msgid "Commands are shortcuts that do specific actions within the chat window:" msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:13 +#: ../../content/applications/websites/livechat/responses.rst:13 msgid "**/help**: shows a help message." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:14 +#: ../../content/applications/websites/livechat/responses.rst:14 msgid "**/helpdesk**: creates a helpdesk ticket." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:15 +#: ../../content/applications/websites/livechat/responses.rst:15 msgid "**/helpdesk_search**: searches for a helpdesk ticket." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:16 +#: ../../content/applications/websites/livechat/responses.rst:16 msgid "**/history**: shows the last 15 visited pages." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:17 +#: ../../content/applications/websites/livechat/responses.rst:17 msgid "**/lead**: creates a new lead." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:18 +#: ../../content/applications/websites/livechat/responses.rst:18 msgid "**/leave**: leaves the channel." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:0 +#: ../../content/applications/websites/livechat/responses.rst:0 msgid "- For *helpdesk tickets*: make sure the application is installed on your database and the option *Live Chat* under :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` is enabled." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:0 +#: ../../content/applications/websites/livechat/responses.rst:0 msgid "- For *leads*: the *CRM* application must be installed on your database." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:26 +#: ../../content/applications/websites/livechat/responses.rst:26 msgid "To access the ticket or lead created from the chat, click on the shortcut link." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:None +#: ../../content/applications/websites/livechat/responses.rst:-1 msgid "View of the chat window with a helpdesk ticket created in Odoo Live Chat" msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:33 +#: ../../content/applications/websites/livechat/responses.rst:33 msgid "Helpdesk tickets created from the chat automatically add the conversation as a description of the ticket. The same goes for the creation of a lead." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:37 +#: ../../content/applications/websites/livechat/responses.rst:37 msgid "Send canned responses" msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:40 +#: ../../content/applications/websites/livechat/responses.rst:40 msgid "Canned responses allow you to have a full piece of text being placed when you type a shortcut word. To create them, go to :menuselection:`Live Chat --> Configuration --> Canned Responses`." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:41 +#: ../../content/applications/websites/livechat/responses.rst:41 msgid "To use them during a conversation, simply type **:** followed by the shortcut word you created." msgstr "" -#: ../../content/applications/websites/livechat/overview/responses.rst:None +#: ../../content/applications/websites/livechat/responses.rst:-1 msgid "View of a chat window and the use of a canned response in Odoo Live Chat" msgstr "" +#: ../../content/applications/websites/livechat/responses.rst:48 +msgid ":doc:`ratings`" +msgstr "" + #: ../../content/applications/websites/website.rst:8 msgid "Website" msgstr "" @@ -932,1414 +929,1415 @@ msgstr "" msgid "Discover the best **Open-Source Website Builder** and learn how to build beautiful websites that convert visitors into leads or revenues." msgstr "" -#: ../../content/applications/websites/website/optimize.rst:5 -msgid "Optimize" -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:3 -msgid "How to track your website's traffic in Google Analytics" -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:6 -msgid "Google deprecated **Universal Analytics** which won't be supported anymore in `July 2023 `_. They are replacing it with **Analytics 4**." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:10 -msgid "New accounts are already using it, but accounts created before `October 2020 `_ are most likely still using **Universal Analytics**." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:14 -msgid "Odoo 15.0 is already adapted and ready for **Analytics 4**. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:19 -msgid "To follow your website's traffic with Google Analytics:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:21 -msgid "`Create a Google Analytics account `__ if you don't have any." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:24 -msgid "Go through the creation form and accept the conditions to get the tracking ID." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:29 -msgid "Copy the tracking ID to insert it in Odoo." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:34 -msgid "Go to the *Configuration* menu of your Odoo's Website app. In the settings, turn on Google Analytics and paste the tracking ID. Then save the page." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:41 -msgid "To make your first steps in Google Analytics, refer to `Google Documentation `_." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics.rst:46 -msgid ":doc:`google_analytics_dashboard`" -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:3 -msgid "How to track your website traffic from your Odoo Dashboard" -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:6 -msgid "It is not possible anymore for new Google Analytics accounts to integrate their **Google Analytics Dashboard** inside their **Odoo Dashboard**. Google deprecated **Universal Analytics** which won't be supported anymore in `July 2023 `_. They are replacing it with **Analytics 4**. New accounts are already using it." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:12 -msgid "**Analytics 4** `doesn't allow `_ its dashboard to be integrated in external websites." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:15 -msgid "You now have to check your Analytics data directly in the Google Platform as it won't be possible in Odoo anymore." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:18 -msgid "Accounts created before `October 2020 `_ should still be using **Universal Analytics** and be able to integrate their dashboard on external website until the official end of support `around mid 2023 `_." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:23 -msgid "You can follow your traffic statistics straight from your Odoo Website Dashboard thanks to Google Analytics." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:26 -msgid "A preliminary step is creating a Google Analytics account and entering the tracking ID in your Website's settings (see :doc:`google_analytics`)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:29 -msgid "Go to `Google APIs platform `__ to generate Analytics API credentials. Log in with your Google account." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:32 -msgid "Select Analytics API." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:37 -msgid "Create a new project and give it a name (e.g. Odoo). This project is needed to store your API credentials." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:43 -msgid "Enable the API." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:48 -msgid "Create credentials to use in Odoo." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:53 -msgid "Select *Web browser (Javascript)* as calling source and *User data* as kind of data." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:59 -msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:69 -msgid "Go through the Consent Screen step by entering a product name (e.g. Google Analytics in Odoo). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:74 -msgid "Finally you are provided with your Client ID. Copy and paste it in Odoo." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:79 -msgid "Open your Website Dashboard in Odoo and link your Analytics account to past your Client ID." -msgstr "" - -#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:85 -msgid "As a last step, authorize Odoo to access Google API." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:3 -msgid "Track clicks and visitors using Link Trackers" -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:5 -msgid "Link Trackers allow you to track your marketing campaigns (emails, banner ads, blog posts, social media posts, affiliate links, etc.). This way, you are able to identify your best traffic sources and make informed decisions about the distribution of your marketing budget." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:10 +#: ../../content/applications/websites/website/configuration.rst:5 +#: ../../content/applications/websites/website/reporting/link_tracker.rst:10 msgid "Configuration" msgstr "" -#: ../../content/applications/websites/website/optimize/link_tracker.rst:12 -msgid "Go to :menuselection:`Website --> Configuration --> Settings` and activate *Link Trackers*." +#: ../../content/applications/websites/website/configuration/multi_website.rst:3 +msgid "Multiple websites" msgstr "" -#: ../../content/applications/websites/website/optimize/link_tracker.rst:None -msgid "View of Website settings page emphasizing the link trackers field in Odoo Website" -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:19 -msgid "Set up traceable URLs" -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:21 -msgid "Go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Here, you are able to get a specific tracked URL based on the campaign, medium, and source being used." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:None -msgid "View of the link tracker fields for Odoo Website" -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:28 -msgid "**URL**: url of the page you want to track (e.g. the home page or a product's page)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:29 -msgid "**Campaign**: context of your link (e.g. a special promotion)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:30 -msgid "**Medium**: channel used to share (deliver) your link (e.g. an email or a Facebook ad)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:31 -msgid "**Source**: platform where the traffic originates (e.g. Google or Twitter)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:33 -msgid "Now, click on *Get tracked link* to generate a URL that you can post or send by the source you have decided on." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:37 -msgid "Follow-up on tracked links" -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:39 -msgid "To look at statistics of your links, go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Besides being able to see the *Most Clicked* and *Recently Used* links, you can also see complete statistics by clicking on *Stats*, including the number of clicks, and the country of origin for those clicks." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:None -msgid "View of the tracked list emphasizing the statistics buttons in Odoo Website" -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:50 -msgid "You can also access the link tracker on *odoo.com/r* via your browser." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:51 -msgid "Activate the developer mode (:menuselection:`Settings --> Activate the developer mode`) and get access to the *Link Tracker* module and its back-end functionalities." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:53 -msgid "Integrated with :doc:`Google Analytics `, those trackers allow you to see the number of clicks and visitors to keep you on top of your marketing campaigns." -msgstr "" - -#: ../../content/applications/websites/website/optimize/link_tracker.rst:55 -msgid "The integration with the :doc:`CRM ` application allows you to understand where your leads and opportunities are coming from." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:3 -msgid "How to do Search Engine Optimisation (SEO) in Odoo" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:5 -msgid "Search Engine Optimization (SEO) is a set of good practices to optimize your website so that you get a better ranking in search engines like Google. In short, a good SEO allows you to get more visitors." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:9 -msgid "Some examples of SEO rules: your web pages should load fast, your page should have one and only one title ``

``, meta tags (alt-tag, title-tag) should be consistent with the content, your website should have a ``/sitemap.xml`` file, etc." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:15 -msgid "To guarantee Odoo Website and Odoo eCommerce users have a great SEO, Odoo abstracts all the technical complexities of SEO and handles everything for you, in the best possible way. This will be explained here below." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:20 -msgid "But first, let see how you can easily boost your ranking by finetuning the content and the meta tags of your website." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:24 -msgid "Meta Tags" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:27 -msgid "Title, Description" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:29 -msgid "Every web page should define the ```` and ``<description>`` meta data. These information elements are used by search engines to promote your website. They are automatically generated based on page title & content, but you can finetune them. Make sure they fit the content of the page, otherwise you will be downgraded by search engines." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:39 -msgid "Keywords" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:41 -msgid "In order to write quality content and boost your traffic, Odoo provides a ``<keyword>`` finder. Those keywords are the searches you want to head towards your website. For each keyword, you see how it is used in the content (H1, H2, page title, page description, page content) and what are the related searches in Google. The more keywords are used the better." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:51 -msgid "If your website is in multiple languages, you can use the Promote tool for every language of a single page and set specific title, description and search tags." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:56 -msgid "Content is King" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:58 -msgid "When it comes to SEO, content is usually king. Odoo provides several modules to help you build your website content:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:61 -msgid "**Odoo Blogs**: write great contents." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:63 -msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:67 -msgid "**Odoo Forum**: let your community create contents for you. Example: `odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com landing pages)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:71 -msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:77 -msgid "The 404 page is a regular page, that you can edit like any other page in Odoo. That way, you can build a great 404 page to redirect to the top content of your website when visitors get lost in invalid URLs." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:82 -msgid "Use Social Networks" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:84 -msgid "Social media is built for mass sharing. If lots of people share your content on social media, then it's likely more people will link to it, and links are a huge factor for SEO ranking." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:88 -msgid "Odoo embeds several tools to share content through social media:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:91 -msgid "Social Network" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:93 -msgid "Odoo allows to link all your social network accounts in your website footer. All you have to do is to refer all your accounts in your company settings." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:100 -msgid "Social Share" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:102 -msgid "Drop the building block *Share* on any page you want your visitors to share. By clicking the icon, they are prompted to share the page in their social media wall." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:109 -msgid "Most social media use a picture of the picture to decorate the share post. Odoo uses the website logo by default but you can choose any other image of your page in the Promote tool." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:117 -msgid "Facebook Page" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:119 -msgid "Drop the building block *Facebook Page* to display a widget of your Facebook business page and encourage visitors to follow it. You can display the timeline, the next events and the messages." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:124 -msgid "Twitter Scroller" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:126 -msgid "Display the Twitter feeds with customer satifaction on your website. This will increase the number of tweets and shares." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:130 -msgid "Test Your Website" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:132 -msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `woorank.com <https://www.woorank.com>`_" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:137 -msgid "URLs Handling" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:139 -msgid "This section sheds some light on how Odoo makes URLs SEO-friendly." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:142 -msgid "URLs Structure" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:144 -msgid "A typical Odoo URL will look like this:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:146 -msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:148 -msgid "With the following components:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:150 -msgid "**https://** = Protocol" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:152 -msgid "**www.mysite.com** = your domain name" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:154 -msgid "**/fr\\_FR** = page language. This part of the URL is removed if the visitor browses the main language of the website Thus, the main version of this page is: https://www.mysite.com/shop/product/my-great-product-31" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:159 -msgid "**/shop/product** = every module defines its own namespace (/shop is for the catalog of the eCommerce module, /shop/product is for a product page)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:163 -msgid "**my-great-product** = by default, this is the slugified title of the product this page refers to. But you can customize it for SEO purposes. A product named \"Pain carré\" will be slugified to \"pain-carre\". Depending on the namespace, this could be different objects (blog post, page title, forum post, forum comment, product category, etc.)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:170 -msgid "**-31** = the unique ID of the product" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:172 -msgid "Note that any dynamic component of an URL can be reduced to its ID. As an example, the following URLs all do a 301 redirect to the above URL:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:175 -msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:177 -msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:179 -msgid "http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product name)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:182 -msgid "Some URLs have several dynamic parts, like this one (a blog category and a post):" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:185 -msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:187 -msgid "In the above example:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:189 -msgid "*Company News* is the title of the blog" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:191 -msgid "*The Odoo Story* is the title of a specific blog post" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:193 -msgid "When an Odoo page has a pager, the page number is set directly in the URL (does not have a GET argument). This allows every page to be indexed by search engines. Example:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:197 -msgid "https://www.odoo.com/blog/page/3" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:200 -msgid "Changes in URLs & Titles" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:202 -msgid "When the URL of a page changes (e.g. a more SEO friendly version of your product name), you don't have to worry about updating all links:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:205 -msgid "Odoo will automatically update all its links to the new URL." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:207 -msgid "If external websites still points to the old URL, a 301 redirect will be done to route visitors to the new address of the page." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:210 -msgid "As an example, this URL:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:212 -msgid "http://mysite.com/shop/product/old-product-name-31" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:214 -msgid "Will automatically redirect to:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:216 -msgid "http://mysite.com/shop/product/new-and-better-product-name-31" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:218 -msgid "In short, just change the title of a blog post or the name of a product, and the changes will apply automatically everywhere in your website. The old link still functions when used by external websites, via a 301 redirect, maintaining the SEO link juice." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:224 -msgid "HTTPS" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:226 -msgid "Search engines boost ranking of secure HTTPS/SSL websites. So, by default all Odoo Online instances are fully based on HTTPS. If the visitor accesses your website through a non HTTPS url, it gets a 301 redirect to its HTTPS equivalent." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:232 -msgid "Links: Nofollow Strategy" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:234 -msgid "The more a page is linked from external and quality websites, the better it is for your SEO." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:237 -msgid "Here are Odoo strategies to manage links:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:239 -msgid "Every link you add to your website is \"dofollow\", which means that this link will contribute to the SEO Juice for the linked page." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:243 -msgid "Every link posted by a contributor (forum post, blog comment, etc.) that links to your own website is \"dofollow\" too." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:246 -msgid "But every link posted by a contributor that links to an external website is \"nofollow\". In that way, you do not run the risk of people posting links on your website to third-party websites which have a bad reputation." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:251 -msgid "Note that, when using the forum, contributors having a lot of Karma can be trusted. In such case, their links will not have any ``rel=\"nofollow\"`` attribute." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:256 -msgid "Multi-Language Support" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:259 -msgid "Multi-Language URLs" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:261 -msgid "If you run a website in multiple languages, the same content will be available in different URLs, depending on the language used:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:264 -msgid "https://www.mywebsite.com/shop/product/my-product-1 (main language, English here)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:266 -msgid "https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French version)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:268 -msgid "In this example, fr\\_FR is the language of the page. You can even have several variations of the same language: pt\\_BR (Portuguese from Brazil) , pt\\_PT (Portuguese from Portugal)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:273 -msgid "Language Annotation" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:275 -msgid "To let search engines know that the second URL is the French translation of the first URL, Odoo will add an HTML link element in the header. In the HTML <head> section of the main version, Odoo automatically adds a link element pointing to the translated versions of that webpage;" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:280 -msgid "<link rel=\"alternate\" hreflang=\"fr\" href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:283 -msgid "With this approach:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:285 -msgid "Search engines will redirect to the right language according to the visitor language." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:288 -msgid "You do not get penalized by search engines if your page is not translated yet. Indeed, it's not a duplicated content, but a different version of the same content." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:293 -msgid "Language Detection" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:295 -msgid "When a visitor lands for the first time on your website (e.g. yourwebsite.com/shop), they may automatically be redirected to a translated version according to their browser language preference (e.g. yourwebsite.com/fr\\_FR/shop)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:300 -msgid "Next time, it keeps a cookie of the current language to avoid any redirection." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:303 -msgid "To force a visitor to stick to the default language, you can use the code of the default language in your link, example: yourwebsite.com/en\\_US/shop. This will always land visitors to the English version of the page, without using the browser language preferences." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:310 -msgid "Page Speed" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:313 -msgid "Introduction" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:315 -msgid "The time to load a page is an important criteria for search engines. A faster website not only improves your visitor's experience, but gives you a better page ranking. Some studies have shown that, if you divide the time to load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor abandonment rate is also divided by two. (25% to 12.5%). One extra second to load a page could `cost $1.6b to Amazon in sales <http://www.fastcompany.com/1825005/how-one-second-could-cost-amazon-16-billion-sales>`__." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:326 -msgid "Fortunately, Odoo does all the magic for you. Below, you will find the tricks Odoo uses to speed up your page loading time. You can compare how your website ranks using these two tools:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:330 -msgid "`Google Page Speed <https://developers.google.com/speed/pagespeed/insights/>`__" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:332 -msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:335 -msgid "Images" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:337 -msgid "When you upload new images, Odoo automatically compresses them to reduce their sizes (lossless compression for .PNG and .GIF and lossy compression for .JPG)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:341 -msgid "From the upload button, you have the option to keep the original image unmodified if you prefer to optimize the quality of the image rather than performance." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:349 -msgid "Odoo compresses images when they are uploaded to your website, not when requested by the visitor. Thus, it's possible that, if you use a third-party theme, it will provide images that are not compressed efficiently. But all images used in Odoo official themes have been compressed by default." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:355 -msgid "When you click on an image, Odoo shows you the Alt and title attributes of the ``<img>`` tag. You can click on it to set your own title and Alt attributes for the image." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:362 -msgid "When you click on this link, the following window will appear:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:367 -msgid "Odoo's pictograms are implemented using a font (`Font Awesome <https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes). Thus, you can use as many pictograms as you want in your page, they will not result in extra requests to load the page." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:376 -msgid "Static Resources: CSS" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:378 -msgid "All CSS files are pre-processed, concatenated, minified, compressed and cached (server-side and browser-side). The result:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:381 -msgid "only one CSS file request is needed to load a page" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:383 -msgid "this CSS file is shared and cached amongst pages, so that when the visitor clicks on another page, the browser doesn't have to even load a single CSS resource." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:387 -msgid "this CSS file is optimized to be small" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:389 -msgid "**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a theme might use another framework, most of `Odoo themes <https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap directly. Since Odoo supports Less and Sass, you can modify CSS rules instead of overwriting them through extra CSS lines, resulting in a smaller file." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:396 -msgid "**Concatenated:** every module or library you might use in Odoo has its own set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having several CSS files is great for the modularity, but not good for the performance because most browsers can only perform 6 requests in parallel resulting in lots of files loaded in series. The latency time to transfer a file is usually much longer than the actual data transfer time, for small files like .JS and .CSS. Thus, the time to load CSS resources depends more on the number of requests to be done than the actual file size." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:406 -msgid "To address this issue, all CSS / Less / Sass files are concatenated into a single .CSS file to send to the browser. So a visitor has **only one .CSS file to load** per page, which is particularly efficient. As the CSS is shared amongst all pages, when the visitor clicks on another page, the browser does not even have to load a new CSS file!" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:413 -msgid "**Both files in the <head>**" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:413 -msgid "**What the visitor gets (only one file)**" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:415 -msgid "/\\* From bootstrap.css \\*/" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:415 -#: ../../content/applications/websites/website/optimize/seo.rst:416 -#: ../../content/applications/websites/website/optimize/seo.rst:422 -#: ../../content/applications/websites/website/optimize/seo.rst:448 -msgid ".text-muted {" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:416 -#: ../../content/applications/websites/website/optimize/seo.rst:423 -#: ../../content/applications/websites/website/optimize/seo.rst:449 -msgid "color: #666;" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:417 -msgid "color: #777;" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:417 -msgid "background: yellow" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:418 -msgid "background: yellow;" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:418 -#: ../../content/applications/websites/website/optimize/seo.rst:419 -#: ../../content/applications/websites/website/optimize/seo.rst:424 -#: ../../content/applications/websites/website/optimize/seo.rst:450 -msgid "}" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:421 -msgid "/\\* From my-theme.css \\*/" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:427 -msgid "The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. By doing this, additional page views from the same visitor will not have to load CSS files at all. But some modules might include huge CSS/Javascript resources that you do not want to prefetch at the first page because they are too big. In this case, Odoo splits this resource into a second bundle that is loaded only when the page using it is requested. An example of this is the backend that is only loaded when the visitor logs in and accesses the backend (/web)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:437 -msgid "If the CSS file is very big, Odoo will split it into two smaller files to avoid the 4095 selectors limit per sheet of Internet Explorer. But most themes fit below this limit." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:441 -msgid "**Minified:** After being pre-processed and concatenated, the resulting CSS is minified to reduce its size." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:445 -msgid "**Before minification**" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:445 -msgid "**After minification**" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:447 -msgid "/\\* some comments \\*/" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:447 -msgid ".text-muted {color: #666}" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:453 -msgid "The final result is then compressed, before being delivered to the browser." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:456 -msgid "Then, a cached version is stored server-side (so we do not have to pre-process, concatenate, minify at every request) and browser-side (so the same visitor will load the CSS only once for all pages they visit)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:462 -msgid "Static Resources: Javascript" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:464 -msgid "As with CSS resources, Javascript resources are also concatenated, minified, compressed and cached (server-side and browser-side)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:467 -msgid "Odoo creates three Javascript bundles:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:469 -msgid "One for all pages of the website (including code for parallax effects, form validation, etc.)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:472 -msgid "One for common Javascript code shared among frontend and backend (Bootstrap)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:475 -msgid "One for backend specific Javascript code (Odoo Web Client interface for your employees using Odoo)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:478 -msgid "Most visitors of your website will only need the first two bundles, resulting in a maximum of two Javascript files to load to render one page. As these files are shared across all pages, further clicks by the same visitor will not load any other Javascript resource." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:484 -msgid "If you work on :ref:`developer mode <developer-mode>`, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:489 -msgid "CDN" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:491 -msgid "If you activate the CDN feature in Odoo, static resources (Javascript, CSS, images) are loaded from a Content Delivery Network. Using a Content Delivery Network has three advantages:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:495 -msgid "Load resources from a nearby server (most CDN have servers in main countries around the globe)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:498 -msgid "Cache resources efficiently (no computation resources usage on your own server)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:501 -msgid "Split the resource loading on different services allowing to load more resources in parallel (since the Chrome limit of 6 parallel requests is by domain)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:505 -msgid "You can configure your CDN options from the **Website Admin** app, using the Configuration menu. Here is an example of configuration you can use:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:512 -msgid "HTML Pages" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:514 -msgid "The HTML pages can be compressed, but this is usually handled by your web server (NGINX or Apache)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:517 -msgid "The Odoo Website builder has been optimized to guarantee clean and short HTML code. Building blocks have been developed to produce clean HTML code, usually using Bootstrap and the HTML editor." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:521 -msgid "As an example, if you use the color picker to change the color of a paragraph to the primary color of your website, Odoo will produce the following code:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:525 -msgid "``<p class=\"text-primary\">My Text</p>``" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:527 -msgid "Whereas most HTML editors (such as CKEditor) will produce the following code:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:530 -msgid "``<p style=\"color: #AB0201\">My Text</p>``" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:533 -msgid "Responsive Design" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:535 -msgid "Websites that are not mobile-friendly are negatively impacted in search engine rankings. All Odoo themes rely on Bootstrap to render efficiently according to the device: desktop, tablet or mobile." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:542 -msgid "As all Odoo modules share the same technology, absolutely all pages in your website are mobile friendly." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:546 -msgid "Browser Caching" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:548 -msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:555 -msgid "This allows Odoo to set a very long cache delay (XXX) on these resources: XXX secs, while being updated instantly if you update the resource." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:560 -msgid "Scalability" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:562 -msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:565 -msgid "Here is the slide that summarizes the scalability of Odoo Website & eCommerce." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:571 -msgid "Search Engines Files" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:574 -msgid "Sitemap" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:576 -msgid "The sitemap points out pages to index to search engine robots. Odoo generates a ``/sitemap.xml`` file automatically for you. For performance reasons, this file is cached and updated every 12 hours." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:580 -msgid "By default, all URLs will be in a single ``/sitemap.xml`` file, but if you have a lot of pages, Odoo will automatically create a Sitemap Index file, respecting the `sitemaps.org protocol <http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 chunks per file." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:586 -msgid "Every sitemap entry has 4 attributes that are computed automatically:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:588 -msgid "``<loc>`` : the URL of a page" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:590 -msgid "``<lastmod>`` : last modification date of the resource, computed automatically based on related object. For a page related to a product, this could be the last modification date of the product or the page." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:595 -msgid "``<priority>`` : modules may implement their own priority algorithm based on their content (example: a forum might assign a priority based on the number of votes on a specific post). The priority of a static page is defined by it's priority field, which is normalized (16 is the default)." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:602 -msgid "Structured Data Markup" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:604 -msgid "Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them understand your content and create well-presented search results." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:609 -msgid "Google supports a number of rich snippets for content types, including: Reviews, People, Products, Businesses, Events and Organizations." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:612 -msgid "Odoo implements micro data as defined in the `schema.org <http://schema.org>`__ specification for events, eCommerce products, forum posts and contact addresses. This allows your product pages to be displayed in Google using extra information like the price and rating of a product:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:622 -msgid "robots.txt" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:624 -msgid "When indexing your website, search engines take a first look at the general indexing rules of the ``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:628 -msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml" -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:631 -msgid "It means that all robots are allowed to index your website and there is no other indexing rule than specified in the sitemap to be found at following address." -msgstr "" - -#: ../../content/applications/websites/website/optimize/seo.rst:635 -msgid "You can customize the file *robots* in :ref:`developer mode <developer-mode>` from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:3 -msgid "Unsplash (free images)" -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:6 -msgid "Generate an Unsplash access key" -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:9 -msgid "**As an Odoo Online user**, you are ready to use Unsplash. You won't need to follow this guide to set up Unsplash information since you will use our own Odoo Unsplash key in a transparent way." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:13 -msgid "Generate an Unsplash access key for non-Odoo Online users" -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:15 -msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:17 -msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on **New Application**." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:23 -msgid "Accept the conditions and click on **Accept terms**." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:28 -msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so that Unsplash can recognize it as an Odoo instance. Once done, click on **Create application**." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:35 -msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:42 -msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:46 -msgid "Generate an Unsplash application ID" -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:49 -msgid "You should first create and set up your Unsplash application." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:51 -msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on your newly created Unsplash application under **Your applications**." -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:57 -msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/<application_id>``" -msgstr "" - -#: ../../content/applications/websites/website/optimize/unsplash.rst:65 -msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction." -msgstr "" - -#: ../../content/applications/websites/website/publish.rst:5 -msgid "Publish" -msgstr "" - -#: ../../content/applications/websites/website/publish/multi_website.rst:3 -msgid "Manage Multi Websites" -msgstr "" - -#: ../../content/applications/websites/website/publish/multi_website.rst:8 +#: ../../content/applications/websites/website/configuration/multi_website.rst:8 msgid "Odoo’s Multi-Websites opens up broad possibilities of diversification and customer segmentation for your business. A multiplied audience and boosted revenue are now just a few clicks away!" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:12 +#: ../../content/applications/websites/website/configuration/multi_website.rst:12 msgid "Each website can work in a fully independent way, with its theme, branding, domain name, header & footer, pages, languages, products, blog posts, forum, slides, events, live chat channels, etc. Let’s go for a tour!" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:20 +#: ../../content/applications/websites/website/configuration/multi_website.rst:20 msgid "To create a new website, go to :menuselection:`Website --> Configuration --> Settings`. The button, *Create a new website*, lays in the first section." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:28 +#: ../../content/applications/websites/website/configuration/multi_website.rst:28 msgid "In the upcoming prompt, set a name for your new website and a specific domain name. Leave empty to publish the new website under the default domain of your Odoo database. You can later set some country groups to redirect visitors to it using Geo IP." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:36 +#: ../../content/applications/websites/website/configuration/multi_website.rst:36 msgid "Then, select a theme. This new website might have an entirely different purpose or audience than the first one. So feel free to go for a different theme!" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:40 +#: ../../content/applications/websites/website/configuration/multi_website.rst:40 msgid "Once the theme is selected, you can start to build the homepage of your website. Follow the purple drops; they will help you in the first steps." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:48 +#: ../../content/applications/websites/website/configuration/multi_website.rst:48 msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (``CNAME``) and to authorize it Odoo-side. See :ref:`domain-name/existing`." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:52 +#: ../../content/applications/websites/website/configuration/multi_website.rst:52 msgid "Create the menu" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:54 +#: ../../content/applications/websites/website/configuration/multi_website.rst:54 msgid "The new website has a default menu with all the installed applications. To edit it, click :menuselection:`Pages --> Edit Menu`. Moving forward you only edit the menu of the current website." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:59 +#: ../../content/applications/websites/website/configuration/multi_website.rst:59 msgid "Switch from one website to another" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:62 +#: ../../content/applications/websites/website/configuration/multi_website.rst:62 msgid "As easy as ABC! There is a website switcher in the right corner of the edit bar. Switching to another website will connect to the domain of this website. If you use another domain for the website, the user is requested to sign in." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:71 +#: ../../content/applications/websites/website/configuration/multi_website.rst:71 msgid "When switching, you are redirected to the same domain path on the other website (e.g., ``/shop/myproduct``). If this URL is not used, you will be redirected to a 404 page but prompted to create a new page from there." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:76 +#: ../../content/applications/websites/website/configuration/multi_website.rst:76 msgid "Add features" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:78 +#: ../../content/applications/websites/website/configuration/multi_website.rst:78 msgid "The website apps you install (e.g., Slides, Blogs) are made available on all your websites. You can, of course, keep them hidden in one website by removing the menu item." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:82 +#: ../../content/applications/websites/website/configuration/multi_website.rst:82 msgid "Each website comes with a high range of specific options in the settings. First, select the website to configure." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:88 +#: ../../content/applications/websites/website/configuration/multi_website.rst:88 msgid "Then, take a look at the options flagged with the earth icon. It means they only impact the very website you are working on." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:94 +#: ../../content/applications/websites/website/configuration/multi_website.rst:94 msgid "You can, for instance, set specific :" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:96 +#: ../../content/applications/websites/website/configuration/multi_website.rst:96 msgid "languages," msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:98 +#: ../../content/applications/websites/website/configuration/multi_website.rst:98 msgid "domain names," msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:100 +#: ../../content/applications/websites/website/configuration/multi_website.rst:100 msgid "social media links," msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:102 +#: ../../content/applications/websites/website/configuration/multi_website.rst:102 msgid "customer portal mode (B2C vs. B2B)," msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:104 +#: ../../content/applications/websites/website/configuration/multi_website.rst:104 msgid "dedicated live chat channels," msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:106 +#: ../../content/applications/websites/website/configuration/multi_website.rst:106 msgid "etc." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:108 +#: ../../content/applications/websites/website/configuration/multi_website.rst:108 msgid "The other options are global and apply to all your websites." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:111 +#: ../../content/applications/websites/website/configuration/multi_website.rst:111 msgid "Manage domain names" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:113 +#: ../../content/applications/websites/website/configuration/multi_website.rst:113 msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using GeoIP." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:122 +#: ../../content/applications/websites/website/configuration/multi_website.rst:122 msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *GeoIP* library. See :doc:`on-premise_geo-ip-installation`" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:127 +#: ../../content/applications/websites/website/configuration/multi_website.rst:127 msgid ":doc:`/administration/maintain/domain_names`" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:129 +#: ../../content/applications/websites/website/configuration/multi_website.rst:129 msgid "If you setup an extra website and specify the domain name you will have to do three things to get this feature to work:" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:132 +#: ../../content/applications/websites/website/configuration/multi_website.rst:132 msgid "Setup an A-record in the DNS configuration of your hosting provider so that \"www.mywebsite2.ext\" is redirected to the IP of your Odoo instance." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:134 +#: ../../content/applications/websites/website/configuration/multi_website.rst:134 msgid "Create an extra Nginx ``server`` block in which you set the ``server_name`` that you've set in the :guilabel:`Website domain` field." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:136 +#: ../../content/applications/websites/website/configuration/multi_website.rst:136 msgid "Reload and restart your Nginx instance to use the new ``server`` block." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:139 +#: ../../content/applications/websites/website/configuration/multi_website.rst:139 msgid "Customize the visitor experience" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:142 +#: ../../content/applications/websites/website/configuration/multi_website.rst:142 msgid "The customer experience can be customized very profoundly thanks to the menu \\*Customize\\*. All the visual options available there are specific to each website. Go through the different pages to adapt them to this new audience. Focus on workflows, and automatic pages (eCommerce checkout, blogs, events, etc.) as the number of available options is higher there." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:152 +#: ../../content/applications/websites/website/configuration/multi_website.rst:152 msgid "Publish specific content per website" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:155 +#: ../../content/applications/websites/website/configuration/multi_website.rst:155 msgid "Like static pages, any content created from the front-end (product, blog post, etc.) is always only published in the current website. You can change that from the edit form view in the backend and leave the *Website* field blank. This will publish it in all the websites." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:163 +#: ../../content/applications/websites/website/configuration/multi_website.rst:163 msgid "Here are all the objects that you can link to *either one or all the websites*:" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:166 +#: ../../content/applications/websites/website/configuration/multi_website.rst:166 msgid "Products" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:168 +#: ../../content/applications/websites/website/configuration/multi_website.rst:168 msgid "Product Categories for eCommerce" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:170 +#: ../../content/applications/websites/website/configuration/multi_website.rst:170 msgid "Blogs" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:172 +#: ../../content/applications/websites/website/configuration/multi_website.rst:172 msgid "Slide Channels" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:174 +#: ../../content/applications/websites/website/configuration/multi_website.rst:174 msgid "Forums" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:176 +#: ../../content/applications/websites/website/configuration/multi_website.rst:176 msgid "Events" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:178 +#: ../../content/applications/websites/website/configuration/multi_website.rst:178 msgid "Job Positions" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:181 +#: ../../content/applications/websites/website/configuration/multi_website.rst:181 msgid "When you create the record from the backend and publish it, typically a product or an event, it is made available in all websites." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:185 +#: ../../content/applications/websites/website/configuration/multi_website.rst:185 msgid "Publish a page in all websites" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:187 +#: ../../content/applications/websites/website/configuration/multi_website.rst:187 msgid "A new static page is created and only made available in the current website. You can duplicate it to other websites from :menuselection:`Website --> Configuration --> Pages`. To do so, leave the *Website* field empty." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:191 +#: ../../content/applications/websites/website/configuration/multi_website.rst:191 msgid "If you want to duplicate it in just one other website, duplicate the page and set the new website." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:197 +#: ../../content/applications/websites/website/configuration/multi_website.rst:197 msgid "When you edit the page again, the change only affects the current website. A new page is duplicated and tied up to the website. The original page still being linked to all websites." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:202 +#: ../../content/applications/websites/website/configuration/multi_website.rst:202 msgid "By grouping pages by URL in the page manager, you quickly find the original page behind each edited page." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:209 +#: ../../content/applications/websites/website/configuration/multi_website.rst:209 msgid "Multi-companies" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:211 +#: ../../content/applications/websites/website/configuration/multi_website.rst:211 msgid "Each website can be linked to a specific company of your system, in a multi-companies environment." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:217 +#: ../../content/applications/websites/website/configuration/multi_website.rst:217 msgid "With such a configuration, only company-related data appear on the website (products, jobs, events, etc.)." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:220 +#: ../../content/applications/websites/website/configuration/multi_website.rst:220 msgid "Website editors can only view and edit the pages of the records they have access to, typically the ones belonging to their current company (and to their subsidiaries, or child companies in Odoo language). And so is it for visitors." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:226 +#: ../../content/applications/websites/website/configuration/multi_website.rst:226 msgid "If websites are multi-companies, you don’t change company when switching websites. To change the company and see the related content, use the company selector in the menu." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:232 +#: ../../content/applications/websites/website/configuration/multi_website.rst:232 msgid "Configure your eCommerce website" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:234 +#: ../../content/applications/websites/website/configuration/multi_website.rst:234 msgid "eCommerce is a crucial feature in the multi-websites environment. We made it so that the entire flow can be customized to fit the very audience of each website." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:239 +#: ../../content/applications/websites/website/configuration/multi_website.rst:239 msgid "Products only available on one website" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:241 +#: ../../content/applications/websites/website/configuration/multi_website.rst:241 msgid "We already saw earlier how to publish a specific record in only one website. You will find the \\*Website\\* field in the eCommerce tab of the product edit form. Empty means available in all websites." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:249 +#: ../../content/applications/websites/website/configuration/multi_website.rst:249 msgid "Products available on *some* websites" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:251 +#: ../../content/applications/websites/website/configuration/multi_website.rst:251 msgid "To make a product available on some websites, but not all of them, you should duplicate the product for each website." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:254 +#: ../../content/applications/websites/website/configuration/multi_website.rst:254 msgid "If you need a unique reference to manage in your inventory, you should install *Manufacturing\\ and create *Kits* BoMs (bills of materials). Each kit will link each published “virtual” product to the main reference managed in your inventory. That way, any item sold from your website will be converted into the storable item in the delivery order." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:261 +#: ../../content/applications/websites/website/configuration/multi_website.rst:261 msgid "Pricelists" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:263 +#: ../../content/applications/websites/website/configuration/multi_website.rst:263 msgid "To manage specific prices by websites, you can activate *Multiple Sales Prices per Product* in Website settings." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:266 +#: ../../content/applications/websites/website/configuration/multi_website.rst:266 msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. You can also choose to have a pricelist available *only* on a specific website." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:270 +#: ../../content/applications/websites/website/configuration/multi_website.rst:270 msgid ":doc:`../../ecommerce/maximizing_revenue/pricing`." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:275 +#: ../../content/applications/websites/website/configuration/multi_website.rst:275 msgid "Leaving the field empty means that you make it work in all websites if *Selectable* is selected. Otherwise, it makes it only available for backend operations of Sales and Point of Sale applications." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:280 +#: ../../content/applications/websites/website/configuration/multi_website.rst:280 msgid "Payment Acquirers and Delivery Methods" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:282 +#: ../../content/applications/websites/website/configuration/multi_website.rst:282 msgid "By default, published payment acquirers and delivery methods are deployed in all websites. You could already use specific payment acquirers per country using Geo IP by defining countries in their configuration. Now you can also do it per website by filling in the *Website* field." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:288 +#: ../../content/applications/websites/website/configuration/multi_website.rst:288 msgid "Customer accounts" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:290 +#: ../../content/applications/websites/website/configuration/multi_website.rst:290 msgid "There is a setting to choose how to manage customer accounts in Website settings. You can either allow customers to use one account through all the websites or compel them to create one account for each website. This last option is convenient if your websites shouldn’t be related to each other in the visitor mind." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:300 +#: ../../content/applications/websites/website/configuration/multi_website.rst:300 msgid "Technical hints for customization" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:302 +#: ../../content/applications/websites/website/configuration/multi_website.rst:302 msgid "If you want to publish custom objects on the website, here are a few tips to make it work with multi websites:" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:306 +#: ../../content/applications/websites/website/configuration/multi_website.rst:306 msgid "Sitemap: don’t forget the domain in the route to only publish" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:306 +#: ../../content/applications/websites/website/configuration/multi_website.rst:306 msgid "available records in each website’s sitemap." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:310 +#: ../../content/applications/websites/website/configuration/multi_website.rst:310 msgid "Access: you should call the method" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:309 +#: ../../content/applications/websites/website/configuration/multi_website.rst:309 msgid "*can_access_from_current_website* in the controller to make sure the visitor can see a record in the current website." msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:314 +#: ../../content/applications/websites/website/configuration/multi_website.rst:314 msgid "Search: when a list of records is displayed, don’t forget to specify" msgstr "" -#: ../../content/applications/websites/website/publish/multi_website.rst:313 +#: ../../content/applications/websites/website/configuration/multi_website.rst:313 msgid "the domain to only display records available for the current website." msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:3 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:3 msgid "Geo IP Installation (On-Premises Database)" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:6 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:6 msgid "Installation" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:9 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:9 msgid "Please note that the installation depends on your computer's operating system and distribution. We will assume that a Linux operating system is being used." msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:15 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:15 msgid "Install `geoip2 <https://pypi.org/project/geoip2/>`__ Python library" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:17 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:17 msgid "Download the `GeoLite2 City database <https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You should end up with a file called ``GeoLite2-City.mmdb``" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:22 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:22 msgid "Move the file to the folder ``/usr/share/GeoIP/``" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:24 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:24 msgid "Restart the server" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:27 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:27 msgid "If you can't/don't want to locate the geoip database in ``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo command line interface. This option takes the absolute path to the GeoIP database file and uses it as the GeoIP database. For example:" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:36 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:36 msgid ":doc:`CLI documentation </developer/reference/cli>`." msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:39 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:39 msgid "``GeoIP`` Python library can also be used. However this version is discontinued since January 1. See `GeoLite Legacy databases are now discontinued <https://support.maxmind.com/geolite-legacy-discontinuation-notice/>`_" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:44 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:44 msgid "How To Test GeoIP Geolocation In Your Odoo Website" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:46 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:46 msgid "Go to your website. Open the web page that you want to test ``GeoIP``." msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:47 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:47 msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:48 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:48 msgid "Add the following piece of XML in the page :" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:54 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:54 msgid "You should end up with a dictionary indicating the location of the IP address." msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:60 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:60 msgid "If the curly braces are empty ``{}``, it can be for any of the following reasons :" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:62 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:62 msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:64 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:64 msgid "If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode <odoo-bin --proxy-mode>`" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:66 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:66 msgid "``geoip2`` is not installed or the GeoIP database file wasn't found" msgstr "" -#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:67 +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:67 msgid "The GeoIP database was unable to resolve the given IP address" msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:3 -msgid "How to translate my website" +#: ../../content/applications/websites/website/configuration/translate.rst:3 +msgid "Translations" msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:8 +#: ../../content/applications/websites/website/configuration/translate.rst:5 msgid "In addition to creating great modern websites, Odoo gives you the possibility to translate it in different languages." msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:12 +#: ../../content/applications/websites/website/configuration/translate.rst:9 msgid "Process" msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:14 +#: ../../content/applications/websites/website/configuration/translate.rst:11 msgid "Once your website is created, you have the opportunity to translate it in as many different languages as you want." msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:17 +#: ../../content/applications/websites/website/configuration/translate.rst:14 msgid "You can only translate your website manually, follow the next step." msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:19 +#: ../../content/applications/websites/website/configuration/translate.rst:16 msgid "Now go to your website. On the bottom right corner of the page, click on **Add a language**." msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:25 +#: ../../content/applications/websites/website/configuration/translate.rst:22 msgid "Choose the language in which you want to translate your website and then click on **Load.**" msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:31 +#: ../../content/applications/websites/website/configuration/translate.rst:28 msgid "You will see that Now, next to English there is also French, which means that the page for the translation has been created. You can also see that some of the text has been translated automatically." msgstr "" -#: ../../content/applications/websites/website/publish/translate.rst:38 +#: ../../content/applications/websites/website/configuration/translate.rst:35 msgid "To translate the content of the website, click on **Translate** (here **Traduire** since we want to translate the website in French)." msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:3 +msgid "Unsplash (free images)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:6 +msgid "Generate an Unsplash access key" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:9 +msgid "**As an Odoo Online user**, you are ready to use Unsplash. You won't need to follow this guide to set up Unsplash information since you will use our own Odoo Unsplash key in a transparent way." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:13 +msgid "Generate an Unsplash access key for non-Odoo Online users" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:15 +msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:17 +msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on **New Application**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:23 +msgid "Accept the conditions and click on **Accept terms**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:28 +msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so that Unsplash can recognize it as an Odoo instance. Once done, click on **Create application**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:35 +msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:42 +msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:46 +msgid "Generate an Unsplash application ID" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:49 +msgid "You should first create and set up your Unsplash application." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:51 +msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on your newly created Unsplash application under **Your applications**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:57 +msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/<application_id>``" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:65 +msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:5 +msgid "Pages" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:3 +msgid "Search Engine Optimisation (SEO)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:5 +msgid "Search Engine Optimization (SEO) is a set of good practices to optimize your website so that you get a better ranking in search engines like Google. In short, a good SEO allows you to get more visitors." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:9 +msgid "Some examples of SEO rules: your web pages should load fast, your page should have one and only one title ``<h1>``, meta tags (alt-tag, title-tag) should be consistent with the content, your website should have a ``/sitemap.xml`` file, etc." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:15 +msgid "To guarantee Odoo Website and Odoo eCommerce users have a great SEO, Odoo abstracts all the technical complexities of SEO and handles everything for you, in the best possible way. This will be explained here below." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:20 +msgid "But first, let see how you can easily boost your ranking by finetuning the content and the meta tags of your website." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:24 +msgid "Meta Tags" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:27 +msgid "Title, Description" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:29 +msgid "Every web page should define the ``<title>`` and ``<description>`` meta data. These information elements are used by search engines to promote your website. They are automatically generated based on page title & content, but you can finetune them. Make sure they fit the content of the page, otherwise you will be downgraded by search engines." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:39 +msgid "Keywords" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:41 +msgid "In order to write quality content and boost your traffic, Odoo provides a ``<keyword>`` finder. Those keywords are the searches you want to head towards your website. For each keyword, you see how it is used in the content (H1, H2, page title, page description, page content) and what are the related searches in Google. The more keywords are used the better." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:51 +msgid "If your website is in multiple languages, you can use the Promote tool for every language of a single page and set specific title, description and search tags." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:56 +msgid "Content is King" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:58 +msgid "When it comes to SEO, content is usually king. Odoo provides several modules to help you build your website content:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:61 +msgid "**Odoo Blogs**: write great contents." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:63 +msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:67 +msgid "**Odoo Forum**: let your community create contents for you. Example: `odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com landing pages)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:71 +msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:77 +msgid "The 404 page is a regular page, that you can edit like any other page in Odoo. That way, you can build a great 404 page to redirect to the top content of your website when visitors get lost in invalid URLs." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:82 +msgid "Use Social Networks" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:84 +msgid "Social media is built for mass sharing. If lots of people share your content on social media, then it's likely more people will link to it, and links are a huge factor for SEO ranking." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:88 +msgid "Odoo embeds several tools to share content through social media:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:91 +msgid "Social Network" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:93 +msgid "Odoo allows to link all your social network accounts in your website footer. All you have to do is to refer all your accounts in your company settings." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:100 +msgid "Social Share" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:102 +msgid "Drop the building block *Share* on any page you want your visitors to share. By clicking the icon, they are prompted to share the page in their social media wall." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:109 +msgid "Most social media use a picture of the picture to decorate the share post. Odoo uses the website logo by default but you can choose any other image of your page in the Promote tool." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:117 +msgid "Facebook Page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:119 +msgid "Drop the building block *Facebook Page* to display a widget of your Facebook business page and encourage visitors to follow it. You can display the timeline, the next events and the messages." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:124 +msgid "Twitter Scroller" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:126 +msgid "Display the Twitter feeds with customer satifaction on your website. This will increase the number of tweets and shares." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:130 +msgid "Test Your Website" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:132 +msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `woorank.com <https://www.woorank.com>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:137 +msgid "URLs Handling" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:139 +msgid "This section sheds some light on how Odoo makes URLs SEO-friendly." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:142 +msgid "URLs Structure" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:144 +msgid "A typical Odoo URL will look like this:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:146 +msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:148 +msgid "With the following components:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:150 +msgid "**https://** = Protocol" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:152 +msgid "**www.mysite.com** = your domain name" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:154 +msgid "**/fr\\_FR** = page language. This part of the URL is removed if the visitor browses the main language of the website Thus, the main version of this page is: https://www.mysite.com/shop/product/my-great-product-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:159 +msgid "**/shop/product** = every module defines its own namespace (/shop is for the catalog of the eCommerce module, /shop/product is for a product page)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:163 +msgid "**my-great-product** = by default, this is the slugified title of the product this page refers to. But you can customize it for SEO purposes. A product named \"Pain carré\" will be slugified to \"pain-carre\". Depending on the namespace, this could be different objects (blog post, page title, forum post, forum comment, product category, etc.)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:170 +msgid "**-31** = the unique ID of the product" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:172 +msgid "Note that any dynamic component of an URL can be reduced to its ID. As an example, the following URLs all do a 301 redirect to the above URL:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:175 +msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:177 +msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:179 +msgid "http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product name)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:182 +msgid "Some URLs have several dynamic parts, like this one (a blog category and a post):" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:185 +msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:187 +msgid "In the above example:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:189 +msgid "*Company News* is the title of the blog" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:191 +msgid "*The Odoo Story* is the title of a specific blog post" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:193 +msgid "When an Odoo page has a pager, the page number is set directly in the URL (does not have a GET argument). This allows every page to be indexed by search engines. Example:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:197 +msgid "https://www.odoo.com/blog/page/3" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:200 +msgid "Changes in URLs & Titles" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:202 +msgid "When the URL of a page changes (e.g. a more SEO friendly version of your product name), you don't have to worry about updating all links:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:205 +msgid "Odoo will automatically update all its links to the new URL." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:207 +msgid "If external websites still points to the old URL, a 301 redirect will be done to route visitors to the new address of the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:210 +msgid "As an example, this URL:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:212 +msgid "http://mysite.com/shop/product/old-product-name-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:214 +msgid "Will automatically redirect to:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:216 +msgid "http://mysite.com/shop/product/new-and-better-product-name-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:218 +msgid "In short, just change the title of a blog post or the name of a product, and the changes will apply automatically everywhere in your website. The old link still functions when used by external websites, via a 301 redirect, maintaining the SEO link juice." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:224 +msgid "HTTPS" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:226 +msgid "Search engines boost ranking of secure HTTPS/SSL websites. So, by default all Odoo Online instances are fully based on HTTPS. If the visitor accesses your website through a non HTTPS url, it gets a 301 redirect to its HTTPS equivalent." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:232 +msgid "Links: Nofollow Strategy" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:234 +msgid "The more a page is linked from external and quality websites, the better it is for your SEO." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:237 +msgid "Here are Odoo strategies to manage links:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:239 +msgid "Every link you add to your website is \"dofollow\", which means that this link will contribute to the SEO Juice for the linked page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:243 +msgid "Every link posted by a contributor (forum post, blog comment, etc.) that links to your own website is \"dofollow\" too." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:246 +msgid "But every link posted by a contributor that links to an external website is \"nofollow\". In that way, you do not run the risk of people posting links on your website to third-party websites which have a bad reputation." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:251 +msgid "Note that, when using the forum, contributors having a lot of Karma can be trusted. In such case, their links will not have any ``rel=\"nofollow\"`` attribute." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:256 +msgid "Multi-Language Support" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:259 +msgid "Multi-Language URLs" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:261 +msgid "If you run a website in multiple languages, the same content will be available in different URLs, depending on the language used:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:264 +msgid "https://www.mywebsite.com/shop/product/my-product-1 (main language, English here)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:266 +msgid "https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:268 +msgid "In this example, fr\\_FR is the language of the page. You can even have several variations of the same language: pt\\_BR (Portuguese from Brazil) , pt\\_PT (Portuguese from Portugal)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:273 +msgid "Language Annotation" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:275 +msgid "To let search engines know that the second URL is the French translation of the first URL, Odoo will add an HTML link element in the header. In the HTML <head> section of the main version, Odoo automatically adds a link element pointing to the translated versions of that webpage;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:280 +msgid "<link rel=\"alternate\" hreflang=\"fr\" href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:283 +msgid "With this approach:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:285 +msgid "Search engines will redirect to the right language according to the visitor language." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:288 +msgid "You do not get penalized by search engines if your page is not translated yet. Indeed, it's not a duplicated content, but a different version of the same content." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:293 +msgid "Language Detection" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:295 +msgid "When a visitor lands for the first time on your website (e.g. yourwebsite.com/shop), they may automatically be redirected to a translated version according to their browser language preference (e.g. yourwebsite.com/fr\\_FR/shop)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:300 +msgid "Next time, it keeps a cookie of the current language to avoid any redirection." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:303 +msgid "To force a visitor to stick to the default language, you can use the code of the default language in your link, example: yourwebsite.com/en\\_US/shop. This will always land visitors to the English version of the page, without using the browser language preferences." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:310 +msgid "Page Speed" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:313 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:315 +msgid "The time to load a page is an important criteria for search engines. A faster website not only improves your visitor's experience, but gives you a better page ranking. Some studies have shown that, if you divide the time to load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor abandonment rate is also divided by two. (25% to 12.5%). One extra second to load a page could `cost $1.6b to Amazon in sales <http://www.fastcompany.com/1825005/how-one-second-could-cost-amazon-16-billion-sales>`__." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:326 +msgid "Fortunately, Odoo does all the magic for you. Below, you will find the tricks Odoo uses to speed up your page loading time. You can compare how your website ranks using these two tools:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:330 +msgid "`Google Page Speed <https://developers.google.com/speed/pagespeed/insights/>`__" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:332 +msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:335 +msgid "Images" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:337 +msgid "When you upload new images, Odoo automatically compresses them to reduce their sizes (lossless compression for .PNG and .GIF and lossy compression for .JPG)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:341 +msgid "From the upload button, you have the option to keep the original image unmodified if you prefer to optimize the quality of the image rather than performance." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:349 +msgid "Odoo compresses images when they are uploaded to your website, not when requested by the visitor. Thus, it's possible that, if you use a third-party theme, it will provide images that are not compressed efficiently. But all images used in Odoo official themes have been compressed by default." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:355 +msgid "When you click on an image, Odoo shows you the Alt and title attributes of the ``<img>`` tag. You can click on it to set your own title and Alt attributes for the image." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:362 +msgid "When you click on this link, the following window will appear:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:367 +msgid "Odoo's pictograms are implemented using a font (`Font Awesome <https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes). Thus, you can use as many pictograms as you want in your page, they will not result in extra requests to load the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:376 +msgid "Static Resources: CSS" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:378 +msgid "All CSS files are pre-processed, concatenated, minified, compressed and cached (server-side and browser-side). The result:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:381 +msgid "only one CSS file request is needed to load a page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:383 +msgid "this CSS file is shared and cached amongst pages, so that when the visitor clicks on another page, the browser doesn't have to even load a single CSS resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:387 +msgid "this CSS file is optimized to be small" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:389 +msgid "**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a theme might use another framework, most of `Odoo themes <https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap directly. Since Odoo supports Less and Sass, you can modify CSS rules instead of overwriting them through extra CSS lines, resulting in a smaller file." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:396 +msgid "**Concatenated:** every module or library you might use in Odoo has its own set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having several CSS files is great for the modularity, but not good for the performance because most browsers can only perform 6 requests in parallel resulting in lots of files loaded in series. The latency time to transfer a file is usually much longer than the actual data transfer time, for small files like .JS and .CSS. Thus, the time to load CSS resources depends more on the number of requests to be done than the actual file size." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:406 +msgid "To address this issue, all CSS / Less / Sass files are concatenated into a single .CSS file to send to the browser. So a visitor has **only one .CSS file to load** per page, which is particularly efficient. As the CSS is shared amongst all pages, when the visitor clicks on another page, the browser does not even have to load a new CSS file!" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:413 +msgid "**Both files in the <head>**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:413 +msgid "**What the visitor gets (only one file)**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:415 +msgid "/\\* From bootstrap.css \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:415 +#: ../../content/applications/websites/website/pages/seo.rst:416 +#: ../../content/applications/websites/website/pages/seo.rst:422 +#: ../../content/applications/websites/website/pages/seo.rst:448 +msgid ".text-muted {" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:416 +#: ../../content/applications/websites/website/pages/seo.rst:423 +#: ../../content/applications/websites/website/pages/seo.rst:449 +msgid "color: #666;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:417 +msgid "color: #777;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:417 +msgid "background: yellow" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:418 +msgid "background: yellow;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:418 +#: ../../content/applications/websites/website/pages/seo.rst:419 +#: ../../content/applications/websites/website/pages/seo.rst:424 +#: ../../content/applications/websites/website/pages/seo.rst:450 +msgid "}" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:421 +msgid "/\\* From my-theme.css \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:427 +msgid "The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. By doing this, additional page views from the same visitor will not have to load CSS files at all. But some modules might include huge CSS/Javascript resources that you do not want to prefetch at the first page because they are too big. In this case, Odoo splits this resource into a second bundle that is loaded only when the page using it is requested. An example of this is the backend that is only loaded when the visitor logs in and accesses the backend (/web)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:437 +msgid "If the CSS file is very big, Odoo will split it into two smaller files to avoid the 4095 selectors limit per sheet of Internet Explorer. But most themes fit below this limit." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:441 +msgid "**Minified:** After being pre-processed and concatenated, the resulting CSS is minified to reduce its size." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:445 +msgid "**Before minification**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:445 +msgid "**After minification**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:447 +msgid "/\\* some comments \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:447 +msgid ".text-muted {color: #666}" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:453 +msgid "The final result is then compressed, before being delivered to the browser." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:456 +msgid "Then, a cached version is stored server-side (so we do not have to pre-process, concatenate, minify at every request) and browser-side (so the same visitor will load the CSS only once for all pages they visit)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:462 +msgid "Static Resources: Javascript" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:464 +msgid "As with CSS resources, Javascript resources are also concatenated, minified, compressed and cached (server-side and browser-side)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:467 +msgid "Odoo creates three Javascript bundles:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:469 +msgid "One for all pages of the website (including code for parallax effects, form validation, etc.)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:472 +msgid "One for common Javascript code shared among frontend and backend (Bootstrap)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:475 +msgid "One for backend specific Javascript code (Odoo Web Client interface for your employees using Odoo)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:478 +msgid "Most visitors of your website will only need the first two bundles, resulting in a maximum of two Javascript files to load to render one page. As these files are shared across all pages, further clicks by the same visitor will not load any other Javascript resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:484 +msgid "If you work on :ref:`developer mode <developer-mode>`, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:489 +msgid "CDN" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:491 +msgid "If you activate the CDN feature in Odoo, static resources (Javascript, CSS, images) are loaded from a Content Delivery Network. Using a Content Delivery Network has three advantages:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:495 +msgid "Load resources from a nearby server (most CDN have servers in main countries around the globe)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:498 +msgid "Cache resources efficiently (no computation resources usage on your own server)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:501 +msgid "Split the resource loading on different services allowing to load more resources in parallel (since the Chrome limit of 6 parallel requests is by domain)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:505 +msgid "You can configure your CDN options from the **Website Admin** app, using the Configuration menu. Here is an example of configuration you can use:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:512 +msgid "HTML Pages" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:514 +msgid "The HTML pages can be compressed, but this is usually handled by your web server (NGINX or Apache)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:517 +msgid "The Odoo Website builder has been optimized to guarantee clean and short HTML code. Building blocks have been developed to produce clean HTML code, usually using Bootstrap and the HTML editor." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:521 +msgid "As an example, if you use the color picker to change the color of a paragraph to the primary color of your website, Odoo will produce the following code:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:525 +msgid "``<p class=\"text-primary\">My Text</p>``" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:527 +msgid "Whereas most HTML editors (such as CKEditor) will produce the following code:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:530 +msgid "``<p style=\"color: #AB0201\">My Text</p>``" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:533 +msgid "Responsive Design" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:535 +msgid "Websites that are not mobile-friendly are negatively impacted in search engine rankings. All Odoo themes rely on Bootstrap to render efficiently according to the device: desktop, tablet or mobile." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:542 +msgid "As all Odoo modules share the same technology, absolutely all pages in your website are mobile friendly." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:546 +msgid "Browser Caching" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:548 +msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:555 +msgid "This allows Odoo to set a very long cache delay (XXX) on these resources: XXX secs, while being updated instantly if you update the resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:560 +msgid "Scalability" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:562 +msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:565 +msgid "Here is the slide that summarizes the scalability of Odoo Website & eCommerce." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:571 +msgid "Search Engines Files" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:574 +msgid "Sitemap" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:576 +msgid "The sitemap points out pages to index to search engine robots. Odoo generates a ``/sitemap.xml`` file automatically for you. For performance reasons, this file is cached and updated every 12 hours." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:580 +msgid "By default, all URLs will be in a single ``/sitemap.xml`` file, but if you have a lot of pages, Odoo will automatically create a Sitemap Index file, respecting the `sitemaps.org protocol <http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 chunks per file." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:586 +msgid "Every sitemap entry has 4 attributes that are computed automatically:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:588 +msgid "``<loc>`` : the URL of a page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:590 +msgid "``<lastmod>`` : last modification date of the resource, computed automatically based on related object. For a page related to a product, this could be the last modification date of the product or the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:595 +msgid "``<priority>`` : modules may implement their own priority algorithm based on their content (example: a forum might assign a priority based on the number of votes on a specific post). The priority of a static page is defined by it's priority field, which is normalized (16 is the default)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:602 +msgid "Structured Data Markup" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:604 +msgid "Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them understand your content and create well-presented search results." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:609 +msgid "Google supports a number of rich snippets for content types, including: Reviews, People, Products, Businesses, Events and Organizations." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:612 +msgid "Odoo implements micro data as defined in the `schema.org <http://schema.org>`__ specification for events, eCommerce products, forum posts and contact addresses. This allows your product pages to be displayed in Google using extra information like the price and rating of a product:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:622 +msgid "robots.txt" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:624 +msgid "When indexing your website, search engines take a first look at the general indexing rules of the ``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:628 +msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:631 +msgid "It means that all robots are allowed to index your website and there is no other indexing rule than specified in the sitemap to be found at following address." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:635 +msgid "You can customize the file *robots* in :ref:`developer mode <developer-mode>` from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades." +msgstr "" + +#: ../../content/applications/websites/website/reporting.rst:5 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:3 +msgid "How to track your website's traffic in Google Analytics" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:6 +msgid "Google deprecated **Universal Analytics** which won't be supported anymore in `July 2023 <https://support.google.com/analytics/answer/11583528>`_. They are replacing it with **Analytics 4**." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:10 +msgid "New accounts are already using it, but accounts created before `October 2020 <https://support.google.com/analytics/answer/11583832>`_ are most likely still using **Universal Analytics**." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:14 +msgid "Odoo 15.0 is already adapted and ready for **Analytics 4**. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:19 +msgid "To follow your website's traffic with Google Analytics:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:21 +msgid "`Create a Google Analytics account <https://www.google.com/analytics/>`__ if you don't have any." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:24 +msgid "Go through the creation form and accept the conditions to get the tracking ID." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:29 +msgid "Copy the tracking ID to insert it in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:34 +msgid "Go to the *Configuration* menu of your Odoo's Website app. In the settings, turn on Google Analytics and paste the tracking ID. Then save the page." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:41 +msgid "To make your first steps in Google Analytics, refer to `Google Documentation <https://support.google.com/analytics/answer/1008015?hl=en/>`_." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:46 +msgid ":doc:`google_analytics_dashboard`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:3 +msgid "How to track your website traffic from your Odoo Dashboard" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:6 +msgid "It is not possible anymore for new Google Analytics accounts to integrate their **Google Analytics Dashboard** inside their **Odoo Dashboard**. Google deprecated **Universal Analytics** which won't be supported anymore in `July 2023 <https://support.google.com/analytics/answer/11583528>`_. They are replacing it with **Analytics 4**. New accounts are already using it." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:12 +msgid "**Analytics 4** `doesn't allow <https://issuetracker.google.com/issues/233738709?pli=1>`_ its dashboard to be integrated in external websites." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:15 +msgid "You now have to check your Analytics data directly in the Google Platform as it won't be possible in Odoo anymore." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:18 +msgid "Accounts created before `October 2020 <https://support.google.com/analytics/answer/11583832>`_ should still be using **Universal Analytics** and be able to integrate their dashboard on external website until the official end of support `around mid 2023 <https://developers.googleblog.com/2022/03/gis-jsweb-authz-migration.html>`_." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:23 +msgid "You can follow your traffic statistics straight from your Odoo Website Dashboard thanks to Google Analytics." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:26 +msgid "A preliminary step is creating a Google Analytics account and entering the tracking ID in your Website's settings (see :doc:`google_analytics`)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:29 +msgid "Go to `Google APIs platform <https://console.developers.google.com>`__ to generate Analytics API credentials. Log in with your Google account." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:32 +msgid "Select Analytics API." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:37 +msgid "Create a new project and give it a name (e.g. Odoo). This project is needed to store your API credentials." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:43 +msgid "Enable the API." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:48 +msgid "Create credentials to use in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:53 +msgid "Select *Web browser (Javascript)* as calling source and *User data* as kind of data." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:59 +msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:69 +msgid "Go through the Consent Screen step by entering a product name (e.g. Google Analytics in Odoo). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:74 +msgid "Finally you are provided with your Client ID. Copy and paste it in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:79 +msgid "Open your Website Dashboard in Odoo and link your Analytics account to past your Client ID." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:85 +msgid "As a last step, authorize Odoo to access Google API." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:3 +msgid "Link trackers" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:5 +msgid "Link Trackers allow you to track your marketing campaigns (emails, banner ads, blog posts, social media posts, affiliate links, etc.). This way, you are able to identify your best traffic sources and make informed decisions about the distribution of your marketing budget." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:12 +msgid "Go to :menuselection:`Website --> Configuration --> Settings` and activate *Link Trackers*." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 +msgid "View of Website settings page emphasizing the link trackers field in Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:19 +msgid "Set up traceable URLs" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:21 +msgid "Go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Here, you are able to get a specific tracked URL based on the campaign, medium, and source being used." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 +msgid "View of the link tracker fields for Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:28 +msgid "**URL**: url of the page you want to track (e.g. the home page or a product's page)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:29 +msgid "**Campaign**: context of your link (e.g. a special promotion)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:30 +msgid "**Medium**: channel used to share (deliver) your link (e.g. an email or a Facebook ad)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:31 +msgid "**Source**: platform where the traffic originates (e.g. Google or Twitter)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:33 +msgid "Now, click on *Get tracked link* to generate a URL that you can post or send by the source you have decided on." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:37 +msgid "Follow-up on tracked links" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:39 +msgid "To look at statistics of your links, go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Besides being able to see the *Most Clicked* and *Recently Used* links, you can also see complete statistics by clicking on *Stats*, including the number of clicks, and the country of origin for those clicks." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 +msgid "View of the tracked list emphasizing the statistics buttons in Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:50 +msgid "You can also access the link tracker on *odoo.com/r* via your browser." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:51 +msgid "Activate the developer mode (:menuselection:`Settings --> Activate the developer mode`) and get access to the *Link Tracker* module and its back-end functionalities." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:53 +msgid "Integrated with :doc:`Google Analytics <google_analytics>`, those trackers allow you to see the number of clicks and visitors to keep you on top of your marketing campaigns." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:55 +msgid "The integration with the :doc:`CRM </applications/sales/crm/track_leads/prospect_visits>` application allows you to understand where your leads and opportunities are coming from." +msgstr ""