diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 1410b48d9..fdd9133b8 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-09-01 15:11+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -809,7 +809,7 @@ msgid "Editions" msgstr "" #: ../../content/administration/install/install.rst:35 -msgid "There are two different Editions_ of Odoo: the Community and Enterprise versions. Using the Enterprise version is possible on our SaaS_ and accessing the code is restricted to Enterprise customers and partners. The Community version is freely available to anyone." +msgid "There are two different Editions_ of Odoo: the Community and Enterprise versions. Using the Enterprise version is possible on `Odoo Online`_ and accessing the code is restricted to Enterprise customers and partners. The Community version is freely available to anyone." msgstr "" #: ../../content/administration/install/install.rst:40 @@ -833,11 +833,15 @@ msgid "Demo_ instances require no local installation, just a web browser." msgstr "" #: ../../content/administration/install/install.rst:59 -msgid "SaaS" +#: ../../content/administration/maintain/domain_names.rst:136 +#: ../../content/administration/maintain/domain_names.rst:206 +#: ../../content/administration/maintain/supported_versions.rst:27 +#: ../../content/administration/upgrade/odoo_online.rst:3 +msgid "Odoo Online" msgstr "" #: ../../content/administration/install/install.rst:61 -msgid "Trivial to start with, fully managed and migrated by Odoo S.A., Odoo's SaaS_ provides private instances and starts out free. It can be used to discover and test Odoo and do non-code customizations (i.e. incompatible with custom modules or the Odoo Apps Store) without having to install it locally." +msgid "Trivial to start with, fully managed and migrated by Odoo S.A., `Odoo Online`_ provides private instances and starts out free. It can be used to discover and test Odoo and do non-code customizations (i.e. incompatible with custom modules or the Odoo Apps Store) without having to install it locally." msgstr "" #: ../../content/administration/install/install.rst:66 @@ -845,7 +849,7 @@ msgid "Can be used for both testing Odoo and long-term production use." msgstr "" #: ../../content/administration/install/install.rst:68 -msgid "Like demo_ instances, SaaS_ instances require no local installation, a web browser is sufficient." +msgid "Like demo_ instances, `Odoo Online`_ instances require no local installation, a web browser is sufficient." msgstr "" #: ../../content/administration/install/install.rst:75 @@ -1475,322 +1479,344 @@ msgstr "" msgid "Odoo manages payment and technical support for you." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:63 +#: ../../content/administration/maintain/domain_names.rst:62 +msgid "This offer doesn't include any mailbox. However, you can :ref:`configure your MX records ` to use your own email server or solution such as Google Workspace." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:65 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:71 +#: ../../content/administration/maintain/domain_names.rst:None +msgid "Clicking on Domain Names from an Odoo website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:73 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:78 -msgid "Next, fill in the form with your information to become the domain name owner." +#: ../../content/administration/maintain/domain_names.rst:None +msgid "The search of the domain name example.com shows which associated domains are available." msgstr "" #: ../../content/administration/maintain/domain_names.rst:80 +msgid "Next, fill in the form with your information to become the domain name owner." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:82 msgid "Your domain name is directly linked to your database, but you still have to :ref:`map your domain name with your website `." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:84 +#: ../../content/administration/maintain/domain_names.rst:86 msgid "Free domain names are also available for free Odoo Online databases (if you installed one app only, for example). In this case, Odoo reviews your request and your website to avoid abuse. This process may take up to three days." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:87 +#: ../../content/administration/maintain/domain_names.rst:89 msgid "This is not available for Odoo.sh databases yet." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:92 +#: ../../content/administration/maintain/domain_names.rst:94 msgid "Manage your domain name registered with Odoo" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:94 +#: ../../content/administration/maintain/domain_names.rst:96 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:104 +#: ../../content/administration/maintain/domain_names.rst:None +msgid "Management of the domain names linked to an Odoo database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:106 msgid "Please `submit a support ticket `_ if you need further assistance to manage your domain name." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:110 +#: ../../content/administration/maintain/domain_names.rst:112 msgid "Configure your existing domain name" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:112 +#: ../../content/administration/maintain/domain_names.rst:114 msgid "If you already own a domain name, you can use it to point to your website." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:114 +#: ../../content/administration/maintain/domain_names.rst:116 msgid "To avoid any issue with the :ref:`SSL certificate validation `, we highly recommend that you proceed with the following actions in this order:" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:117 +#: ../../content/administration/maintain/domain_names.rst:119 msgid ":ref:`Add a CNAME record ` on your domain name's DNS zone." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:118 +#: ../../content/administration/maintain/domain_names.rst:120 msgid ":ref:`Map your domain name with your Odoo database `." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:119 +#: ../../content/administration/maintain/domain_names.rst:121 msgid ":ref:`Map your domain name with your Odoo website `." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:124 +#: ../../content/administration/maintain/domain_names.rst:126 msgid "Add a CNAME record" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:126 +#: ../../content/administration/maintain/domain_names.rst:128 msgid "A **CNAME record** is a type of DNS record that points to the IP address of another website rather than to directly to an IP address." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:129 +#: ../../content/administration/maintain/domain_names.rst:131 msgid "You need a CNAME record that points to your Odoo database. The requirements are detailed in your database manager." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:134 -#: ../../content/administration/maintain/domain_names.rst:204 -#: ../../content/administration/maintain/supported_versions.rst:26 -msgid "Odoo Online" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:136 +#: ../../content/administration/maintain/domain_names.rst:138 msgid "The target address is the current address of your database, as defined at its creation (e.g., ``example.odoo.com``)" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:139 -#: ../../content/administration/maintain/domain_names.rst:218 -#: ../../content/administration/maintain/supported_versions.rst:26 +#: ../../content/administration/maintain/domain_names.rst:141 +#: ../../content/administration/maintain/domain_names.rst:220 +#: ../../content/administration/maintain/supported_versions.rst:27 #: ../../content/administration/odoo_sh.rst:5 #: ../../content/administration/upgrade/odoo_sh.rst:3 msgid "Odoo.sh" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:141 +#: ../../content/administration/maintain/domain_names.rst:143 msgid "Your project's main address is defined in :menuselection:`Settings --> Project Name`." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:143 +#: ../../content/administration/maintain/domain_names.rst:145 msgid "If you want to target a specific branch (production, staging or development), go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, and click on :guilabel:`How to set up my domain?`. A message indicates which address your CNAME record should target." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:148 -#: ../../content/administration/maintain/domain_names.rst:190 +#: ../../content/administration/maintain/domain_names.rst:150 +#: ../../content/administration/maintain/domain_names.rst:192 msgid "Open your domain name's manager dashboard." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:149 +#: ../../content/administration/maintain/domain_names.rst:151 msgid "Open the **DNS zone** management page for the domain name you want to configure." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:150 +#: ../../content/administration/maintain/domain_names.rst:152 msgid "Create a **CNAME record** pointing to the address of your database." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:152 +#: ../../content/administration/maintain/domain_names.rst:154 msgid "While Odoo suggests creating a CNAME record for your ``www.`` subdomain (``www.example.com``, you can of course use any domain name of your choice, with any subdomain (e.g., ``anything.example.com``)." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:157 +#: ../../content/administration/maintain/domain_names.rst:159 msgid "You own the domain name ``example.com``, and you have an Odoo Online database at the address ``example.odoo.com``. You want to access your Odoo database primarily with the domain ``www.example.com`` but also with the :ref:`naked domain ` ``example.com``." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:162 +#: ../../content/administration/maintain/domain_names.rst:164 msgid "To do so, you create a CNAME record for the ``www`` subdomain, with ``example.odoo.com`` as the target. The DNS zone manager generates the following rule and adds it to your DNS zone: ``www IN CNAME example.odoo.com.``" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:166 +#: ../../content/administration/maintain/domain_names.rst:168 msgid "You also create a redirection from ``example.com`` to ``wwww.example.com``." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:168 +#: ../../content/administration/maintain/domain_names.rst:170 msgid "Your new DNS records are propagated to all DNS servers." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:171 +#: ../../content/administration/maintain/domain_names.rst:173 msgid "Here are some specific guidelines to create a CNAME record:" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:173 +#: ../../content/administration/maintain/domain_names.rst:175 msgid "`GoDaddy `_" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:174 +#: ../../content/administration/maintain/domain_names.rst:176 msgid "`Namecheap `_" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:175 +#: ../../content/administration/maintain/domain_names.rst:177 msgid "`OVH `_" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:176 +#: ../../content/administration/maintain/domain_names.rst:178 msgid "`CloudFlare `_" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:177 +#: ../../content/administration/maintain/domain_names.rst:179 msgid "`Google Domains `_" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:182 +#: ../../content/administration/maintain/domain_names.rst:184 msgid "Naked domain" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:184 +#: ../../content/administration/maintain/domain_names.rst:186 msgid "A **naked domain** is a domain name that doesn't have any subdomain at the beginning of the address (e.g., ``odoo.com`` instead of ``www.odoo.com``)." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:187 +#: ../../content/administration/maintain/domain_names.rst:189 msgid "You may want your naked domain to redirect to your website as some visitors may not type the full domain name to access your website." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:191 +#: ../../content/administration/maintain/domain_names.rst:193 msgid "Create a **redirection** from the naked domain (``example.com``) to your main domain name (``www.example.com``)." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:195 +#: ../../content/administration/maintain/domain_names.rst:197 msgid "Depending on your domain name registrar, this redirection may be already pre-configured." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:200 +#: ../../content/administration/maintain/domain_names.rst:202 msgid "Map your domain name with your Odoo database" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:206 +#: ../../content/administration/maintain/domain_names.rst:208 msgid "Open your `database manager `_, click on the :guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on :guilabel:`Use my own domain` at the bottom of the right column." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:210 +#: ../../content/administration/maintain/domain_names.rst:212 msgid "Type the domain name you want to add to this database, then click on :guilabel:`Verify` to check if the CNAME record is correctly configured. Once done, click on :guilabel:`I confirm, it's done`." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:220 +#: ../../content/administration/maintain/domain_names.rst:0 +msgid "Verification of the CNAME records of a domain name before mapping it with a database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:222 msgid "Go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, type the domain name you want to add to this database, then click on :guilabel:`Add domain`." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:228 +#: ../../content/administration/maintain/domain_names.rst:0 +msgid "Mapping a domain name with an Odoo.sh branch" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:230 msgid ":ref:`Odoo.sh branches: settings tab `" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:231 +#: ../../content/administration/maintain/domain_names.rst:233 msgid "Make sure to :ref:`add a CNAME record ` to your domain name's DNS **before** mapping your domain name with your Odoo database." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:234 +#: ../../content/administration/maintain/domain_names.rst:236 msgid "Failing to do so may impede the validation of the :ref:`SSL certificate ` and would result in a *certificate name mismatch* error. This is often displayed by web browsers as a warning such as *\"Your connection is not private\"*." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:238 +#: ../../content/administration/maintain/domain_names.rst:240 msgid "If this is the case and you have added the domain name to your database's settings less than five days ago, wait 24 hours as the validation may still happen. Otherwise, please `submit a support ticket `_ including screenshots of your CNAME records." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:245 +#: ../../content/administration/maintain/domain_names.rst:247 msgid "SSL encryption (HTTPS protocol)" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:247 +#: ../../content/administration/maintain/domain_names.rst:249 msgid "**SSL encryption** is an encryption-based Internet security protocol. It allows your visitors to navigate your website through a secure connection, which appears as an ``https://`` protocol at the beginning of your web address, rather than a non-secure ``http://`` protocol." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:251 +#: ../../content/administration/maintain/domain_names.rst:253 msgid "Odoo generates a separate SSL certificate for each domain :ref:`mapped in the database manager `, using integration with `Let's Encrypt Certificate Authority and ACME protocol `_." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:256 +#: ../../content/administration/maintain/domain_names.rst:258 msgid "The certificate generation may take up to 24h." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:257 +#: ../../content/administration/maintain/domain_names.rst:259 msgid "Several attempts to validate your certificate are made during the five days following the moment you add your domain name in your database's settings." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:259 +#: ../../content/administration/maintain/domain_names.rst:261 msgid "If you already use another service, you can keep using it or simply change for Odoo." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:264 +#: ../../content/administration/maintain/domain_names.rst:266 msgid "Web base URL of a database" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:267 +#: ../../content/administration/maintain/domain_names.rst:269 msgid "If you have Odoo Website, you can disregard this part and directly :ref:`map your domain name with your website `." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:270 +#: ../../content/administration/maintain/domain_names.rst:272 msgid "The **web base URL** of a database, or **root URL** affects your main website address and all the links sent to your customers (e.g., quotations, portal links, etc.)." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:273 +#: ../../content/administration/maintain/domain_names.rst:275 msgid "To configure it, access your Odoo database with your custom address, then log in as an administrator of your database (any user in the *Settings* group) from the login screen." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:277 +#: ../../content/administration/maintain/domain_names.rst:279 msgid "Connecting to your database with the original Odoo subdomain address (e.g., ``example.odoo.com`` also updates the web base URL of your database. See below to prevent these automatic updates." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:280 +#: ../../content/administration/maintain/domain_names.rst:282 msgid "Alternatively, you can do it manually. To do so, activate the :ref:`developer mode `, then go to :menuselection:`Settings --> Technical --> System Parameters`." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:283 +#: ../../content/administration/maintain/domain_names.rst:285 msgid "Find the key called ``web.base.url`` (or create it if it does not exist) and enter the full address of your website as value, such as ``https://www.example.com``." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:287 +#: ../../content/administration/maintain/domain_names.rst:289 msgid "The URL must include the protocol ``https://`` (or ``http://``) and must not end with a slash (``/``)." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:290 +#: ../../content/administration/maintain/domain_names.rst:292 msgid "To prevent the automatic update of the web base URL when an administrator logs in the database, you can create the following System Parameter:" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:293 +#: ../../content/administration/maintain/domain_names.rst:295 msgid "key: ``web.base.url.freeze``" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:294 +#: ../../content/administration/maintain/domain_names.rst:296 msgid "value: ``True``" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:299 +#: ../../content/administration/maintain/domain_names.rst:301 msgid "Map your domain name with your website" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:301 +#: ../../content/administration/maintain/domain_names.rst:303 msgid "Mapping your domain name to your website isn't the same as mapping it with your database:" msgstr "" -#: ../../content/administration/maintain/domain_names.rst:303 +#: ../../content/administration/maintain/domain_names.rst:305 msgid "It defines your domain name as the main one for your website, helping search engines to index your website properly." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:305 +#: ../../content/administration/maintain/domain_names.rst:307 msgid "It defines your domain name as the base URL for your database, including the portal links sent by email to your customers." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:307 +#: ../../content/administration/maintain/domain_names.rst:309 msgid "If you have multiple websites, it maps your domain name with the appropriate website." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:309 +#: ../../content/administration/maintain/domain_names.rst:311 msgid "Go to :menuselection:`Website --> Configuration --> Settings --> Website Info`. If you have multiple websites, select the one you want to configure." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:312 +#: ../../content/administration/maintain/domain_names.rst:314 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:320 +#: ../../content/administration/maintain/domain_names.rst:None +msgid "Configuring https://www.example.com as the Domain of the website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:322 msgid "Mapping your domain name with your Odoo website prevents Google from indexing both your custom domain name ``www.example.com`` and your original odoo database address ``example.odoo.com``." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:323 +#: ../../content/administration/maintain/domain_names.rst:325 msgid "If both addresses are already indexed, it may take some time before Google removes the indexation of the second address. You may also try using the `Google Search Console `_ to fix this." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:328 +#: ../../content/administration/maintain/domain_names.rst:330 msgid "If you have multiple websites and companies on your database, make sure that you select the right :guilabel:`Company` in the website settings, next to the :guilabel:`Domain` settings. Doing so indicates Odoo which URL to use as the :ref:`base URL ` according to the company in use." msgstr "" -#: ../../content/administration/maintain/domain_names.rst:334 +#: ../../content/administration/maintain/domain_names.rst:336 msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr "" @@ -1922,6 +1948,10 @@ msgstr "" 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`." 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." msgstr "" @@ -1986,6 +2016,10 @@ msgstr "" 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:None +msgid "Client ID and Client Secret for Google OAuth." +msgstr "" + #: ../../content/administration/maintain/google_oauth.rst:84 msgid "Setup in Odoo" msgstr "" @@ -2010,6 +2044,11 @@ msgstr "" 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." msgstr "" +#: ../../content/administration/maintain/google_oauth.rst:None +#: ../../content/administration/maintain/google_oauth.rst:None +msgid "Configure Outgoing Email Servers in Odoo." +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`." msgstr "" @@ -2042,6 +2081,10 @@ msgstr "" msgid "Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` (instead of Testing) will display the following warning message:" msgstr "" +#: ../../content/administration/maintain/google_oauth.rst:None +msgid "OAuth is Limited to 100 Sensitive Scope Logins." +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." msgstr "" @@ -2054,6 +2097,10 @@ msgstr "" 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: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." msgstr "" @@ -2066,6 +2113,10 @@ msgstr "" msgid "If the :guilabel:`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:None +msgid "Forbidden you don't have the permission to access the requested resource." +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`." msgstr "" @@ -2078,6 +2129,10 @@ msgstr "" 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." msgstr "" +#: ../../content/administration/maintain/google_oauth.rst:None +msgid "Error 400 Redirect URI Mismatch." +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." msgstr "" @@ -2260,6 +2315,229 @@ msgstr "" msgid "Grab a :ref:`backup of your Odoo.sh production database `." msgstr "" +#: ../../content/administration/maintain/odoo_online.rst:3 +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*." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:None +msgid "Clicking on the user icon opens a drop-down menu. \"My databases\" button is highlighted." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:13 +msgid "Make sure you are connected as the administrator of the database you want to manage." +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 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:24 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:25 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:26 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:27 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:28 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:29 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:30 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:31 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:36 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:285 +#: ../../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)." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:0 +msgid "**If your Odoo database's version is lower than the latest major release:**" +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 +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." +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." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:70 +msgid "Duplicate databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:75 +msgid "Rename" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:77 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:82 +msgid "Download" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:84 +msgid "Download instantly a ZIP file with 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 `_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:93 +msgid "Domains" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:95 +msgid "Configure custom domains to access the database via another URL." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:98 +msgid ":doc:`domain_names`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:103 +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." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:110 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:539 +msgid "Delete" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:112 +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." +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:" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:None +msgid "A warning message is prompted before deleting a database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:126 +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." +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 `_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:130 +msgid "To delete your account, please get in touch with `Odoo Support `_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:135 +msgid "Contact Support" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:137 +msgid "Access the Odoo `support page `_ with your database's details already pre-filled." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:143 +msgid "Invite / Remove 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*." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:None +msgid "Clicking on \"Add more users\" adds additional email fields." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:152 +msgid "To remove users, select the users to remove and click on *Remove*." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:155 +msgid ":doc:`/applications/general/users/manage_users`" +msgstr "" + #: ../../content/administration/maintain/on_premise.rst:3 msgid "On-premise database management" msgstr "" @@ -2280,6 +2558,11 @@ msgstr "" msgid "If you are unable to register your database, you will likely encounter this message:" msgstr "" +#: ../../content/administration/maintain/on_premise.rst:None +msgid "Something went wrong while registering your database,\n" +"you can try again or contact Odoo Help" +msgstr "" + #: ../../content/administration/maintain/on_premise.rst:27 #: ../../content/administration/maintain/on_premise.rst:106 #: ../../content/administration/maintain/on_premise.rst:134 @@ -2359,6 +2642,11 @@ 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 +msgid "This database will expire in X days, you\n" +"have more users than your subscription allows" +msgstr "" + #: ../../content/administration/maintain/on_premise.rst:102 msgid "When the message appears you have 30 days before the expiration. The countdown is updated everyday." msgstr "" @@ -2383,6 +2671,10 @@ 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 +msgid "This database has expired." +msgstr "" + #: ../../content/administration/maintain/on_premise.rst:130 msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired." msgstr "" @@ -2419,213 +2711,6 @@ msgstr "" msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator `_ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button." msgstr "" -#: ../../content/administration/maintain/online.rst:3 -msgid "Online (SaaS) database management" -msgstr "" - -#: ../../content/administration/maintain/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*." -msgstr "" - -#: ../../content/administration/maintain/online.rst:13 -msgid "Make sure you are connected as the administrator of the database you want to manage." -msgstr "" - -#: ../../content/administration/maintain/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/online.rst:21 -msgid "Several actions are available:" -msgstr "" - -#: ../../content/administration/maintain/online.rst:23 -msgid ":ref:`online/upgrade`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:24 -msgid ":ref:`online/duplicate`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:25 -msgid ":ref:`online/rename`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:26 -msgid ":ref:`online/download`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:27 -msgid ":ref:`online/domains`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:28 -msgid ":ref:`online/tags`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:29 -msgid ":ref:`online/delete`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:30 -msgid ":ref:`online/contact-support`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:31 -msgid ":ref:`online/users`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:36 -#: ../../content/administration/odoo_sh/getting_started/branches.rst:285 -#: ../../content/administration/upgrade.rst:10 -msgid "Upgrade" -msgstr "" - -#: ../../content/administration/maintain/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)." -msgstr "" - -#: ../../content/administration/maintain/online.rst:0 -msgid "**If your Odoo database's version is lower than the latest major release:**" -msgstr "" - -#: ../../content/administration/maintain/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/online.rst:0 -msgid "**If your Odoo database's version is equal to or higher than the latest major release:**" -msgstr "" - -#: ../../content/administration/maintain/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/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/online.rst:56 -msgid ":doc:`../upgrade`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:57 -msgid ":doc:`supported_versions`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:62 -msgid "Duplicate" -msgstr "" - -#: ../../content/administration/maintain/online.rst:64 -msgid "Make an exact copy of the database to be able to perform testing without compromising the daily operations." -msgstr "" - -#: ../../content/administration/maintain/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." -msgstr "" - -#: ../../content/administration/maintain/online.rst:70 -msgid "Duplicate databases expire automatically after 15 days." -msgstr "" - -#: ../../content/administration/maintain/online.rst:75 -msgid "Rename" -msgstr "" - -#: ../../content/administration/maintain/online.rst:77 -msgid "Rename the database and its URL." -msgstr "" - -#: ../../content/administration/maintain/online.rst:82 -msgid "Download" -msgstr "" - -#: ../../content/administration/maintain/online.rst:84 -msgid "Download instantly a ZIP file with a backup of the database." -msgstr "" - -#: ../../content/administration/maintain/online.rst:87 -msgid "Databases are backed up daily according to the `Odoo Cloud SLA `_." -msgstr "" - -#: ../../content/administration/maintain/online.rst:93 -msgid "Domains" -msgstr "" - -#: ../../content/administration/maintain/online.rst:95 -msgid "Configure custom domains to access the database via another URL." -msgstr "" - -#: ../../content/administration/maintain/online.rst:98 -msgid ":doc:`domain_names`" -msgstr "" - -#: ../../content/administration/maintain/online.rst:103 -msgid "Tags" -msgstr "" - -#: ../../content/administration/maintain/online.rst:105 -msgid "Add tags to sort your databases out. You can search the tags in the search bar." -msgstr "" - -#: ../../content/administration/maintain/online.rst:110 -#: ../../content/administration/odoo_sh/getting_started/branches.rst:539 -msgid "Delete" -msgstr "" - -#: ../../content/administration/maintain/online.rst:112 -msgid "Delete a database instantly." -msgstr "" - -#: ../../content/administration/maintain/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." -msgstr "" - -#: ../../content/administration/maintain/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:" -msgstr "" - -#: ../../content/administration/maintain/online.rst:126 -msgid "Only an administrator can delete a database." -msgstr "" - -#: ../../content/administration/maintain/online.rst:127 -msgid "The database name is immediately available for a new database." -msgstr "" - -#: ../../content/administration/maintain/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 `_." -msgstr "" - -#: ../../content/administration/maintain/online.rst:130 -msgid "To delete your account, please get in touch with `Odoo Support `_." -msgstr "" - -#: ../../content/administration/maintain/online.rst:135 -msgid "Contact Support" -msgstr "" - -#: ../../content/administration/maintain/online.rst:137 -msgid "Access the Odoo `support page `_ with your database's details already pre-filled." -msgstr "" - -#: ../../content/administration/maintain/online.rst:143 -msgid "Invite / Remove Users" -msgstr "" - -#: ../../content/administration/maintain/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*." -msgstr "" - -#: ../../content/administration/maintain/online.rst:152 -msgid "To remove users, select the users to remove and click on *Remove*." -msgstr "" - -#: ../../content/administration/maintain/online.rst:155 -msgid ":doc:`/applications/general/users/manage_users`" -msgstr "" - #: ../../content/administration/maintain/supported_versions.rst:6 #: ../../content/administration/upgrade.rst:208 msgid "Supported versions" @@ -2636,277 +2721,289 @@ msgid "Odoo provides support and bug fixing **for the 3 last major versions** of msgstr "" #: ../../content/administration/maintain/supported_versions.rst:11 -msgid "Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online ` hosting every two months. Odoo Online users can then benefit from the latest features of Odoo." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:14 -msgid "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly." +msgid "Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online ` hosting every two months. Odoo Online users can then benefit from the latest features of Odoo." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:15 -msgid "Online versions are *not* released for Odoo.sh and On-Premise installations." +msgid "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:16 +msgid "Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:17 msgid "Online versions are listed below as *SaaS*." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:19 +#: ../../content/administration/maintain/supported_versions.rst:20 msgid "What's the support status of my Odoo?" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:21 +#: ../../content/administration/maintain/supported_versions.rst:22 msgid "This matrix shows the support status of every version." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:23 +#: ../../content/administration/maintain/supported_versions.rst:24 msgid "**Major releases are in bold type.**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:26 +#: ../../content/administration/maintain/supported_versions.rst:27 #: ../../content/administration/upgrade/on_premise.rst:3 msgid "On-Premise" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:26 +#: ../../content/administration/maintain/supported_versions.rst:27 msgid "Release date" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:26 +#: ../../content/administration/maintain/supported_versions.rst:27 msgid "End of support" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:28 -msgid "Odoo saas~15.2" +#: ../../content/administration/maintain/supported_versions.rst:29 +msgid "**Odoo 16.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:28 -#: ../../content/administration/maintain/supported_versions.rst:32 -#: ../../content/administration/maintain/supported_versions.rst:32 -#: ../../content/administration/maintain/supported_versions.rst:32 -#: ../../content/administration/maintain/supported_versions.rst:34 -#: ../../content/administration/maintain/supported_versions.rst:34 -#: ../../content/administration/maintain/supported_versions.rst:34 -#: ../../content/administration/maintain/supported_versions.rst:36 -#: ../../content/administration/maintain/supported_versions.rst:36 -#: ../../content/administration/maintain/supported_versions.rst:36 +#: ../../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 msgid "|green|" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:28 -#: ../../content/administration/maintain/supported_versions.rst:28 -#: ../../content/administration/maintain/supported_versions.rst:30 -#: ../../content/administration/maintain/supported_versions.rst:30 -#: ../../content/administration/maintain/supported_versions.rst:38 -#: ../../content/administration/maintain/supported_versions.rst:38 -#: ../../content/administration/maintain/supported_versions.rst:42 -#: ../../content/administration/maintain/supported_versions.rst:42 -#: ../../content/administration/maintain/supported_versions.rst:46 -#: ../../content/administration/maintain/supported_versions.rst:46 -#: ../../content/administration/maintain/supported_versions.rst:48 -#: ../../content/administration/maintain/supported_versions.rst:48 -#: ../../content/administration/maintain/supported_versions.rst:52 -#: ../../content/administration/maintain/supported_versions.rst:52 -#: ../../content/administration/maintain/supported_versions.rst:54 -#: ../../content/administration/maintain/supported_versions.rst:56 -#: ../../content/administration/maintain/supported_versions.rst:56 -#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../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: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: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 msgid "N/A" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:28 +#: ../../content/administration/maintain/supported_versions.rst:31 msgid "March 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:30 +#: ../../content/administration/maintain/supported_versions.rst:33 msgid "Odoo saas~15.1" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:30 -#: ../../content/administration/maintain/supported_versions.rst:38 -#: ../../content/administration/maintain/supported_versions.rst:40 -#: ../../content/administration/maintain/supported_versions.rst:40 -#: ../../content/administration/maintain/supported_versions.rst:40 -#: ../../content/administration/maintain/supported_versions.rst:42 -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:46 -#: ../../content/administration/maintain/supported_versions.rst:48 -#: ../../content/administration/maintain/supported_versions.rst:50 -#: ../../content/administration/maintain/supported_versions.rst:50 -#: ../../content/administration/maintain/supported_versions.rst:50 -#: ../../content/administration/maintain/supported_versions.rst:52 -#: ../../content/administration/maintain/supported_versions.rst:54 -#: ../../content/administration/maintain/supported_versions.rst:54 -#: ../../content/administration/maintain/supported_versions.rst:56 -#: ../../content/administration/maintain/supported_versions.rst:58 -#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../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 +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../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 msgid "|red|" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:30 +#: ../../content/administration/maintain/supported_versions.rst:33 msgid "February 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:32 +#: ../../content/administration/maintain/supported_versions.rst:35 msgid "**Odoo 15.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:32 -#: ../../content/administration/maintain/supported_versions.rst:40 +#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:43 msgid "October 2021" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:32 +#: ../../content/administration/maintain/supported_versions.rst:35 msgid "October 2024 (planned)" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:34 +#: ../../content/administration/maintain/supported_versions.rst:37 msgid "**Odoo 14.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:34 -#: ../../content/administration/maintain/supported_versions.rst:44 +#: ../../content/administration/maintain/supported_versions.rst:37 +#: ../../content/administration/maintain/supported_versions.rst:47 msgid "October 2020" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:34 +#: ../../content/administration/maintain/supported_versions.rst:37 msgid "October 2023 (planned)" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:36 +#: ../../content/administration/maintain/supported_versions.rst:39 msgid "**Odoo 13.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:36 -#: ../../content/administration/maintain/supported_versions.rst:50 +#: ../../content/administration/maintain/supported_versions.rst:39 +#: ../../content/administration/maintain/supported_versions.rst:53 msgid "October 2019" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:36 -msgid "October 2022 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:38 +#: ../../content/administration/maintain/supported_versions.rst:41 msgid "Odoo saas~12.3" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:38 +#: ../../content/administration/maintain/supported_versions.rst:41 msgid "August 2019" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:40 +#: ../../content/administration/maintain/supported_versions.rst:43 msgid "**Odoo 12.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:40 -#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:57 msgid "October 2018" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:42 +#: ../../content/administration/maintain/supported_versions.rst:45 msgid "Odoo saas~11.3" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:42 +#: ../../content/administration/maintain/supported_versions.rst:45 msgid "April 2018" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:44 +#: ../../content/administration/maintain/supported_versions.rst:47 msgid "**Odoo 11.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../content/administration/maintain/supported_versions.rst:61 msgid "October 2017" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:46 +#: ../../content/administration/maintain/supported_versions.rst:49 msgid "Odoo 10.saas~15" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:46 +#: ../../content/administration/maintain/supported_versions.rst:49 msgid "March 2017" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:51 msgid "Odoo 10.saas~14" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:51 msgid "January 2017" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:50 +#: ../../content/administration/maintain/supported_versions.rst:53 msgid "**Odoo 10.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:50 +#: ../../content/administration/maintain/supported_versions.rst:53 msgid "October 2016" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:52 +#: ../../content/administration/maintain/supported_versions.rst:55 msgid "Odoo 9.saas~11" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:52 +#: ../../content/administration/maintain/supported_versions.rst:55 msgid "May 2016" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:57 msgid "**Odoo 9.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:57 msgid "October 2015" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:56 +#: ../../content/administration/maintain/supported_versions.rst:59 msgid "Odoo 8.saas~6" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:56 +#: ../../content/administration/maintain/supported_versions.rst:59 msgid "February 2015" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:61 msgid "**Odoo 8.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:61 msgid "September 2014" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:63 +#: ../../content/administration/maintain/supported_versions.rst:66 msgid "|green| Supported version" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:65 +#: ../../content/administration/maintain/supported_versions.rst:68 msgid "|red| End-of-support" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:67 +#: ../../content/administration/maintain/supported_versions.rst:70 msgid "N/A Never released for this platform" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:69 +#: ../../content/administration/maintain/supported_versions.rst:72 msgid "🏁 Future version, not released yet" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:80 +#: ../../content/administration/maintain/supported_versions.rst:83 msgid "I run an older version of Odoo/OpenERP/TinyERP" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:82 +#: ../../content/administration/maintain/supported_versions.rst:85 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:84 +#: ../../content/administration/maintain/supported_versions.rst:87 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:86 +#: ../../content/administration/maintain/supported_versions.rst:89 msgid "Even though we don't support older versions, you can always `upgrade from any version `_." msgstr "" @@ -3251,6 +3348,10 @@ 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 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 msgid "Frequent Technical Questions" msgstr "" @@ -4347,7 +4448,7 @@ msgid "`Access your databases manager ` (i.e., Community t msgstr "" #: ../../content/administration/upgrade.rst:25 -msgid "Switching :ref:`hosting type ` (i.e., On-Premise to Online or Odoo.sh)" +msgid "Switching :ref:`hosting type ` (i.e., On-Premise to Odoo Online or Odoo.sh)" msgstr "" #: ../../content/administration/upgrade.rst:27 @@ -5382,7 +5493,7 @@ msgid "You restore it in your Production environment a few short hours later and msgstr "" #: ../../content/administration/upgrade.rst:57 -msgid ":doc:`Upgrade process for Odoo Online (SaaS) `" +msgid ":doc:`Upgrade process for Odoo Online `" msgstr "" #: ../../content/administration/upgrade.rst:58 @@ -5457,6 +5568,10 @@ msgstr "" msgid "Follow the instructions available per hosting type on the `website form `_ and select *Testing* purpose." msgstr "" +#: ../../content/administration/upgrade.rst:None +msgid "Selection of the \"Testing\" purpose in the upgrade form on Odoo" +msgstr "" + #: ../../content/administration/upgrade.rst:115 msgid "Test guidance" msgstr "" @@ -5482,6 +5597,10 @@ msgstr "" msgid "Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type." msgstr "" +#: ../../content/administration/upgrade.rst:0 +msgid "Selection of \"An issue related to my upgrade\" as Ticket Type in the support form on Odoo" +msgstr "" + #: ../../content/administration/upgrade.rst:139 msgid "If you choose another *Ticket Description* type, the request will be redirected to another team. This will slow down the processing and response time." msgstr "" @@ -5573,7 +5692,7 @@ msgid "What is covered by the Enterprise Licence?" msgstr "" #: ../../content/administration/upgrade.rst:228 -msgid "Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the following services at all times." +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 @@ -5745,7 +5864,7 @@ msgid "`Editions `_" msgstr "" #: ../../content/administration/upgrade/faq.rst:112 -msgid "Switching the hosting types (Self-Hosting vs. Online Hosting - SaaS vs. Cloud Platform - Odoo.sh)" +msgid "Switching the hosting types (On-premise vs. Odoo Online vs. Odoo.sh)" msgstr "" #: ../../content/administration/upgrade/faq.rst:114 @@ -5785,7 +5904,7 @@ msgid "How long is my test available for" msgstr "" #: ../../content/administration/upgrade/faq.rst:154 -msgid "An Odoo Online (SaaS) test database is available for one month by default. We can extend this trial period upon request. For Odoo.sh or on-premise, there is no restriction." +msgid "An Odoo Online test database is available for one month by default. We can extend this trial period upon request. For Odoo.sh or on-premise, there is no restriction." msgstr "" #: ../../content/administration/upgrade/faq.rst:158 @@ -5892,6 +6011,46 @@ 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" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:8 +msgid "Go to your `database manager `_" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:9 +msgid "Click on your profile icon and select *My Databases*." +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 action settings icon next to your main database and select the *Upgrade* option." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:0 +msgid "Selecting the action settings icon" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:19 +msgid "In the pop-up message that will appear, select Test Upgrade." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:0 +msgid "Selecting test upgrade" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:24 +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." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:28 +msgid "You can also see and access your test database from your *My Databases* page." +msgstr "" + #: ../../content/administration/upgrade/odoo_sh.rst:10 msgid "Odoo.sh is integrated with the upgrade platform to make the upgrade process easier." msgstr "" @@ -5900,6 +6059,10 @@ 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 +msgid "Click on the upgrade menu" +msgstr "" + #: ../../content/administration/upgrade/odoo_sh.rst:20 msgid "The suggested upgrade steps on Odoo.sh are:" msgstr "" @@ -5952,6 +6115,10 @@ 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 +msgid "Odoo.sh project and tabs" +msgstr "" + #: ../../content/administration/upgrade/odoo_sh.rst:62 msgid "The **latest production daily automatic backup** is sent to the `upgrade platform `_ to start the upgrade test process." msgstr "" @@ -5997,6 +6164,10 @@ 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 +msgid "View from the upgrade tab" +msgstr "" + #: ../../content/administration/upgrade/odoo_sh.rst:105 msgid "The actual process is **triggered as soon as you push a new commit** in your branch. Make sure you are pushing code that is compatible with the new version. For example by merging the code from your upgraded staging branch." msgstr "" @@ -6005,6 +6176,10 @@ 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 +msgid "View showing the progress of the upgrade" +msgstr "" + #: ../../content/administration/upgrade/odoo_sh.rst:118 msgid "Your database is unavailable throughout the process." msgstr "" @@ -6104,35 +6279,3 @@ msgstr "" #: ../../content/administration/upgrade/on_premise.rst:59 msgid "by Odoo (if you hold a subscription to 'Maintenance of Customizations')." msgstr "" - -#: ../../content/administration/upgrade/online_hosting.rst:3 -msgid "Odoo Online (SaaS)" -msgstr "" - -#: ../../content/administration/upgrade/online_hosting.rst:6 -msgid "Requesting a test upgrade" -msgstr "" - -#: ../../content/administration/upgrade/online_hosting.rst:8 -msgid "Go to your `database manager `_" -msgstr "" - -#: ../../content/administration/upgrade/online_hosting.rst:9 -msgid "Click on your profile icon and select *My Databases*." -msgstr "" - -#: ../../content/administration/upgrade/online_hosting.rst:14 -msgid "Click on the action settings icon next to your main database and select the *Upgrade* option." -msgstr "" - -#: ../../content/administration/upgrade/online_hosting.rst:19 -msgid "In the pop-up message that will appear, select Test Upgrade." -msgstr "" - -#: ../../content/administration/upgrade/online_hosting.rst:24 -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." -msgstr "" - -#: ../../content/administration/upgrade/online_hosting.rst:28 -msgid "You can also see and access your test database from your *My Databases* page." -msgstr "" diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot index 9cd1a3bb6..874eabb8d 100644 --- a/locale/sources/contributing.pot +++ b/locale/sources/contributing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -212,707 +212,687 @@ msgstr "" 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 -msgid "report: use to declare a :ref:`report action `" -msgstr "" - #: ../../content/contributing/development/coding_guidelines.rst:280 -msgid "act_window: use it if the record notation can't do what you want" +msgid "These tags are preferred over the *record* notation." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:282 -msgid "The 4 first tags are preferred over the *record* notation." -msgstr "" - -#: ../../content/contributing/development/coding_guidelines.rst:286 +#: ../../content/contributing/development/coding_guidelines.rst:284 msgid "XML IDs and naming" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:289 +#: ../../content/contributing/development/coding_guidelines.rst:287 msgid "Security, View and Action" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:291 +#: ../../content/contributing/development/coding_guidelines.rst:289 msgid "Use the following pattern :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:293 +#: ../../content/contributing/development/coding_guidelines.rst:291 msgid "For a menu: :samp:`{}_menu`, or :samp:`{}_menu_{do_stuff}` for submenus." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:294 +#: ../../content/contributing/development/coding_guidelines.rst:292 msgid "For a view: :samp:`{}_view_{}`, where *view_type* is ``kanban``, ``form``, ``tree``, ``search``, ..." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:296 +#: ../../content/contributing/development/coding_guidelines.rst:294 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:300 +#: ../../content/contributing/development/coding_guidelines.rst:298 msgid "For window actions: suffix the action name by the specific view information like :samp:`{}_action_view_{}`." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:302 +#: ../../content/contributing/development/coding_guidelines.rst:300 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:304 +#: ../../content/contributing/development/coding_guidelines.rst:302 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:309 +#: ../../content/contributing/development/coding_guidelines.rst:307 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:363 +#: ../../content/contributing/development/coding_guidelines.rst:361 msgid "Inheriting XML" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:365 +#: ../../content/contributing/development/coding_guidelines.rst:363 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:369 +#: ../../content/contributing/development/coding_guidelines.rst:367 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:380 +#: ../../content/contributing/development/coding_guidelines.rst:378 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:395 +#: ../../content/contributing/development/coding_guidelines.rst:393 #: ../../content/contributing/documentation.rst:204 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:861 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:863 #: ../../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:399 +#: ../../content/contributing/development/coding_guidelines.rst:397 msgid "Do not forget to read the :ref:`Security Pitfalls ` section as well to write secure code." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:403 +#: ../../content/contributing/development/coding_guidelines.rst:401 msgid "PEP8 options" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:405 +#: ../../content/contributing/development/coding_guidelines.rst:403 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:408 +#: ../../content/contributing/development/coding_guidelines.rst:406 msgid "E501: line too long" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:409 +#: ../../content/contributing/development/coding_guidelines.rst:407 msgid "E301: expected 1 blank line, found 0" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:410 +#: ../../content/contributing/development/coding_guidelines.rst:408 msgid "E302: expected 2 blank lines, found 1" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:413 +#: ../../content/contributing/development/coding_guidelines.rst:411 msgid "Imports" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:414 +#: ../../content/contributing/development/coding_guidelines.rst:412 msgid "The imports are ordered as" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:416 +#: ../../content/contributing/development/coding_guidelines.rst:414 msgid "External libraries (one per line sorted and split in python stdlib)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:417 +#: ../../content/contributing/development/coding_guidelines.rst:415 msgid "Imports of ``odoo``" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:418 +#: ../../content/contributing/development/coding_guidelines.rst:416 msgid "Imports from Odoo modules (rarely, and only if necessary)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:420 +#: ../../content/contributing/development/coding_guidelines.rst:418 msgid "Inside these 3 groups, the imported lines are alphabetically sorted." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:438 +#: ../../content/contributing/development/coding_guidelines.rst:436 msgid "Idiomatics of Programming (Python)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:440 +#: ../../content/contributing/development/coding_guidelines.rst:438 msgid "Always favor *readability* over *conciseness* or using the language features or idioms." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:441 +#: ../../content/contributing/development/coding_guidelines.rst:439 msgid "Don't use ``.clone()``" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:452 +#: ../../content/contributing/development/coding_guidelines.rst:450 msgid "Python dictionary : creation and update" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:477 +#: ../../content/contributing/development/coding_guidelines.rst:475 msgid "Use meaningful variable/class/method names" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:478 +#: ../../content/contributing/development/coding_guidelines.rst:476 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:490 +#: ../../content/contributing/development/coding_guidelines.rst:488 msgid "Multiple return points are OK, when they're simpler" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:510 +#: ../../content/contributing/development/coding_guidelines.rst:508 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:518 +#: ../../content/contributing/development/coding_guidelines.rst:516 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:521 +#: ../../content/contributing/development/coding_guidelines.rst:519 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:534 +#: ../../content/contributing/development/coding_guidelines.rst:532 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:545 +#: ../../content/contributing/development/coding_guidelines.rst:543 msgid "So, you can write ``if some_collection:`` instead of ``if len(some_collection):``." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:548 +#: ../../content/contributing/development/coding_guidelines.rst:546 msgid "Iterate on iterables" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:562 +#: ../../content/contributing/development/coding_guidelines.rst:560 msgid "Use dict.setdefault" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:578 +#: ../../content/contributing/development/coding_guidelines.rst:576 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:580 +#: ../../content/contributing/development/coding_guidelines.rst:578 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:585 +#: ../../content/contributing/development/coding_guidelines.rst:583 msgid "Programming in Odoo" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:587 +#: ../../content/contributing/development/coding_guidelines.rst:585 msgid "Avoid to create generators and decorators: only use the ones provided by the Odoo API." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:589 +#: ../../content/contributing/development/coding_guidelines.rst:587 msgid "As in python, use ``filtered``, ``mapped``, ``sorted``, ... methods to ease code reading and performance." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:594 -msgid "Make your method work in batch" -msgstr "" - -#: ../../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: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:619 +#: ../../content/contributing/development/coding_guidelines.rst:591 msgid "Propagate the context" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:620 +#: ../../content/contributing/development/coding_guidelines.rst:592 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:629 +#: ../../content/contributing/development/coding_guidelines.rst:601 msgid "Passing parameter in context can have dangerous side-effects." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:631 +#: ../../content/contributing/development/coding_guidelines.rst:603 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:637 -msgid "If you need to create a key context influencing the behavior of some object, choice 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*, ..." +#: ../../content/contributing/development/coding_guidelines.rst:609 +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:644 +#: ../../content/contributing/development/coding_guidelines.rst:616 msgid "Think extendable" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:646 +#: ../../content/contributing/development/coding_guidelines.rst:618 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:651 +#: ../../content/contributing/development/coding_guidelines.rst:623 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:677 +#: ../../content/contributing/development/coding_guidelines.rst:649 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:680 +#: ../../content/contributing/development/coding_guidelines.rst:652 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:683 +#: ../../content/contributing/development/coding_guidelines.rst:655 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:688 +#: ../../content/contributing/development/coding_guidelines.rst:660 msgid "Never commit the transaction" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:689 +#: ../../content/contributing/development/coding_guidelines.rst:661 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:710 +#: ../../content/contributing/development/coding_guidelines.rst:682 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:713 +#: ../../content/contributing/development/coding_guidelines.rst:685 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:717 +#: ../../content/contributing/development/coding_guidelines.rst:689 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:722 +#: ../../content/contributing/development/coding_guidelines.rst:694 msgid "inconsistent business data, usually data loss" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:723 +#: ../../content/contributing/development/coding_guidelines.rst:695 msgid "workflow desynchronization, documents stuck permanently" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:724 +#: ../../content/contributing/development/coding_guidelines.rst:696 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:735 +#: ../../content/contributing/development/coding_guidelines.rst:707 msgid "Here is the very simple rule:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:729 +#: ../../content/contributing/development/coding_guidelines.rst:701 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:733 +#: ../../content/contributing/development/coding_guidelines.rst:705 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: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 have in doubt!)" +#: ../../content/contributing/development/coding_guidelines.rst:709 +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:749 +#: ../../content/contributing/development/coding_guidelines.rst:721 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:756 +#: ../../content/contributing/development/coding_guidelines.rst:728 msgid "Use translation method correctly" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:758 +#: ../../content/contributing/development/coding_guidelines.rst:730 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:767 +#: ../../content/contributing/development/coding_guidelines.rst:739 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:770 +#: ../../content/contributing/development/coding_guidelines.rst:742 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:775 +#: ../../content/contributing/development/coding_guidelines.rst:747 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:818 +#: ../../content/contributing/development/coding_guidelines.rst:790 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:838 +#: ../../content/contributing/development/coding_guidelines.rst:810 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:845 +#: ../../content/contributing/development/coding_guidelines.rst:817 msgid "Symbols and Conventions" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:855 +#: ../../content/contributing/development/coding_guidelines.rst:827 msgid "Model name (using the dot notation, prefix by the module name) :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:848 +#: ../../content/contributing/development/coding_guidelines.rst:820 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:850 +#: ../../content/contributing/development/coding_guidelines.rst:822 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:854 +#: ../../content/contributing/development/coding_guidelines.rst:826 msgid "When defining *report* model (SQL views e.i.) : use ``.report.``, based on the Transient convention." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:857 +#: ../../content/contributing/development/coding_guidelines.rst:829 msgid "Odoo Python Class : use camelcase (Object-oriented style)." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:868 +#: ../../content/contributing/development/coding_guidelines.rst:840 msgid "Variable name :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:866 +#: ../../content/contributing/development/coding_guidelines.rst:838 msgid "use camelcase for model variable" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:867 +#: ../../content/contributing/development/coding_guidelines.rst:839 msgid "use underscore lowercase notation for common variable." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:868 +#: ../../content/contributing/development/coding_guidelines.rst:840 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:876 +#: ../../content/contributing/development/coding_guidelines.rst:848 msgid "``One2Many`` and ``Many2Many`` fields should always have *_ids* as suffix (example: sale_order_line_ids)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:877 +#: ../../content/contributing/development/coding_guidelines.rst:849 msgid "``Many2One`` fields should have *_id* as suffix (example : partner_id, user_id, ...)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:887 +#: ../../content/contributing/development/coding_guidelines.rst:859 msgid "Method conventions" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:879 +#: ../../content/contributing/development/coding_guidelines.rst:851 msgid "Compute Field : the compute method pattern is *_compute_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:880 +#: ../../content/contributing/development/coding_guidelines.rst:852 msgid "Search method : the search method pattern is *_search_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:881 +#: ../../content/contributing/development/coding_guidelines.rst:853 msgid "Default method : the default method pattern is *_default_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:882 +#: ../../content/contributing/development/coding_guidelines.rst:854 msgid "Selection method: the selection method pattern is *_selection_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:883 +#: ../../content/contributing/development/coding_guidelines.rst:855 msgid "Onchange method : the onchange method pattern is *_onchange_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:884 +#: ../../content/contributing/development/coding_guidelines.rst:856 msgid "Constraint method : the constraint method pattern is *_check_*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:885 +#: ../../content/contributing/development/coding_guidelines.rst:857 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:898 +#: ../../content/contributing/development/coding_guidelines.rst:870 msgid "In a Model attribute order should be" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:890 -msgid "Private attributes (``_name``, ``_description``, ``_inherit``, ...)" +#: ../../content/contributing/development/coding_guidelines.rst:862 +msgid "Private attributes (``_name``, ``_description``, ``_inherit``, ``_sql_constraints``, ...)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:891 -msgid "Default method and ``_default_get``" +#: ../../content/contributing/development/coding_guidelines.rst:863 +msgid "Default method and ``default_get``" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:892 +#: ../../content/contributing/development/coding_guidelines.rst:864 msgid "Field declarations" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:893 +#: ../../content/contributing/development/coding_guidelines.rst:865 msgid "Compute, inverse and search methods in the same order as field declaration" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:894 +#: ../../content/contributing/development/coding_guidelines.rst:866 msgid "Selection method (methods used to return computed values for selection fields)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:895 +#: ../../content/contributing/development/coding_guidelines.rst:867 msgid "Constrains methods (``@api.constrains``) and onchange methods (``@api.onchange``)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:896 +#: ../../content/contributing/development/coding_guidelines.rst:868 msgid "CRUD methods (ORM overrides)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:897 +#: ../../content/contributing/development/coding_guidelines.rst:869 msgid "Action methods" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:898 +#: ../../content/contributing/development/coding_guidelines.rst:870 msgid "And finally, other business methods." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:954 +#: ../../content/contributing/development/coding_guidelines.rst:926 msgid "Javascript and CSS" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:957 +#: ../../content/contributing/development/coding_guidelines.rst:929 msgid "Static files organization" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:959 +#: ../../content/contributing/development/coding_guidelines.rst:931 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:962 +#: ../../content/contributing/development/coding_guidelines.rst:934 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:967 +#: ../../content/contributing/development/coding_guidelines.rst:939 msgid "The convention is to organize the code according to the following structure:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:969 +#: ../../content/contributing/development/coding_guidelines.rst:941 msgid "*static*: all static files in general" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:971 +#: ../../content/contributing/development/coding_guidelines.rst:943 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:973 +#: ../../content/contributing/development/coding_guidelines.rst:945 msgid "*static/src*: the generic static source code folder" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:975 +#: ../../content/contributing/development/coding_guidelines.rst:947 msgid "*static/src/css*: all css files" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:976 +#: ../../content/contributing/development/coding_guidelines.rst:948 msgid "*static/fonts*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:977 +#: ../../content/contributing/development/coding_guidelines.rst:949 msgid "*static/img*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:978 +#: ../../content/contributing/development/coding_guidelines.rst:950 msgid "*static/src/js*" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:980 +#: ../../content/contributing/development/coding_guidelines.rst:952 msgid "*static/src/js/tours*: end user tour files (tutorials, not tests)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:982 +#: ../../content/contributing/development/coding_guidelines.rst:954 msgid "*static/src/scss*: scss files" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:983 +#: ../../content/contributing/development/coding_guidelines.rst:955 msgid "*static/src/xml*: all qweb templates that will be rendered in JS" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:985 +#: ../../content/contributing/development/coding_guidelines.rst:957 msgid "*static/tests*: this is where we put all test related files." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:987 +#: ../../content/contributing/development/coding_guidelines.rst:959 msgid "*static/tests/tours*: this is where we put all tour test files (not tutorials)." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:990 +#: ../../content/contributing/development/coding_guidelines.rst:962 msgid "Javascript coding guidelines" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:992 +#: ../../content/contributing/development/coding_guidelines.rst:964 msgid "``use strict;`` is recommended for all javascript files" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:993 +#: ../../content/contributing/development/coding_guidelines.rst:965 msgid "Use a linter (jshint, ...)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:994 +#: ../../content/contributing/development/coding_guidelines.rst:966 msgid "Never add minified Javascript Libraries" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:995 +#: ../../content/contributing/development/coding_guidelines.rst:967 msgid "Use camelcase for class declaration" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:997 +#: ../../content/contributing/development/coding_guidelines.rst:969 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:1002 +#: ../../content/contributing/development/coding_guidelines.rst:974 msgid "CSS coding guidelines" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1004 +#: ../../content/contributing/development/coding_guidelines.rst:976 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:1009 +#: ../../content/contributing/development/coding_guidelines.rst:981 msgid "Avoid using *id* tag" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1010 +#: ../../content/contributing/development/coding_guidelines.rst:982 msgid "Use Bootstrap native classes" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1011 +#: ../../content/contributing/development/coding_guidelines.rst:983 msgid "Use underscore lowercase notation to name class" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1016 +#: ../../content/contributing/development/coding_guidelines.rst:988 msgid "Git" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1019 +#: ../../content/contributing/development/coding_guidelines.rst:991 msgid "Configure your git" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1021 +#: ../../content/contributing/development/coding_guidelines.rst:993 msgid "Based on ancestral experience and oral tradition, the following things go a long way towards making your commits more helpful:" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1024 +#: ../../content/contributing/development/coding_guidelines.rst:996 msgid "Be sure to define both the user.email and user.name in your local git config" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1030 +#: ../../content/contributing/development/coding_guidelines.rst:1002 msgid "Be sure to add your full name to your Github profile here. Please feel fancy and add your team, avatar, your favorite quote, and whatnot ;-)" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1034 +#: ../../content/contributing/development/coding_guidelines.rst:1006 msgid "Commit message structure" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1036 +#: ../../content/contributing/development/coding_guidelines.rst:1008 msgid "Commit message has four parts: tag, module, short description and full description. Try to follow the preferred structure for your commit messages" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1059 +#: ../../content/contributing/development/coding_guidelines.rst:1031 msgid "Tag and module name" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1061 +#: ../../content/contributing/development/coding_guidelines.rst:1033 msgid "Tags are used to prefix your commit. They should be one of the following" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1063 +#: ../../content/contributing/development/coding_guidelines.rst:1035 msgid "**[FIX]** for bug fixes: mostly used in stable version but also valid if you are fixing a recent bug in development version;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1065 +#: ../../content/contributing/development/coding_guidelines.rst:1037 msgid "**[REF]** for refactoring: when a feature is heavily rewritten;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1066 +#: ../../content/contributing/development/coding_guidelines.rst:1038 msgid "**[ADD]** for adding new modules;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1067 +#: ../../content/contributing/development/coding_guidelines.rst:1039 msgid "**[REM]** for removing resources: removing dead code, removing views, removing modules, ...;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1069 +#: ../../content/contributing/development/coding_guidelines.rst:1041 msgid "**[REV]** for reverting commits: if a commit causes issues or is not wanted reverting it is done using this tag;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1071 +#: ../../content/contributing/development/coding_guidelines.rst:1043 msgid "**[MOV]** for moving files: use git move and do not change content of moved file otherwise Git may loose track and history of the file; also used when moving code from one file to another;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1074 +#: ../../content/contributing/development/coding_guidelines.rst:1046 msgid "**[REL]** for release commits: new major or minor stable versions;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1075 +#: ../../content/contributing/development/coding_guidelines.rst:1047 msgid "**[IMP]** for improvements: most of the changes done in development version are incremental improvements not related to another tag;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1077 +#: ../../content/contributing/development/coding_guidelines.rst:1049 msgid "**[MERGE]** for merge commits: used in forward port of bug fixes but also as main commit for feature involving several separated commits;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1079 +#: ../../content/contributing/development/coding_guidelines.rst:1051 msgid "**[CLA]** for signing the Odoo Individual Contributor License;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1080 +#: ../../content/contributing/development/coding_guidelines.rst:1052 msgid "**[I18N]** for changes in translation files;" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1082 +#: ../../content/contributing/development/coding_guidelines.rst:1054 msgid "After tag comes the modified module name. Use the technical name as functional name may change with time. If several modules are modified, list them or use various to tell it is cross-modules. Unless really required or easier avoid modifying code across several modules in the same commit. Understanding module history may become difficult." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1089 +#: ../../content/contributing/development/coding_guidelines.rst:1061 msgid "Commit message header" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1091 +#: ../../content/contributing/development/coding_guidelines.rst:1063 msgid "After tag and module name comes a meaningful commit message header. It should be self explanatory and include the reason behind the change. Do not use single words like \"bugfix\" or \"improvements\". Try to limit the header length to about 50 characters for readability." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1096 +#: ../../content/contributing/development/coding_guidelines.rst:1068 msgid "Commit message header should make a valid sentence once concatenated with ``if applied, this commit will
``. For example ``[IMP] base: prevent to archive users linked to active partners`` is correct as it makes a valid sentence ``if applied, this commit will prevent users to archive...``." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1102 +#: ../../content/contributing/development/coding_guidelines.rst:1074 msgid "Commit message full description" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1104 +#: ../../content/contributing/development/coding_guidelines.rst:1076 msgid "In the message description specify the part of the code impacted by your changes (module name, lib, transversal object, ...) and a description of the changes." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1107 +#: ../../content/contributing/development/coding_guidelines.rst:1079 msgid "First explain WHY you are modifying code. What is important if someone goes back to your commit in about 4 decades (or 3 days) is why you did it. It is the purpose of the change." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1111 +#: ../../content/contributing/development/coding_guidelines.rst:1083 msgid "What you did can be found in the commit itself. If there was some technical choices involved it is a good idea to explain it also in the commit message after the why. For Odoo R&D developers \"PO team asked me to do it\" is not a valid why, by the way." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1115 +#: ../../content/contributing/development/coding_guidelines.rst:1087 msgid "Please avoid commits which simultaneously impact multiple modules. Try to split into different commits where impacted modules are different. It will be helpful if we need to revert changes in a given module separately." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1119 +#: ../../content/contributing/development/coding_guidelines.rst:1091 msgid "Don't hesitate to be a bit verbose. Most people will only see your commit message and judge everything you did in your life just based on those few sentences. No pressure at all." msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1123 +#: ../../content/contributing/development/coding_guidelines.rst:1095 msgid "**You spend several hours, days or weeks working on meaningful features. Take some time to calm down and write clear and understandable commit messages.**" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1126 +#: ../../content/contributing/development/coding_guidelines.rst:1098 msgid "If you are an Odoo R&D developer the WHY should be the purpose of the task you are working on. Full specifications make the core of the commit message. **If you are working on a task that lacks purpose and specifications please consider making them clear before continuing.**" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1131 +#: ../../content/contributing/development/coding_guidelines.rst:1103 msgid "Finally here are some examples of correct commit messages :" msgstr "" -#: ../../content/contributing/development/coding_guidelines.rst:1154 +#: ../../content/contributing/development/coding_guidelines.rst:1126 msgid "Use the long description to explain the *why* not the *what*, the *what* can be seen in the diff" msgstr "" @@ -1566,6 +1546,10 @@ 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 +msgid "Three tips to take good screenshots for the Odoo documentation." +msgstr "" + #: ../../content/contributing/documentation/content_guidelines.rst:210 msgid "Resizing the window's width is the most important step to do as Odoo's responsive design automatically resizes all fields to match the window's width." msgstr "" @@ -1994,6 +1978,10 @@ msgstr "" msgid "The ``image`` markup allows inserting images in a document." msgstr "" +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0 +msgid "Create an invoice." +msgstr "" + #: ../../content/contributing/documentation/rst_cheat_sheet.rst:458 msgid "Add the :code:`:class: o-no-modal` `option `_ to an image to prevent opening it in a modal." msgstr "" @@ -2193,182 +2181,190 @@ msgid "Code blocks" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:720 -msgid "Content tabs" -msgstr "" - -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:723 -msgid "The `tabs` markup may not work well in some situations. In particular:" -msgstr "" - -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:725 -msgid "The tabs' headers cannot be translated." -msgstr "" - -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:726 -msgid "A tab cannot contain :ref:`headings `." +msgid "Spoilers" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:727 -msgid "An :ref:`alert block ` cannot contain tabs." +msgid "**42**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:728 -msgid "A tab cannot contain :ref:`custom anchors `." +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:738 +msgid "Content tabs" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:733 -msgid "Basic tabs" -msgstr "" - -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:735 -msgid "Basic tabs are useful to split the content into multiple options. The `tabs` markup is used to define sequence of tabs. Each tab is then defined with the `tab` markup followed by a label." +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:741 +msgid "The `tabs` markup may not work well in some situations. In particular:" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:743 -msgid "Odoo Online" +msgid "The tabs' headers cannot be translated." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:744 +msgid "A tab cannot contain :ref:`headings `." msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:745 -msgid "Content dedicated to Odoo Online users." +msgid "An :ref:`alert block ` cannot contain tabs." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:747 -msgid "Odoo.sh" -msgstr "" - -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:749 -msgid "Alternative for Odoo.sh users." +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:746 +msgid "A tab cannot contain :ref:`custom anchors `." msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:751 -msgid "On-premise" +msgid "Basic tabs" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:753 +msgid "Basic tabs are useful to split the content into multiple options. The `tabs` markup is used to define sequence of tabs. Each tab is then defined with the `tab` markup followed by a label." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:761 +msgid "Odoo Online" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:763 +msgid "Content dedicated to Odoo Online users." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:765 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:767 +msgid "Alternative for Odoo.sh users." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:769 +msgid "On-premise" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:771 msgid "Third version for On-premise users." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:774 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:792 msgid "Nested tabs" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:776 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:794 msgid "Tabs can be nested inside one another." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:783 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:801 msgid "Stars" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:787 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:805 msgid "The Sun" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:789 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:807 msgid "The closest star to us." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:791 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:809 msgid "Proxima Centauri" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:793 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:811 msgid "The second closest star to us." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:795 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:813 msgid "Polaris" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:797 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:815 msgid "The North Star." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:799 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:817 msgid "Moons" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:803 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:821 msgid "The Moon" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:805 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:823 msgid "Orbits the Earth." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:807 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:825 msgid "Titan" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:809 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:827 msgid "Orbits Jupiter." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:846 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:864 msgid "Group tabs" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:848 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:866 msgid "Group tabs are special tabs that synchronize based on a group label. The last selected group is remembered and automatically selected when the user returns to the page or visits another page with the tabs group. The `group-tab` markup is used to define group tabs." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:857 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:859 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:871 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:875 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:877 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:889 msgid "C++" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:865 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:867 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:886 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:883 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:885 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:904 msgid "Java" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:938 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:956 msgid "Code tabs" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:940 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:958 msgid "Code tabs are essentially :ref:`group tabs ` that treat the content as a :ref:`code block `. The `code-tab` markup is used to define a code tab. Just as for the `code-block` markup, the language defines the syntax highlighting of the tab. If set, the label is used instead of the language for grouping tabs." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:991 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1009 msgid "Document metadata" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:993 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1011 msgid "Sphinx supports document-wide metadata markups that specify a behavior for the entire page." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:994 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1012 msgid "They must be placed between colons (`:`) at the top of the source file." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:997 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1015 msgid "**Metadata**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:997 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1015 msgid "**Purpose**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:999 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1017 msgid "`show-content`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:999 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1017 msgid "Make a toctree page accessible from the navigation menu." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1001 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1019 msgid "`show-toc`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1001 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1019 msgid "Show the table of content on a page that has the `show-content` metadata markup." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1004 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1022 msgid "`code-column`" msgstr "" @@ -2380,59 +2376,59 @@ msgstr "" msgid "For example, see :doc:`/applications/finance/accounting/getting_started/memento`." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1009 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1027 msgid "`hide-page-toc`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1009 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1027 msgid "Hide the \"On this page\" sidebar and use full page width for the content." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1011 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1029 msgid "`custom-css`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1011 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1029 msgid "Link CSS files (comma-separated) to the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1013 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1031 msgid "`custom-js`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1013 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1031 msgid "Link JS files (comma-separated) to the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1015 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1033 msgid "`classes`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1015 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1033 msgid "Assign the specified classes to the `
` element of the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1017 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1035 msgid "`orphan`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1017 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1035 msgid "Suppress the need to include the document in a toctree." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1019 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1037 msgid "`nosearch`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1019 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1037 msgid "Exclude the document from search results." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1025 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1043 msgid "Formatting tips" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1030 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1048 msgid "Break the line but not the paragraph" msgstr "" @@ -2444,15 +2440,15 @@ msgstr "" msgid "A second line that follows a line break." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1048 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1066 msgid "Escape markup symbols (Advanced)" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1050 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1068 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:1054 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:1072 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 4b855bcfd..6b4f1096b 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-09-01 15:11+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -45,121 +45,98 @@ msgid "Bank and cash" msgstr "" #: ../../content/applications/finance/accounting/bank/feeds.rst:5 +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:123 msgid "Bank feeds" msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:3 +#: ../../content/applications/finance/accounting/others/multi_currency.rst:143 msgid "Bank statements" msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/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." +msgid "Importing your bank statements allows you to keep track of your bank account transactions and reconcile them with the ones recorded in Odoo." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:9 -msgid "We recommend you use bank synchronization for more efficiency. Please read the related documentation: :doc:`bank_synchronization`." +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:8 +msgid "We recommend using :doc:`the bank synchronization feature ` for more efficiency. However, if you do not want to use it or if your bank is not yet supported, other options exist:" msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/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:" +msgid "Import the bank statement files delivered by your bank;" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:15 -msgid "Import the bank statement files delivered by your bank" +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:13 +msgid "Register the bank statements manually." msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:16 -msgid "Register the bank statements manually" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/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/feeds/bank_statements.rst:18 msgid "Odoo supports multiple file formats to import bank statements:" msgstr "" +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:20 +msgid "SEPA recommended Cash Management format (CAMT.053);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:21 +msgid "Comma-separated values (.CSV);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:22 +msgid "Open Financial Exchange (.OFX);" +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:23 -msgid "SEPA recommended Cash Management format (CAMT.053)" +msgid "Quicken Interchange Format (.QIF);" msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:24 -msgid "Comma-separated values (.CSV)" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:25 -msgid "Open Financial Exchange (.OFX)" +msgid "Belgium: Coded Statement of Account (.CODA)." msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:26 -msgid "Quicken Interchange Format (.QIF)" +msgid "To import a file, go to the Accounting dashboard and click on :guilabel:`Import (Statements)` under the :guilabel:`Bank` window, or click on the drop-down menu (:guilabel:`⋮`) button and then on :guilabel:`Import Statement`." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:27 -msgid "Belgium: Coded Statement of Account (.CODA)" +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:None +msgid "Import a bank statement file in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/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*." +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:34 +msgid "Next, select the file you want to import and click on :guilabel:`Upload`." msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:36 -msgid "Next, select the file you want to import and click on *Import*." +msgid "Once the file uploaded, the **import widget** helps you set formatting options and **map** the different columns you want to import. You also can :guilabel:`test` the bank statement file before importing it to your database." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/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." +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:None +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:None +msgid "Register bank statements manually in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/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/feeds/bank_statements.rst:45 msgid "Register bank statements manually" msgstr "" +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:47 +msgid "If needed, you can also record your bank statements manually. To do so, go to the :guilabel:`Accounting dashboard` and click on the :guilabel:`Create Statements` under the :guilabel:`Bank` window. Alternatively, you can click the drop-down menu (:guilabel:`⋮`) button, and then :guilabel:`New Statement`." +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:52 -msgid "If needed, you can also record your bank statements manually." +msgid "To ease the reconciliation process, make sure to fill out the :guilabel:`Partner` field. You can also type in the payments’ references in the :guilabel:`Label` field. Add a new line for each transaction written on the original bank statement." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/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 -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 -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 -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 -msgid ":doc:`bank_synchronization`" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:72 -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:10 -#: ../../content/applications/finance/accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:44 -#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:72 -#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:16 -msgid "Todo" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:72 -msgid "add doc link to new documentation about reconciliation" +#: ../../content/applications/finance/accounting/bank/feeds/bank_statements.rst:61 +msgid "The **Ending Balance** and the **Computed Balance** should have the same amount. If this is not the case, make sure there are no mistakes in the transactions’ amounts." msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:3 -msgid "Bank synchronization: Automatic import" +msgid "Bank synchronization: automatic import" msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:5 @@ -167,43 +144,44 @@ msgid "Odoo can synchronize directly with your bank institution to get all bank msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:8 -msgid "To check if your bank is compatible with Odoo, go to `Odoo Accounting Features `_, and click on *See list of supported institutions*." +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:15 -msgid "More than 20,000 institutions around the world are supported." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:12 +msgid "Odoo supports more than 25,000 institutions around the world." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:17 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:14 msgid "To connect to the banks, Odoo uses multiple web-services:" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:19 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:16 msgid "**Plaid**: United States of America and Canada" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:20 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:17 msgid "**Yodlee**: Worldwide" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:21 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:18 msgid "**Salt Edge**: Europe (:doc:`more information `)" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:22 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:19 msgid "**Ponto**: Europe (:doc:`more information `)" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:25 -msgid "Bank synchronization is not available for trial databases." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:20 +msgid "**EnableBanking**: Scandinavian countries" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:28 +#: ../../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/reconciliation/reconciliation_models.rst:69 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:9 +#: ../../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/bank_accounts.rst:76 #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:16 #: ../../content/applications/finance/accounting/bank/setup/manage_cash_register.rst:9 #: ../../content/applications/finance/accounting/bank/setup/outstanding_accounts.rst:20 @@ -221,9 +199,7 @@ msgstr "" #: ../../content/applications/finance/accounting/others/adviser/budget.rst:21 #: ../../content/applications/finance/accounting/others/analytic/purchases_expenses.rst:18 #: ../../content/applications/finance/accounting/others/analytic/timesheets.rst:16 -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:16 -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:15 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:22 +#: ../../content/applications/finance/accounting/others/multi_currency.rst:15 #: ../../content/applications/finance/accounting/payables/pay/check.rst:11 #: ../../content/applications/finance/accounting/payables/pay/sepa.rst:30 #: ../../content/applications/finance/accounting/payables/supplier_bills/invoice_digitization.rst:22 @@ -240,11 +216,11 @@ msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:15 #: ../../content/applications/finance/accounting/reporting/declarations/intrastat.rst:19 #: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:60 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:14 #: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:19 #: ../../content/applications/finance/accounting/taxation/taxes/eu_distance_selling.rst:30 #: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:27 #: ../../content/applications/finance/accounting/taxation/taxes/retention.rst:23 -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:12 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:29 #: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:13 #: ../../content/applications/finance/payment_acquirers.rst:227 @@ -258,212 +234,220 @@ msgstr "" msgid "Configuration" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:31 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:26 msgid "On-Premise users" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:33 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:28 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:39 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:34 msgid "https://production.odoofin.com/" msgstr "" +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:37 +msgid "First synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:39 +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 -msgid "First Synchronization" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:44 -msgid "You can start synchronization either by going to :menuselection:`Accounting --> Configuration --> Add a Bank Account` or via the configuration bar on the accounting dashboard." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/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: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 adblocker is disabled." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:45 +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:53 -msgid "During your first synchronization, you will be asked for a phone number to secure your account. The reason we ask for such information is that we don't want your data falling into the wrong hands. Therefore, if we detect suspicious activity on your account, we block all requests coming from your account, and you need to reactivate it using that phone number. 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." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:49 +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:60 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:54 +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 +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 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:64 -msgid "You can find all your synchronizations by going to :menuselection:`Accounting --> Configuration --> Online Synchronization`." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:67 +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:68 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:71 msgid "Synchronize manually" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:70 -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 *Synchronize Now* button on the dashboard." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:73 +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:78 -msgid "Or you can go to :menuselection:`Accounting --> Configuration --> Online Synchronization`, select your institution and then click on the *Fetch Transactions* button." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:77 +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:86 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:82 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:92 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:88 msgid "Issues" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:95 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:91 msgid "Synchronization in error" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:97 -msgid "To report a connection error to the `Odoo support `_, go to :menuselection:`Accounting --> Configuration --> Online Synchronization`, select the connection that failed, and copy the error description and the reference." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:93 +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:102 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:98 msgid "Synchronization disconnected" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:104 -msgid "If your connection with the proxy is disconnected, you can reconnect with the proxy using the *Reconnect* button." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:100 +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:108 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:104 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:115 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:111 msgid "Migration process for users having installed Odoo before December 2020" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:117 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:113 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:120 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:116 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:123 -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 the *Install* button to install the new module." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:119 +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:131 -msgid "Finally, make sure all your users refresh their Odoo page by pressing CTRL+F5." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:125 +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 +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 +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 +msgid "By default, `account_online_synchronization` is installed automatically with Accounting." msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:135 -msgid "All previous synchronizations are disconnected during the installation and won't work anymore. You can find them directly in the synchronization menu (:menuselection:`Accounting --> Configuration --> 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:139 -msgid "Please 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:141 -msgid "By default *account_online_synchronization* is installed automatically with Accounting." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:144 #: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:95 #: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:78 msgid "FAQ" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:147 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:138 msgid "The synchronization is not working in real-time. Is that normal?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:149 -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 *Accounting dashboard*, and click on the *Synchronize Now* button. You can also synchronize and fetch transactions through :menuselection:`Accounting --> Configuration --> Online Synchronization`. Some providers only allow one refresh per day, so it is possible that clicking on *Synchronize Now* does not get your latest transactions if you already performed such action earlier in the day." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:140 +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:156 -msgid "A transaction can be visible on your bank account, but not be fetched if it has the status *Pending*. Only transactions with the *Posted* status will be retrieved. If it is not *Posted* yet, you will have to wait until the status changes." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:148 +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:161 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:153 msgid "Is the Online Bank Synchronization feature included in my contract?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:163 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:155 msgid "**Community Version**: No, this feature is not included in the Community Version." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:164 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:156 msgid "**Online Version**: Yes, even if you benefit from the One App Free contract." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:165 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:157 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:168 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:160 msgid "Some banks have a status \"Beta.\" What does this mean?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:170 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:162 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:176 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:168 msgid "Why do my transactions only synchronize when I refresh manually?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:178 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:170 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:183 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:175 msgid "Not all of my past transactions are in Odoo, why?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:185 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:177 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:188 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:180 msgid "Why don't I see any transactions?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:190 -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 --> Configuration --> Online Synchronization` to click on the *Fetch Accounts* button on the connection." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:182 +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:194 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:187 msgid "There may also be no new transactions." msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:196 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:189 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:200 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:193 msgid "How can I update my bank credentials?" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:202 -msgid "You can update your credentials by going to :menuselection:`Accounting --> Configuration --> Online Synchronization`, open the connection you want to update your credentials and click on the *Update Credentials* button." +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:195 +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:207 +#: ../../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`" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:208 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:201 #: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:110 msgid ":doc:`ponto`" msgstr "" -#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:209 +#: ../../content/applications/finance/accounting/bank/feeds/bank_synchronization.rst:202 #: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:123 msgid ":doc:`saltedge`" msgstr "" @@ -476,6 +460,10 @@ msgstr "" 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 +msgid "Logo of the Ponto brand" +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:13 msgid "**Odoo** can synchronize directly with your bank to get all bank statements imported automatically into your database." msgstr "" @@ -504,6 +492,10 @@ msgstr "" msgid "Once you are logged in, create an *organization*." msgstr "" +#: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:0 +msgid "Fill out the form to add an organization in Ponto." +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:0 msgid "Go to :menuselection:`Accounts --> Live`, and click on *Add account*." msgstr "" @@ -516,6 +508,10 @@ msgstr "" 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 +msgid "Add bank accounts to your Ponto account." +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/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 "" @@ -540,12 +536,16 @@ msgstr "" 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 +msgid "Selection of the accounts you wish to synchronize with Odoo." +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/ponto.rst:64 msgid "Finish the flow." msgstr "" #: ../../content/applications/finance/accounting/bank/feeds/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 at the second step." +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 @@ -607,6 +607,11 @@ msgstr "" 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/ponto.rst:122 +#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:109 +msgid ":doc:`bank_synchronization`" +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:3 msgid "Salt Edge as bank synchronization provider" msgstr "" @@ -615,6 +620,10 @@ msgstr "" 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 +msgid "Salt Edge Logo" +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:13 msgid "Odoo can synchronize directly with your bank to get all bank statements imported automatically into your database." msgstr "" @@ -639,14 +648,26 @@ msgstr "" 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 +msgid "Email address to provide to Salt Edge for the creation of your account." +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:37 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 +msgid "Salt Edge Login page." +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:44 msgid "Make sure you give your consent by checking the consent checkbox." msgstr "" +#: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:0 +msgid "Salt Edge give consent page." +msgstr "" + #: ../../content/applications/finance/accounting/bank/feeds/saltedge.rst:50 msgid "Complete the synchronization by following the steps." msgstr "" @@ -702,228 +723,397 @@ msgid "Miscellaneous" msgstr "" #: ../../content/applications/finance/accounting/bank/misc/interbank.rst:3 -msgid "Do a bank wire transfer from one bank to another" +msgid "Internal transfer" msgstr "" #: ../../content/applications/finance/accounting/bank/misc/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." +msgid "In Odoo, internal money transfers can be made in a few clicks. You need at least either two bank accounts, two cash journals, or one bank account and one cash journal." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:11 +msgid "An internal transfer account is automatically created on your database based on your company's localization and depending on your country’s legislation. If needed, the default :guilabel:`Internal transfer account` can be modified by going to :menuselection:`Accounting app --> Configuration --> Settings` and then under the :guilabel:`Default Accounts` section." msgstr "" #: ../../content/applications/finance/accounting/bank/misc/interbank.rst:17 -msgid "Check your Chart of Accounts and default transfer account" +msgid "At least two bank accounts are needed to make internal transfers. Refer to :doc:`Bank and cash accounts section <../setup/bank_accounts>` to see how to add an additional bank account to your database." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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`." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:22 +msgid "Register an internal transfer from one bank to another" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:25 -msgid "Your chart of accounts will be pre-installed depending on the country specified during your registration, it cannot be changed." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:24 +msgid "Let's say you have two bank accounts registered on your database and you want to transfer 1,000 USD from Bank A to Bank B." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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 -msgid "Create a second bank account / Journal" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/misc/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 -msgid "By saving the changes you now have 2 bank accounts." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:56 -msgid "Register an internal transfer from one bank to another." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/misc/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/misc/interbank.rst:28 msgid "Log an internal transfer" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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`." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:30 +msgid "From the Accounting Dashboard, click on the drop-down selection button (:guilabel:`⋮`) on one of your banks. In the :guilabel:`New` column click on :guilabel:`Internal Transfer` and enter the information related to the transfer." msgstr "" +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:None +msgid "Fill in the information related to your internal transfer" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:39 +msgid "Fill in the :guilabel:`Memo` field for automatic reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:41 +msgid ":guilabel:`Save` and :guilabel:`Confirm` to register your internal transfer. The money is now booked in the transfer account and another payment is **automatically** created in the destination journal (Bank B)." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:46 +msgid "Bank journal (Bank A)" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:52 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:69 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:119 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:139 +#: ../../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 "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:53 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:70 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:120 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:140 +#: ../../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:157 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:68 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:82 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:99 +msgid "**Debit**" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:54 #: ../../content/applications/finance/accounting/bank/misc/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." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:121 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:141 +#: ../../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:157 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:68 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:82 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:99 +msgid "**Credit**" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:76 -msgid "The memo is important if you wish to automatically reconcile (see `Import bank statements and reconcile`_)." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:55 +msgid "Outstanding Payments account" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:82 -msgid "Save and confirm the changes to register the payment." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:57 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:73 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:123 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:144 +msgid "$1,000" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:58 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:75 +msgid "**Internal transfer account**" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:89 -msgid "Import bank statements and reconcile" +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:59 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:77 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:127 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:146 +msgid "**$1,000**" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:63 +msgid "Automated booking - Bank journal (BANK B)" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:72 +msgid "Outstanding Receipts account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:80 +msgid "There are one outstanding payment and one outstanding receipt pending in your two bank account journals, because the bank statement confirming the sending and receiving of the money has not been booked yet." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:None +msgid "Outstanding Payments/Receipts pending bank statement booking" msgstr "" #: ../../content/applications/finance/accounting/bank/misc/interbank.rst:91 -msgid "Note that the bank balance computed by Odoo is different that the last statement of your bank." +msgid "Manage and reconcile bank statements" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:93 +msgid "The next step is to book the bank statements to finalize the transaction by creating, :doc:`importing <../feeds/bank_statements>`, or :doc:`synchronizing <../feeds/bank_synchronization>` your :guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the :guilabel:`Reconcile` button." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:None +msgid "Transaction lines to be filled in prior to reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:114 -msgid "The following window will open:" +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:103 +msgid ":doc:`../reconciliation/use_cases`" msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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" +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:105 +msgid "In the next window, choose counterparts for the payment - in this example, the outstanding payment account - then click :guilabel:`Validate`." msgstr "" -#: ../../content/applications/finance/accounting/bank/misc/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." +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:None +msgid "Reconcile your payment" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:113 +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:133 +msgid "Bank journal entry" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:122 +msgid "Outstanding Payment" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:125 +msgid "Bank Account (BANK A)" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:129 +msgid "The same steps must be repeated once you receive the bank statement related to Bank B. Book and reconcile your bank statement lines." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:142 +msgid "Outstanding Receipt" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/misc/interbank.rst:145 +msgid "Bank Account (BANK B)" msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation.rst:5 msgid "Bank reconciliation" msgstr "" +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:3 +msgid "Cash reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:5 +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 +msgid "In Payment status of invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:16 +msgid "Cash logs" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:18 +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 +msgid "Create a new cash log." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:25 +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 +msgid "Select Cash journal upon payment registration." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:34 +msgid "Go back to your :guilabel:`Accounting Dashboard`, and click again on :guilabel:`New transactions`. Click on the :guilabel:`Add a line` button in the :guilabel:`Transactions` tab, and enter the total of cash earned during the day. Add a label name according to your needs. Input the amount displayed under :guilabel:`Computed Balance` in the :guilabel:`Ending Balance` field, and make sure it matches your end cash float." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:40 +msgid "Once certain the **computed balance** is correct, click :guilabel:`Save`, :guilabel:`Post`, and then :guilabel:`Reconcile`. This will take you to the **bank reconciliation** page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:44 +msgid "Cash payments reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:46 +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 +msgid "Cash payments reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:57 +msgid "If your ending cash balance is **over** or **under** the computed balance, add another :guilabel:`Transaction` line corresponding to the **over** or **under** amount in order to match it later during reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:62 +msgid "Cash reconciliation bypass" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:67 +msgid "Bypassing the cash journal is recommended **only for organizations** that do not need a cash report or do not wish to reconcile cash." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:70 +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 +msgid "Configuration tab of the cash journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/cash_transactions.rst:81 +msgid "In case you use cash to pay expenses, advance employees, are required to keep records of cash flows, or use anything resembling a cash box, you can benefit from creating a second **cash journal** that *does* use the **outstanding accounts**. This way, you can both generate *and* reconcile bank statements when closing your POS session or your books at the end of the day." +msgstr "" + #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:3 -msgid "Reconciliation Models" +msgid "Reconciliation models" msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:5 -msgid "Once the bank statements are correctly imported, it is essential to *reconcile* the records properly and ensure all *Journal Entries* are balanced and in agreement. To ease and speed up the reconciliation process, you can configure **Reconciliation Models**, which are particularly useful with recurrent entries such as bank fees." +msgid "Once the bank statements are correctly imported, it is essential to reconcile the records properly and ensure all **journal entries** are balanced and in agreement. To ease and speed up the reconciliation process, you can configure **reconciliation models**, which are particularly useful with **recurrent entries** such as bank fees." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:10 -msgid "Add a link to the Reconciliation process in the paragraph above, once the doc will have been updated." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:11 +msgid "Reconciliation models are also useful when handling *Cash Discounts*. Please refer to :doc:`the cash discounts <../../receivables/customer_invoices/cash_discounts>` for more information." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:14 -msgid "Reconciliation Models are also useful to handle *Cash Discounts*. Please refer to :doc:`this documentation <../../receivables/customer_invoices/cash_discounts>` for more information." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:18 +msgid "Types of reconciliation models" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:21 -msgid "Types of Reconciliation Models" +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:20 +msgid "There are three types of reconciliation models:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:22 +msgid ":ref:`Write-off button `" msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:23 -msgid "There are three types of Reconciliation Models:" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:25 -msgid ":ref:`Write-off Button `" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:26 msgid ":ref:`Suggestion of counterpart values `" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:27 +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:24 msgid ":ref:`Match existing invoices/bills `" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:32 +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:29 msgid "Manually create a write-off on clicked button" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:34 -msgid "When you are reconciling an entry with an *Open Balance*, you can use the buttons available under the *Manual Operations* tab to pre-fill all the values automatically, before validating the reconciliation. Each button is a different Reconciliation Model." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:31 +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:45 +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +msgid "Example of a reconciliation model with a write-off button in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:42 msgid "Suggest counterpart values" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:47 -msgid "This type of Reconciliation Model suggests immediately counterpart values that only need to be validated. This automation is based on a set of rules defined in the reconciliation model." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:44 +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:57 +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +msgid "Example of a reconciliation model that suggests counterpart values in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:55 msgid "Match existing invoices/bills" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:59 -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." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:57 +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:71 -msgid "To manage or create new **Reconciliation Models**, go to :menuselection:`Accounting --> Reconciliation --> Reconciliation Models`. Alternatively, you can also open this menu from the Accounting Overview, by going to your Bank Journal card, clicking on the three little dots, and then on *Reconciliation Models*." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +msgid "Example of a reconciliation model that matches existing invoices and bills automatically\n" +"in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:81 -msgid "The first entry, named *Invoices Matching Rule*, is the one responsible for the current matching of invoices and bills. Therefore, it is advised to leave it at the top of the list and not to delete it." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:69 +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:85 -msgid "Open the model you want to modify, or click on *Create* to create a new one, then fill out the form." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +msgid "Open the reconciliation model menu from the overview dashboard in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:88 +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:78 +msgid "The first entry, :guilabel:`Invoices Matching Rule`, is responsible for the current matching of invoices and bills. Therefore, it is advised to leave it at the top of the list and not delete it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:82 +msgid "Open the model you want to modify or click on :guilabel:`Create` to create a new one, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:86 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:52 msgid "Type" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:90 -msgid "See :ref:`above ` for an explanation about the different types of Reconciliation Models." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:88 +msgid "See :ref:`types of reconciliation models ` for an explanation about the different types of reconciliation models." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:94 -msgid "If the *Documents* application is installed on your database, an additional **Activity type** field appears when *To check* is ticked. Selecting the value *Reconciliation request* implies that, whenever you use this model, a *Request Document* window pops up to request a document from a user." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:92 +msgid "If the *Documents* application is installed on your database, an additional :guilabel:`Activity type` field appears when :guilabel:`To Check` is ticked. Selecting the value :guilabel:`Reconciliation request` implies that whenever you use this model, a :guilabel:`Request Document` window pops up to request a document from the user." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:98 +msgid "Conditions on bank statement line" msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:100 -msgid "Conditions on Bank Statement Line" +msgid "Define here all the conditions that should be fulfilled for the reconciliation model to be applied. Depending on the :guilabel:`Type` of model you choose, different options are available." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:102 -msgid "Define here all the conditions that are required for a Reconciliation Model to be applied." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:104 +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:105 -msgid "If a record matches with several Reconciliation Models, the first one in the *sequence* of models will be applied. The sequence is simply the order of the models in the *list view*. They can be rearranged by dragging-and-dropping the handle next to the name." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +msgid "Conditions for the reconciliation model to be applied in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:112 +msgid "Counterpart values" msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:114 -msgid "Counterpart Values" +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:116 -msgid "This section comprises the values that are applied by the Reconciliation Model." +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:None +msgid "Counterparts values of a reconciliation model in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:118 -msgid "If the value to reconcile needs to be written-off in two separate accounts, click on *Add a second line*." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:127 +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:124 msgid ":doc:`use_cases`" msgstr "" -#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:128 +#: ../../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:129 +#: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:126 msgid ":doc:`../../receivables/customer_invoices/cash_discounts`" msgstr "" @@ -935,9 +1125,6 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/overview.rst:5 #: ../../content/applications/finance/accounting/others/adviser/budget.rst:6 #: ../../content/applications/finance/accounting/others/analytic/purchases_expenses.rst:6 -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:6 -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:6 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:6 #: ../../content/applications/finance/accounting/reporting/overview.rst:5 #: ../../content/applications/finance/accounting/reporting/overview/customize.rst:6 msgid "Overview" @@ -1037,118 +1224,163 @@ msgid "Setup" msgstr "" #: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:3 -msgid "Bank Accounts" +msgid "Bank accounts" msgstr "" #: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:5 -msgid "You can manage as many **Bank Accounts** as needed on your database. Configuring them well allows you to make sure that all your banking data is up to date and ready for the reconciliation with your *Journal Entries*." +msgid "You can manage as many bank or cash accounts as needed on your database. Configuring them well allows you to have all your banking data up-to-date and ready for :doc:`reconciliation <../../bank/reconciliation/use_cases>` with your journal entries." msgstr "" #: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:9 -msgid "In Odoo Accounting, each Bank Account is configured to have a dedicated *Journal* which is configured to post all entries in a dedicated *Account*." +msgid "In Odoo Accounting, each bank account has a dedicated journal set to post all entries in a dedicated account. Both the journal and the account are automatically created and configured whenever you add a bank account." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:12 -msgid "Whenever you add a Bank Account, a dedicated journal and a dedicated account are automatically created and configured." +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:14 +msgid "Cash journals and accounts must be configured manually." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:15 -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." +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:16 +msgid "Bank journals are displayed by default on the :guilabel:`Accounting Dashboard` in the form of cards which include action buttons." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:25 -msgid "Add a new Bank Account" +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:None +msgid "Bank journals are displayed on the Accounting Dashboard and contain action buttons" 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>`." +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:26 +msgid "Manage your bank and cash accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:29 +msgid "Connect your bank for automatic synchronization" msgstr "" #: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:31 -msgid "Bank Synchronization" +msgid "To connect your bank account to your database, go to :menuselection:`Accounting --> Configuration --> Banks: Add a Bank Account`, select your bank in the list, click on :guilabel:`Connect`, and follow the instructions." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:33 -msgid "Connect your bank account to your database and have your bank statements synced automatically." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:35 -msgid "To synchronize a new bank account, go to :menuselection:`Accounting --> Configuration`, click on *Add a Bank Account*, then find your bank in the list, click on *Connect*, and follow the instructions on-screen." -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." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:48 -msgid "Manual configuration" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:50 -msgid "If your Bank Institution can’t be synchronized automatically, or if you prefer not to sync it with your database, you may also configure your bank account manually." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:53 -msgid "To add a new bank account manually, go to :menuselection:`Accounting --> Configuration`, click on *Add a Bank Account*, then on *Create it*, and fill out the form." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:56 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:65 -msgid "**Name**: the bank account's name, as displayed on Odoo." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:57 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:66 -msgid "**Account Number**: your bank account number (IBAN in Europe)." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:58 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:67 -msgid "**Bank**: click on *Create and Edit* to configure the bank's details. Add the bank institution's name and its Identifier Code (BIC or SWIFT)." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:60 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:69 -msgid "**Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By default, Odoo creates a new Journal with this Short Code." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:62 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:71 -msgid "**Journal**: This field is displayed if you have an existing Bank Journal that is not linked yet to a bank account. If so, then select the *Journal* you want to use to record the financial transactions linked to this bank account or create a new one by clicking on *Create and Edit*." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:67 -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:75 -msgid "Advanced configuration" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:77 -msgid "To edit an existing bank account, go to :menuselection:`Accounting --> Configuration --> Bank Accounts`, and open the bank account you want to modify." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:80 -msgid "If you need to edit the bank account details, go to the *Bank Account* field and click on the *External Link* button next to the list arrow. There, you can edit the bank account's number, Account Holder, Account Holder Name, and your Bank Institution's details by clicking on the *External Link* next to the *Bank* field. These details are used to register some payments." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:85 -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:93 +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:36 +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:135 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:192 msgid ":doc:`../../bank/feeds/bank_synchronization`" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:94 -msgid ":doc:`../feeds/bank_statements`" +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:39 +msgid "Create a bank account" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:95 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:194 -msgid "`Odoo Tutorials: Accounting Basics `_" +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:41 +msgid "If your banking institution is not available in Odoo, or if you don't want to connect your bank account to your database, you can configure your bank account manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:44 +msgid "To manually add a bank account, go to :menuselection:`Accounting --> Configuration --> Banks: Add a Bank Account`, click on :guilabel:`Create it` (at the bottom right), and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:48 +msgid "Odoo automatically detects the bank account type (e.g., IBAN) and enables some features accordingly." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:50 +msgid "A default bank journal is available and can be used to configure your bank account by going to :menuselection:`Accounting --> Configuration --> Accounting: Journals --> Bank`. Open it and edit the different fields to match your bank account information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:55 +msgid "Create a cash journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:57 +msgid "To create a new cash journal, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals`, click on :guilabel:`Create` and select :guilabel:`Cash` in the :guilabel:`Type` field." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:60 +msgid "For more information on the accounting information fields, read the :ref:`bank_accounts/configuration` section of this page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:64 +msgid "A default cash journal is available and can be used straight away. You can review it by going to :menuselection:`Accounting --> Configuration --> Accounting: Journals --> Cash`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:68 +msgid "Edit an existing bank or cash journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:70 +msgid "To edit an existing bank journal, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` and select the journal you want to modify." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:78 +msgid "You can edit the accounting information and bank account number according to your needs." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:None +msgid "Manually configure your bank information" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:85 +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:108 +msgid ":doc:`../../others/multi_currency`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:86 +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:136 +msgid ":doc:`../../bank/feeds/bank_statements`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:87 +msgid ":doc:`../../bank/setup/outstanding_accounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:90 +msgid "Suspense account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:92 +msgid "Bank statement transactions are posted on the :guilabel:`Suspense Account` until the final reconciliation allows finding the right account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:96 +msgid "Profit and loss accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:98 +msgid "The :guilabel:`Profit Account` is used to register a profit when the ending balance of a cash register differs from what the system computes, while the :guilabel:`Loss Account` is used to register a loss when the ending balance of a cash register differs from what the system computes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:103 +msgid "Currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:105 +msgid "You can edit the currency used to enter the statements." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:111 +msgid "Account number" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:113 +msgid "If you need to **edit your bank account details**, click on the external link arrow next to your :guilabel:`Account Number`. On the new page, click on the external link arrow next to your :guilabel:`Bank` and update your bank information accordingly. These details are used when registering payments." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:None +msgid "Edit your bank information" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:125 +msgid ":guilabel:`Bank Feeds` defines how the bank statements are registered. Three options are available:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:127 +msgid ":guilabel:`Undefined yet`, which should be selected when you don’t know yet if you will synchronize your bank account with your database or not." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:129 +msgid ":guilabel:`Import (CAMT, CODA, CSV, OFX, QIF)`, which should be selected if you want to import your bank statement using a different format." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/setup/bank_accounts.rst:131 +msgid ":guilabel:`Automated Bank Synchronization`, which should be selected if your bank is synchronized with your database." msgstr "" #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:3 @@ -1203,6 +1435,10 @@ 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 +msgid "Example of a created bank journal." +msgstr "" + #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:59 msgid "Upon creation of the journal, Odoo automatically links the bank account to the journal. It can be found under :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`." msgstr "" @@ -1215,6 +1451,10 @@ 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 +msgid "How to set a bill currency." +msgstr "" + #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:74 msgid "Note that you can pay a foreign bill with another currency. In that case, Odoo automatically converts between the two currencies." msgstr "" @@ -1227,14 +1467,26 @@ 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 +msgid "View of the Unrealized Gains/Losses journal." +msgstr "" + #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:89 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 +msgid "Menu to manually change exchange rates." +msgstr "" + #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:97 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 +msgid "Banner to reset back to Odoo's rates." +msgstr "" + #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:104 msgid "In order to update your **balance sheet** with the amount of the :guilabel:`adjustment` column, click on the :guilabel:`Adjustment Entry` button. In the pop-up window, select a :guilabel:`Journal`, :guilabel:`Expense Account` and :guilabel:`Income Account` to calculate and process the **unrealized gains and losses**." msgstr "" @@ -1247,6 +1499,10 @@ 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 +msgid "Unrealized Currency Gains/Losses report once adjusted." +msgstr "" + #: ../../content/applications/finance/accounting/bank/setup/manage_cash_register.rst:3 msgid "Manage a cash register" msgstr "" @@ -1353,6 +1609,10 @@ msgstr "" msgid "From your :guilabel:`Accounting Dashboard`, click on the menu selection ⋮ of the journal you want to configure, and click on :guilabel:`Configuration`, then open the :guilabel:`Incoming/Outgoing Payments` tab. To display the outstanding accounts column, click on the toggle button and check the :guilabel:`Outstanding Receipts/Payments accounts`, then update the account." msgstr "" +#: ../../content/applications/finance/accounting/bank/setup/outstanding_accounts.rst:None +msgid "Select the toggle button and click on outstanding Accounts" +msgstr "" + #: ../../content/applications/finance/accounting/bank/setup/outstanding_accounts.rst:45 msgid "If you do not specify an outstanding payments account or an outstanding receipts account for a specific journal, Odoo uses the default outstanding accounts." msgstr "" @@ -1459,7 +1719,7 @@ msgid "Responsables Inscriptos (166 Accounts)." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:68 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:240 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:239 msgid "Configure Master data" msgstr "" @@ -1514,13 +1774,13 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:117 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:161 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:94 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:322 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:321 msgid "Partner" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:120 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:164 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:325 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:324 msgid "Identification Type and VAT" msgstr "" @@ -1544,7 +1804,7 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:198 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:130 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:69 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:243 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:242 #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:111 #: ../../content/applications/finance/accounting/taxation/taxes.rst:5 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:3 @@ -1590,7 +1850,7 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:172 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:224 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:274 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:273 msgid "Document Types" msgstr "" @@ -1662,7 +1922,9 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:259 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:148 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/france.rst:194 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:296 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:94 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:295 +#: ../../content/applications/finance/accounting/others/multi_currency.rst:99 msgid "Journals" msgstr "" @@ -1748,7 +2010,7 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:291 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:178 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:348 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:347 msgid "Usage and testing" msgstr "" @@ -2041,7 +2303,6 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:515 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:653 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:64 msgid "Vendor Bills" msgstr "" @@ -2090,7 +2351,7 @@ msgid "In case it’s not a valid AFIP authorization the value “Rejected” wi msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:566 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:477 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:476 msgid "Special Use cases" msgstr "" @@ -2186,14 +2447,26 @@ msgstr "" msgid "Configure the *KeyPay API*." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:0 +msgid "Odoo Accounting settings includes a section for the Australian Loclization" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:25 msgid "More fields become visible after clicking on *Enable KeyPay Integration*." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:0 +msgid "Enabling KeyPay Integration in Odoo Accounting displays new fields in the settings" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:31 msgid "You can find the API Key in the *My Account* section of the KeyPay platform." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:0 +msgid "\"Account Details\" section on the KeyPay dashboard" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:37 msgid "The **Payroll URL** is pre-filled with ``https://keypay.yourpayroll.com.au``. *Please do not change it.*" msgstr "" @@ -2202,6 +2475,10 @@ msgstr "" msgid "You can find the **Business ID** in the KeyPay URL. (i.e., ``189241``)" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:0 +msgid "The KeyPay \"Business ID\" number is in the URL" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:45 msgid "You can choose any Odoo journal to post the payslip entries." msgstr "" @@ -2214,10 +2491,18 @@ msgstr "" 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." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:None +msgid "Example of a KeyPay Journal Entry in Odoo Accounting (Australia)" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:59 msgid "The API sync is triggered by scheduled actions." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:0 +msgid "Scheduled Actions settings for KeyPay Payroll in Odoo (debug mode)" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:65 msgid "KeyPay payslip entries also work based on double-entry bookkeeping. Debit must equal credit (like in Odoo)." msgstr "" @@ -2226,6 +2511,10 @@ msgstr "" msgid "The accounts used by KeyPay are defined in the section **Payroll settings**." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/australia.rst:None +msgid "Chart of Accounts menu in KeyPay" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/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." msgstr "" @@ -2266,6 +2555,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Chilean module to install on Odoo." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:43 msgid "When you install a database from scratch selecting Chile as country, Odoo will automatically install the base module: Chile - Accounting." msgstr "" @@ -2290,6 +2583,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Chilean company fiscal data." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:76 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:186 msgid "Electronic Invoice Data" @@ -2299,6 +2596,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Chilean edi environment settings." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:87 msgid "Configure DTE Incoming email server" msgstr "" @@ -2307,6 +2608,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Incoming email server configuration for Chilean DTE." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:97 msgid "For your Go-live make sure you archive/remove from your inbox all the emails related to vendor bills that are not required to be processed in Odoo." msgstr "" @@ -2320,6 +2625,14 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Digital certificate access." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Digital certificate configuration." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:114 msgid "A certificate can be shared between several users. If this is the case leave the user field empty, so all your billing users can use the same one. On the other hand, if you need to restrict the certificate for a particular user, just define the users in the certificate." msgstr "" @@ -2337,9 +2650,12 @@ msgstr "" msgid "The report Propuesta F29 requires two values that need to be defined as part of the company configuration:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Fiscal reports parameters." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:134 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:226 -#: ../../content/applications/finance/accounting/others/multicurrencies.rst:5 msgid "Multicurrency" msgstr "" @@ -2347,7 +2663,13 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Currency reate service for Chile." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:145 +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:3 +#: ../../content/applications/finance/accounting/others/multi_currency.rst:87 msgid "Chart of accounts" msgstr "" @@ -2380,6 +2702,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Chilean identification types for partners." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:174 msgid "TaxpayerType" msgstr "" @@ -2388,14 +2714,26 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Chilean taxpayer types for partners." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:188 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Chilean electronic invoice data for partners." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:200 msgid "As part of the localization module, the taxes are created automatically with their related financial account and configuration." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Chilean taxes list." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:210 msgid "Chile has several tax types, the most common ones are:" msgstr "" @@ -2409,7 +2747,7 @@ msgid "ILA (Impuesto a la Ley de Alcholes). Taxes for alcoholic drinks. It has a msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:217 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:265 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:264 msgid "Fiscal Positions" msgstr "" @@ -2429,6 +2767,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Chilean fiscal document types list." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:253 msgid "The Journal related to the Invoice, identifying if the journal uses documents." msgstr "" @@ -2507,6 +2849,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Document type configuration on Journal." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:307 msgid "For the Chilean localization, it is important to define the default Debit and Credit accounts as they are required for one of the debit notes use cases." msgstr "" @@ -2547,6 +2893,10 @@ msgstr "" msgid "Save the CAF." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Steps to add a new CAF." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:345 msgid "Once loaded, the status changes to *In Use*. At this moment, when a transaction is used for this document type, the invoice number takes the first folio in the sequence." msgstr "" @@ -2567,6 +2917,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Diagram with Electronic invoice transactions." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:370 msgid "Customer invoice Emission" msgstr "" @@ -2579,6 +2933,10 @@ msgstr "" msgid "You can manually change the document type if needed." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Document type selection on invoices." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:383 msgid "Documents type 33: Electronic Invoice must have at least one item with tax, otherwise the SII rejects the document validation." msgstr "" @@ -2602,10 +2960,18 @@ msgstr "" msgid "The DTE SII status is set as: Pending to be sent." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:0 +msgid "DTE XML File displayed in chatter." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:401 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Transition of DTE statuses." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:410 msgid "In the first step the DTE is sent to the SII, you can manually send it using the button: Enviar Ahora, a SII Tack number is generated and assigned to the invoice, you can use this number to check the details the SII sent back by email. The DTE status is updated to Ask for Status." msgstr "" @@ -2614,10 +2980,18 @@ msgstr "" msgid "Once the SII response is received Odoo updates the DTE Status, in case you want to do it manually just click on the button: Verify on SII. The result can either be Accepted, Accepted With Objection or Rejected." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:0 +msgid "Identification transaction for invoice and Status update." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:424 msgid "There are several internal status in the SII before you get Acceptance or Rejection, in case you click continuously the Button Verify in SII, you will receive in the chatter the detail of those intermediate statuses:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:0 +msgid "Descprtion of each DTE status in the chatter." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:432 msgid "The final response from the SII, can take on of these values:" msgstr "" @@ -2630,6 +3004,10 @@ msgstr "" msgid "**Accepted with objections:** Indicates the invoice information is correct but a minor issue was identified, nevertheless our document is now fiscally valid and it's automatically sent to the customer." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:0 +msgid "Email track once it is sent to the customer." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:445 msgid "**Rejected:** Indicates the information in the invoice is incorrect and needs to be corrected, the detail of the issue is received in the emails you registered in the SII, if it is properly configured in Odoo, the details are also retrieved in the chatter once the email server is processed." msgstr "" @@ -2650,6 +3028,10 @@ msgstr "" msgid "Post the invoice again." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:0 +msgid "Message when an invoice is rejected." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:462 msgid "Crossed references" msgstr "" @@ -2658,8 +3040,13 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Invoice tab with origin document number and data." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:474 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:450 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:136 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:449 msgid "Invoice PDF Report" msgstr "" @@ -2667,6 +3054,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Barcode and fiscal elements in the invoice report." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:484 msgid "If you are hosted in Odoo SH or On-Premise, you should manually install the ``pdf417gen`` library. Use the following command to install it: ``pip install pdf417gen``." msgstr "" @@ -2695,6 +3086,10 @@ msgstr "" msgid "The field DTE acceptation status is updated automatically." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Message with the commercial acceptance from the customer." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:504 msgid "Processed for Claimed invoices" msgstr "" @@ -2703,8 +3098,12 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Invoice Comercial status updated to Claimed." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:515 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:426 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:425 msgid "Common Errors" msgstr "" @@ -2758,7 +3157,7 @@ msgid "*Hint:* This error indicates that most likely, your company has not passe msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:554 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:556 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:555 msgid "Credit Notes" msgstr "" @@ -2766,6 +3165,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Creation of CAF for Credit notes." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:566 msgid "Refer to the :ref:`CAF section ` where we described the process to load the CAF on each document type." msgstr "" @@ -2783,6 +3186,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Full invoice refund with SII reference code 1." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:583 msgid "Corrects Referenced Document Text" msgstr "" @@ -2791,10 +3198,18 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Partial refund to correct text including the corrected value." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:593 msgid "Odoo creates a Credit Note with the corrected text in an invoice and price 0." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Credit note with the corrected value on the invoice lines." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:600 msgid "It's important to define the default credit account in the Sales journal as it is taken for this use case in specific." msgstr "" @@ -2807,8 +3222,12 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Credit note for partial refund to correct amounts, using the SII reference code 3." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:615 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:584 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:583 msgid "Debit Notes" msgstr "" @@ -2824,10 +3243,18 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Debit note for partial refund to crrect amounts, using the SII reference code 3." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:635 msgid "In this case Odoo automatically includes the source invoice in the cross reference section:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Invoice data on crossed reference section for debit notes." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:642 msgid "Cancel Credit Notes" msgstr "" @@ -2836,6 +3263,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Creating a debit note to cancel a credit note with the SII code reference 1." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:655 msgid "As part of the Chilean localization, you can configure your Incoming email server as the same you have register in the SII in order to:" msgstr "" @@ -2860,6 +3291,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Messages recorded in the chatter with the reception notification for the vendor." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:675 msgid "Acceptation" msgstr "" @@ -2868,6 +3303,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Acceptance button in vendor bills to inform vendor the document is comercially accepted." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:686 msgid "Claim" msgstr "" @@ -2876,6 +3315,10 @@ 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Claim button in vendor bills to inform the vendor all the document is comercially rejected." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:696 msgid "If you claim a vendor bill, the status changes from draft to cancel automatically. Considering this as best practice, all the Claim documents should be canceled as they won't be valid for your accounting records." msgstr "" @@ -2896,6 +3339,10 @@ msgstr "" msgid "The Delivery Guide module includes sending the DTE to SII and the stamp in PDF reports for deliveries." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Install Delivery Guide Module" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:718 msgid "Once all configurations have been made for electronic invoices (e.g., uploading a valid company certificate, setting up master data, etc.), Delivery Guides need their own CAFs. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the CAFs for electronic Delivery Guides." msgstr "" @@ -2928,10 +3375,18 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Create Delivery Guide Button" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:744 msgid "When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up, showing the following:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "An example sequence error when creating a Delivery Guide in Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:751 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 "" @@ -2944,6 +3399,10 @@ msgstr "" msgid "The DTE file (Electronic Tax Document) is automatically created and added to the chatter." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "DTE Status in SII and creation of DTE/XML" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:765 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:829 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." @@ -2953,6 +3412,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Printing Delivery Guide PDF" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:776 msgid "Electronic Receipt" msgstr "" @@ -2969,6 +3432,10 @@ msgstr "" msgid "This module contains the electronic receipt and daily sales report, which are automatically sent to SII." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Install Electronic Receipt module" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:793 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 "" @@ -2981,6 +3448,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Select type of Document: (39) Boleta Electrónica" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:815 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 "" @@ -2993,6 +3464,10 @@ msgstr "" msgid "The DTE file (Electronic Tax Document) is created automatically and added to the chatter." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "DTE status in SII and creation of DTE/XML" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:832 msgid "Please refer to the :ref:`DTE Workflow ` for Electronic Invoices as the workflow for Electronic Receipt follows the same process." msgstr "" @@ -3005,14 +3480,26 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Find Electronic Receipts in the Reports menu, under Daily Sales Reports" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:846 msgid "A list of daily reports is displayed with all daily DTE sent to SII." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "List of Daily Reports" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:852 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/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Daily Sales Book example" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:861 msgid "For Chilean localization, note that the feature tax included in the price is *not* supported for the Electronic Receipt." msgstr "" @@ -3034,6 +3521,10 @@ msgstr "" msgid "You can find this report in :menuselection:`Accounting --> Accounting --> Reports`" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Columns and data displayed in the report Balance Tributario 8 Columnas." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:887 msgid "Propuesta F29" msgstr "" @@ -3046,6 +3537,10 @@ msgstr "" msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the SII." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:None +msgid "Parameters to required to generate the Report Propuesta F29" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:3 msgid "Colombia" msgstr "" @@ -3067,6 +3562,7 @@ msgid "**l10n_co_edi**: This module includes all the extra fields that are requi msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:27 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:108 msgid "Workflow" msgstr "" @@ -3217,7 +3713,8 @@ msgid "**Factura de contingencia**: This is an exceptional type that is used as msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:211 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:386 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:116 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:385 msgid "Invoice validation" msgstr "" @@ -3983,6 +4480,7 @@ msgid "Egypt" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:8 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:8 msgid "Installation" msgstr "" @@ -3992,17 +4490,23 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:16 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/france.rst:182 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:16 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:14 #: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:93 msgid "Name" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:17 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:17 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:15 #: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:94 msgid "Technical name" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:18 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/france.rst:59 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:18 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:16 msgid "Description" msgstr "" @@ -4015,6 +4519,8 @@ msgid "``l10n_eg``" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:21 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:21 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:19 msgid "Default :doc:`fiscal localization package <../overview/fiscal_localization_packages>`" msgstr "" @@ -4062,10 +4568,18 @@ msgstr "" msgid "Access your company profile on the ETA portal by clicking on :guilabel:`View Taxpayer Profile`." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:None +msgid "Clicking on \"View Taxpayer Profile\" on an ETA invoicing portal" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:55 msgid "Next, go to the :guilabel:`Representatives` section and then click on :guilabel:`Register ERP`. Fill out the :guilabel:`ERP Name` (e.g., ``Odoo``) and leave the other fields empty." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:None +msgid "Filling out of the form to register an ERP system on the ETA portal." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:62 msgid "Once successfully registered, the website displays your API credentials:" msgstr "" @@ -4095,6 +4609,7 @@ msgid "These codes are confidential and should be stored safely." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:76 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:82 msgid "Configuration on Odoo" msgstr "" @@ -4102,6 +4617,10 @@ msgstr "" msgid "To connect your Odoo database to your ETA portal account, go to :menuselection:`Accounting --> Configuration --> Settings --> ETA E-Invoicing Settings`, and set the :guilabel:`ETA Client ID` and :guilabel:`ETA Secret` that you retrieved when you :ref:`registered Odoo on your ETA portal `. Set an invoicing threshold if needed." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:None +msgid "Configuration of the ETA E-Invoicing credentials in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:88 msgid "**Test on your preproduction portal** before starting to issue real invoices on the production ETA portal." msgstr "" @@ -4204,6 +4723,10 @@ msgstr "" msgid "Set the :guilabel:`ETA Branch ID` (use ``0`` if you have one branch only)." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:None +msgid "Sales journal configuration of an Egyptian company's branch" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:150 msgid "The contact selected in the :guilabel:`Branch` field must be set as a :guilabel:`Company` (**not** as an :guilabel:`Individual`), and the :guilabel:`Address` and :guilabel:`Tax ID` fields must be filled out." msgstr "" @@ -4289,6 +4812,10 @@ msgstr "" msgid "Select :guilabel:`Local Proxy Mode` as the type of install." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:None +msgid "Selection of \"Local Proxy Mode\" during the installation of Odoo Community." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:215 msgid "This installation of Odoo only works as a server and does not install any Odoo apps on your computer." msgstr "" @@ -4325,6 +4852,10 @@ msgstr "" msgid "Click on :guilabel:`Get certificate`." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:None +msgid "Creating a new thumb drive for the e-invoicing of an egyptian company." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/france.rst:3 msgid "France" msgstr "" @@ -5371,7 +5902,7 @@ msgid "Be careful, you can only change the accounting package as long as you hav msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:16 -msgid "When you create a new SaaS database, the SKR03 is installed by default." +msgid "When you create a new Odoo Online database, the SKR03 is installed by default." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:19 @@ -5391,7 +5922,6 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:24 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/netherlands.rst:19 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:17 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:91 msgid "Profit & Loss" msgstr "" @@ -5448,6 +5978,10 @@ msgstr "" msgid "If these modules are not listed, :ref:`update the app list `." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:None +msgid "Upgrading Odoo Point of Sale from the Apps dashboard" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:77 msgid "Register your company at the financial authority" msgstr "" @@ -5480,6 +6014,10 @@ 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/accounting/fiscal_localizations/localizations/germany.rst:None +msgid "Button to register a company through fiskaly in Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:98 msgid "If you do not see the *fiskaly Registration* button, make sure that you *saved* your company details and are not in *editing mode* anymore." msgstr "" @@ -5496,6 +6034,10 @@ msgstr "" msgid "**fiskaly API key** and **secret** are the credentials the system uses to access the services offered by fiskaly." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:None +msgid "fiskaly keys as displayed on Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:112 msgid "It is possible to request new credentials if there is any issue with the current ones." msgstr "" @@ -5504,6 +6046,10 @@ msgstr "" msgid "Create and link a Technical Security System to your PoS" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:None +msgid "Create TSS option from a point of sale" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:121 msgid "To use your point of sale in Germany, you first have to create a :abbr:`TSS (Technical Security System)` for it." msgstr "" @@ -5512,6 +6058,10 @@ 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/accounting/fiscal_localizations/localizations/germany.rst:None +msgid "Example of TSS ID and Client ID from fiskaly in Odoo Point of Sale" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:131 msgid "Once the creation of the TSS is successful, you can find your **TSS ID** and **Client ID** under the *fiskaly API* section." msgstr "" @@ -5528,6 +6078,10 @@ msgstr "" msgid "DSFinV-K" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:None +msgid "Menu to export DSFinV-K" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:144 msgid "Whenever you close a PoS session, the orders' details are sent to the :abbr:`DSFinV-K (Digitale Schnittstelle der Finanzverwaltung für Kassensysteme)` service of fiskaly." msgstr "" @@ -5560,6 +6114,10 @@ msgstr "" msgid "The creation of a DSFinV-K export triggers on export at fiskaly's side." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:None +msgid "Pending DSFinV-K export on Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:165 msgid "As you can see, the **State** is *Pending*. This means that the export has been successfully triggered and is being processed. You have to click on *Refresh State* to check if it is ready." msgstr "" @@ -5637,7 +6195,7 @@ msgid "Once bookings have been finally posted, they can no longer be changed or msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:227 -msgid "If Odoo is used in the cloud, regular backups are part of the SaaS service. In addition, regular backups can be downloaded and backed up on external systems." +msgid "If Odoo is used in the cloud, regular backups are part of the Odoo Online service. In addition, regular backups can be downloaded and backed up on external systems." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:231 @@ -5764,6 +6322,199 @@ msgstr "" msgid "In the event of an infringement, you can expect a fine but also a court order demanding the implementation of specific measures." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:3 +msgid "India" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:10 +msgid ":ref:`Install ` the following modules to get all the features of the Indian localization:" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:19 +msgid ":guilabel:`Indian - Accounting`" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:20 +msgid "`l10n_in`" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:22 +msgid ":guilabel:`Indian E-invoice Integration`" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:23 +msgid "`l10n_in_edi`" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:24 +msgid ":ref:`Indian e-invoicing integration `" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:29 +msgid "Indian e-invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:31 +msgid "Odoo is compliant with the **Indian Good and Services Tax (GST) e-Invoice system** requirements." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:34 +msgid "Indian e-invoicing is available from Odoo 15.0. If needed, :doc:`upgrade ` your database." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:40 +msgid "Registration on your NIC e-Invoice web portal" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:42 +msgid "You must register on the **NIC e-Invoice** web portal to get your **API credentials**. You need these credentials to :ref:`configure your Odoo Accounting app `." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:45 +msgid "Login to the NIC e-Invoice web portal on - https://einvoice1.gst.gov.in/ by clicking on :guilabel:`Login` and entering your :guilabel:`Username` and :guilabel:`Password`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:49 +msgid "If you have already registered on the NIC Eway Bill Production portal, then you can use the same login credentials here." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:0 +msgid "Register Odoo ERP system on e-invoice web portal" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:56 +msgid "From your dashboard, go to :menuselection:`API Registration --> User Credentials --> Create API User`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:0 +msgid "Click on User Credentials and Create API User" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:63 +msgid "After that, you receive an :abbr:`OTP (one-time password)` code to your registered mobile number." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:64 +msgid "Enter the OTP code and click on :guilabel:`Verify OTP`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:0 +msgid "Trigger an OTP to your registerd phone number" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:70 +msgid "Select :guilabel:`Through GSP` in the first field, select :guilabel:`Tera Software Limited` as your GSP, and type in a :guilabel:`Username` and :guilabel:`Password` for your API." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:0 +msgid "Submit API specific Username and Password" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:77 +msgid "Click on :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:84 +msgid "To set up the e-invoice service, go to :menuselection:`Accounting --> Configuration --> Settings --> Indian Electronic Invoicing`, and enter the :guilabel:`Username` and :guilabel:`Password`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:None +msgid "Setup e-invoice service" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:96 +msgid "Your default *sales* journal should be already configured correctly. You can check it or configure other journals by going to :menuselection:`Accounting --> Configuration --> Journals`. Then, open your *sales* journal, and in the :guilabel:`Advanced Settings` tab, under :guilabel:`Electronic Data Interchange`, check :guilabel:`E-Invoice (IN)` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:None +msgid "Journal configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:110 +msgid "To start invoicing from Odoo, an invoice must be created using the standard invoicing flow, that is, either from a sales order or the invoice menu in the Accounting application." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:118 +msgid "Once the invoice is validated, a confirmation message is displayed at the top." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:120 +msgid "Odoo automatically uploads the JSON-signed file to the government portal after a while. If you want to process the invoice immediately, you can click on :guilabel:`Process Now`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:None +msgid "Indian e-invoicing confirmation message: \"The invoice will be processed asynchronously by\n" +"the following E-invoicing service : E-Invoice (IN)\"" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:129 +msgid "You can find the JSON-signed file in the attached files, in the chatter." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:130 +msgid "You can check the status of EDI with web-service under the :guilabel:`EDI Document` tab or the :guilabel:`Electronic invoicing` field." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:138 +msgid "Once the invoice is submitted and validated, you can print the invoice PDF report. The report includes the :abbr:`IRN (Invoice Reference Number)`, acknowledgment number and date, and QR code. They certify that the invoice is a valid fiscal document." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:None +msgid "IRN and QR code" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:149 +msgid "EDI Cancellation" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:151 +msgid "If you want to cancel an e-invoice, go to the :guilabel:`Other info` tab of the invoice and fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then, click on :guilabel:`Request EDI cancellation`. The status of the :guilabel:`Electronic invoicing` field changes to :guilabel:`To Cancel`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:None +msgid "cancel reason and remarks" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:161 +msgid "If you want to abort the cancellation before processing the invoice, then click on :guilabel:`Call Off EDI Cancellation`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:164 +msgid "Once you request to cancel the e-invoice, Odoo automatically submits the JSON Signed file to the government portal. If you want to process the invoice immediately, you can process it by clicking on :guilabel:`Process Now`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:171 +msgid "Verify the e-invoice from the GST" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:173 +msgid "After submitting an e-invoice, you can also verify the signed invoice from the GST e-Invoice system website." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:176 +msgid "Download the JSON file from the attached files." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:177 +msgid "Open the e-invoice portal: https://einvoice1.gst.gov.in/ and go to :menuselection:`Search --> Verify Signed Invoice`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:179 +msgid "Select the JSON file and submit it." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:0 +msgid "select the JSON file for verify invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:185 +msgid "You can check the verified signed e-invoice here." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/india.rst:0 +msgid "verified e-invoice" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/indonesia.rst:3 msgid "Indonesia" msgstr "" @@ -5932,6 +6683,10 @@ msgstr "" msgid "To do this, go to :menuselection:`Accounting --> Settings --> Electronic Invoicing` and click on *Register*." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:None +msgid "Register button to allow Odoo to process invoices." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:48 msgid "All your files are encrypted upon reception in such a way that only you are able to decrypt them." msgstr "" @@ -5944,6 +6699,10 @@ msgstr "" msgid "Open your sales journal. Under the *Advanced Settings* tab, in the **Electronic invoicing** field, check *FatturaPA* and *Save*." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:None +msgid "FatturaPA feature in the sales journal's settings" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:61 msgid "Issue invoices" msgstr "" @@ -5952,10 +6711,18 @@ msgstr "" msgid "Send an invoice the way you would do it normally. The EDI process proceeds automatically." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:None +msgid "Asynchronous sending on a customer invoice" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:69 msgid "You can check the current status of your customer invoice under the **Electronic invoicing** field." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:None +msgid "Electronic invoicing status (waiting for confirmation)" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:77 msgid "Receive invoices" msgstr "" @@ -6088,100 +6855,129 @@ msgstr "" msgid ":ref:`Install ` the following modules to get all the features of the Luxembourgish localization:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:11 -msgid ":guilabel:`Luxembourg - Accounting` (module's technical name: ``l10n_lu``)." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:17 +msgid ":guilabel:`Luxembourg - Accounting`" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:12 -msgid ":guilabel:`Luxembourg - Accounting Reports` (module's technical name: ``l10n_lu_reports``)." -msgstr "" - -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:13 -msgid ":guilabel:`Luxembourg - Annual VAT Report` (module's technical name: ``l10n_lu_reports_annual_vat``)." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:18 +msgid "`l10n_lu`" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:20 -msgid "Installing the module :guilabel:`Luxembourg - Accounting Reports` installs all three modules at once." +msgid ":guilabel:`Luxembourg - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:21 +msgid "`l10n_lu_reports`" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:22 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:25 +msgid "Country-specific reports" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:23 +msgid ":guilabel:`Luxembourg - Annual VAT Report`" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:24 -msgid "Standard Chart of Accounts - PCN 2020" +msgid "`l10n_lu_reports_annual_vat`" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:26 -msgid "Odoo's :doc:`Fiscal Localization Package <../overview/fiscal_localization_packages>` for Luxembourg includes the current **Standard Chart of Accounts (PCN 2020)**, effective since January 2020." -msgstr "" - -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:30 -msgid "eCDF tax return" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:None +msgid "The three modules for the Luxembourgish Fiscal Localization Package on Odoo" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:32 -msgid "Tax returns in Luxembourg require a specific XML file to upload on the eCDF." +msgid "Installing the module :guilabel:`Luxembourg - Accounting Reports` installs all three modules at once." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:34 -msgid "To download it, go to :menuselection:`Accounting --> Report --> Audit Reports --> Tax Report`, and click on :guilabel:`Export eCDF declaration`." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:36 +msgid "Standard Chart of Accounts - PCN 2020" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:38 +msgid "Odoo's :doc:`Fiscal Localization Package <../overview/fiscal_localization_packages>` for Luxembourg includes the current **Standard Chart of Accounts (PCN 2020)**, effective since January 2020." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:42 +msgid "eCDF tax return" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:44 +msgid "Tax returns in Luxembourg require a specific XML file to upload on the eCDF." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:46 +msgid "To download it, go to :menuselection:`Accounting --> Report --> Audit Reports --> Tax Report`, and click on :guilabel:`Export eCDF declaration`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:50 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:282 msgid ":doc:`../../reporting/declarations/tax_returns`" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:39 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:51 msgid "`Platform for electronic gathering of financial data (eCDF) `_" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:42 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:54 msgid "Annual tax report" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:44 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:56 msgid "You can generate an XML file to electronically file your annual tax report with the tax office." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:46 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:58 msgid "To do so, go to :menuselection:`Accounting --> Report --> Luxembourg --> Annual Tax Report`, click on :guilabel:`Create`, then define the annual period in the :guilabel:`Year` field." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:49 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:61 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/accounting/fiscal_localizations/localizations/luxembourg.rst:56 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:None +msgid "Odoo Accounting (Luxembourg localization) generates an annual tax declaration." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:68 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/accounting/fiscal_localizations/localizations/luxembourg.rst:64 -msgid "Finally, click on :guilabel:`Export XML` to download the XML file." -msgstr "" - -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:67 -msgid "This feature requires the module :guilabel:`Luxembourg - Annual VAT Report` to be installed." -msgstr "" - -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:70 -msgid "FAIA (SAF-T)" -msgstr "" - -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:72 -msgid "**FAIA (Fichier d’Audit Informatisé AED)** is a standardized and structured file that facilitates the exchange of information between the taxpayers' accounting system and the tax office. It is the Luxembourgish version of the OECD-recommended SAF-T (Standard Audit File for Tax)." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:None +msgid "Dropdown menu to select the type of Tax Report" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:76 +msgid "Finally, click on :guilabel:`Export XML` to download the XML file." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:79 +msgid "This feature requires the module :guilabel:`Luxembourg - Annual VAT Report` to be installed." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:82 +msgid "FAIA (SAF-T)" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:84 +msgid "**FAIA (Fichier d’Audit Informatisé AED)** is a standardized and structured file that facilitates the exchange of information between the taxpayers' accounting system and the tax office. It is the Luxembourgish version of the OECD-recommended SAF-T (Standard Audit File for Tax)." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:88 msgid "Odoo can generate an XML file that contains all the content of an accounting period according to the rules imposed by the Luxembourg tax authorities on digital audit files." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:80 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:92 msgid "This feature requires the module :guilabel:`Luxembourg - Accounting Reports` to be installed." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:83 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:95 msgid "Export FAIA file" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:85 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst:97 msgid "Go to :menuselection:`Accounting --> Reporting --> Audit Reports --> General Ledger`, then click on :guilabel:`FAIA`." msgstr "" @@ -6218,7 +7014,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/accounting/fiscal_localizations/localizations/mexico.rst:37 @@ -6233,6 +7029,10 @@ 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Installation of the Mexican localization module in Odoo Apps" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:51 msgid "If you created the database from `www.odoo.com `_ and chose \"Mexico\" as the country when creating your account, some of the Mexican localization modules will have been installed automatically. In that case we observe that some modules have a button that says \"Install\", while others will instead have a label that says \"Installed\"." msgstr "" @@ -6293,6 +7093,10 @@ 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Steps to enable electronic invoicing" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:95 msgid "Enter legal information" msgstr "" @@ -6301,6 +7105,10 @@ 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Update the company's details in the Settings of Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:105 msgid "In the resulting form, put your full address (including zip code), RFC (VAT number), and the rest of the data." msgstr "" @@ -6313,6 +7121,10 @@ msgstr "" msgid "Make sure that in the address, for the Country field, \"Mexico\" is chosen from the list of countries that Odoo shows, because if it is entered manually there is a risk of creating a \"new country\" in the system, which it will result in errors later when the CFDIs are generated." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "Company data information" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:124 msgid "If you want to test the Mexican localization, you can configure the company with a real address within Mexico (including all fields) and add ``EKU9003173C9`` as RFC." msgstr "" @@ -6329,6 +7141,10 @@ 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Set the Fiscal Regime in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:141 msgid "For the test environment: Select the option **General Law on Legal Persons** from the drop-down menu." msgstr "" @@ -6341,6 +7157,10 @@ 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Contact form example" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:156 msgid "Taxes Configuration" msgstr "" @@ -6357,6 +7177,10 @@ msgstr "" msgid "Within the list of taxes that are pre-loaded, select the option *Sales* on the filter, this is to see only taxes associated with sales, which are those that are validated for the stamping of invoices. Open the form view of any of the sales taxes, select the **Advanced Options** tab and within the field **Factor Type** choose the option *Tasa*." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Taxes configuration" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:173 msgid "Do the same for all the sales taxes that the company needs, either those that come by default in Odoo, or those that you add that are necessary for your company bill." msgstr "" @@ -6369,6 +7193,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Taxes accounts" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:190 msgid "Products Configuration" msgstr "" @@ -6381,6 +7209,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Configure products" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:204 msgid "PAC Configuration to sign invoices" msgstr "" @@ -6401,6 +7233,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PAC credentials" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:229 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 "" @@ -6409,6 +7245,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Certificate and key" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:241 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 "" @@ -6449,6 +7289,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Creating an invoice" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:272 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 "" @@ -6549,10 +7393,18 @@ msgstr "" msgid "EDI for Mexico (l10n_mx_edi)" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "EDI para México" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:342 msgid "EDI for Mexico (l10n_mx_edi_extended)" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "EDI Advanced Features" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:349 msgid "Company" msgstr "" @@ -6561,6 +7413,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Contact address configuration" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:360 msgid "Receiving Client" msgstr "" @@ -6569,6 +7425,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "External trade invoice" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:370 msgid "The customer's delivery address must also contain the zip code." msgstr "" @@ -6585,6 +7445,14 @@ msgstr "" msgid "At the product level there must also configure some parameters in the following fields." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "SAT product code" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Tariff fraction" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:390 msgid "You must select the **UMT Aduana** (Unit of Measure) in *KG* since it is only accepted by the SAT" msgstr "" @@ -6617,6 +7485,14 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Incoterm on invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PDF external Trade" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:421 msgid "Assign Pedimentos" msgstr "" @@ -6629,6 +7505,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "MX stock module" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:435 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 "" @@ -6637,6 +7517,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Costos en destino" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:448 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 "" @@ -6645,6 +7529,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Customs number" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:461 msgid "You can only add the Pedimentos number once, so be careful when associating the correct number with the transfer(s)." msgstr "" @@ -6661,6 +7549,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Payment terms" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:478 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 "" @@ -6693,10 +7585,18 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Payment policy" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:514 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Contact bank account" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:522 msgid "Register PPD Payments" msgstr "" @@ -6710,6 +7610,14 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PPD payments" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PPD payment information" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:539 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 "" @@ -6722,6 +7630,10 @@ msgstr "" msgid ":doc:`../../bank/reconciliation/use_cases`." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PPD payment created" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:554 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 "" @@ -6742,6 +7654,18 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PUE payments" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PUE payment information" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PUE payment created" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:588 msgid "In this case it is not created as a payment supplement by the nature of it." msgstr "" @@ -6802,10 +7726,18 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Down payment product" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:627 msgid "Add the down payment product as default to be used from the Odoo configurations." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Down payment configuration" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:634 msgid "Issuance of the electronic invoice for the value of the advance received" msgstr "" @@ -6814,14 +7746,34 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Applying down payment" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:643 msgid "Validate invoice with the down payment product." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Confirm down payment" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Folio fiscal down payment" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:653 msgid "Register Payment to the advance payment invoice." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Down payment invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Down payment registered" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:664 msgid "Issuance of the electronic invoice for the total value of the operation." msgstr "" @@ -6830,6 +7782,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Full invoice" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:674 msgid "Remove the check mark from the **Deduct down payments** field." msgstr "" @@ -6842,10 +7798,18 @@ msgstr "" msgid "Copy the Folio Fiscal of the following invoice following this example:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Folio full invoice" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:685 msgid "And paste it in the draft invoice created from the Sales Order without deducting the advances:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "CFDI origen folio" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:691 msgid "Validate and copy the Folio Fiscal for later (in the example the Folio Fiscal copy is: 50E4FF06-4341-4006-A7C3-A7F653CBEFAE )" msgstr "" @@ -6858,26 +7822,62 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Creation of a Credit Note" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Matching down payment" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:708 msgid "Before you *Confirm* the Credit Note, edit the Origin CFDI with ``07 | XXX`` instead of the prefix ``01 | XXX``" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Modify folio fiscal" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "CFDI origen type" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:719 msgid "Now the invoice can be confirmed." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Post credit note" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:725 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Add credit note" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Down payment applied" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:736 msgid "Register a payment for the difference of the down payment and the total of the sale." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Residual amount payment" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:742 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "XML down payment" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:750 msgid "Discounts based on payment days" msgstr "" @@ -6905,30 +7905,70 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Discount payment term" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:774 msgid "Then when creating our Sales Order or Sales Invoice, assign the Payment Term created previously." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "discount on invoice" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:783 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Discount payment" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:790 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "See discount payment" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Mote to draft payment" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Cancel payment" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:809 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Discount credit note" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Reason of credit note" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:821 msgid "Adjust the amount to the remaining balance in the original invoice." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Total credit note" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:827 msgid "Add the Credit Note to the original invoice so that it is settled." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Add credit note for discount" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:834 msgid "Cancellation of invoices" msgstr "" @@ -6945,6 +7985,10 @@ msgstr "" msgid "Request Cancellation" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "Cancel within 72 hours" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:848 msgid "The status of the **Electronic invoicing** changes to *Cancelled*" msgstr "" @@ -6953,10 +7997,18 @@ msgstr "" msgid "Click on *RESET TO DRAFT*" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "Invoice to draft" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:855 msgid "Click on *CANCEL ENTRY*" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "Cancel journal entry" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:862 msgid "After 72 Hours" msgstr "" @@ -6977,10 +8029,18 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Cancel after 72 hours" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:879 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Check estado del PAC" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:887 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 "" @@ -6989,6 +8049,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "PAC scheduled action" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:899 msgid "Cancel Paid Invoices" msgstr "" @@ -6997,6 +8061,14 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Cancel paid invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Credit note to cancel" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:913 msgid "Cancel Invoices from the previous period" msgstr "" @@ -7017,14 +8089,26 @@ msgstr "" msgid "Invoice to be canceled" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Previous period" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:932 msgid "This is how the Balance Sheet looks like:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Previous BS" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:938 msgid "If the invoice is canceled, the journal entry and the Balance Sheet looks like this after canceling:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "AR in BS" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:945 msgid "Solution" msgstr "" @@ -7057,6 +8141,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Closing fiscal period" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:964 msgid "Cancel invoice in the SAT" msgstr "" @@ -7065,6 +8153,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Cancel in SAT" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:975 msgid "Create Manual Reversal Journal Entry" msgstr "" @@ -7077,14 +8169,38 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Manual reversal" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:988 msgid "Reconcile the open invoice with the reversal entry" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Reconcile open invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Open invoice paid" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:998 msgid "In the Balance Sheet and Trial balance they are now with the correct balances." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "New BS" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Up to date BS" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Balanza de comprobación" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1013 msgid "Change status of Electronic invoicing to Cancelled with server action" msgstr "" @@ -7093,6 +8209,14 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Scheduled action PAC status" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Execute server action" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1028 msgid "Electronic Accounting" msgstr "" @@ -7122,10 +8246,18 @@ msgstr "" msgid "You can find all of those reports in :menuselection:`Accounting --> Reporting --> Mexico`" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "MX reports" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1048 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "COA for SAT" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1056 msgid "How to add new accounts ?" msgstr "" @@ -7138,6 +8270,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Create account" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1072 msgid "What is the meaning of the tags?" msgstr "" @@ -7158,6 +8294,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Electronic verification balance" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1096 msgid "All normal analysis and listed functions are available here as well as any normal Odoo Report." msgstr "" @@ -7238,14 +8378,26 @@ msgstr "" msgid "Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third partied (DIOT)`." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "DIOT report" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1169 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 "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "DIOT filter" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1176 msgid "Click on *Export (XLSX)* or *Print (TXT)*" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Print DIOT" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1182 msgid "Save the downloaded file in a safe place, go to the SAT website and follow the necessary steps to declare it." msgstr "" @@ -7258,6 +8410,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "DIOT configuration" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1197 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 "" @@ -7278,6 +8434,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "DIOT Error" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1216 msgid "Closing Fiscal Period in Odoo" msgstr "" @@ -7369,6 +8529,11 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +#: ../../content/applications/finance/accounting/taxation/fiscal_year.rst:5 +msgid "Fiscal year" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1270 msgid "Accounting Closing Process" msgstr "" @@ -7385,6 +8550,10 @@ msgstr "" 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Balance sheet closing" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1289 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 "" @@ -7397,10 +8566,18 @@ msgstr "" msgid "The simplified accounting entry would look like this:" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Closing journal entry" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1303 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/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Check BS closing" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1313 msgid "Extra Recommended features" msgstr "" @@ -7425,6 +8602,10 @@ msgstr "" msgid "Go to settings and enable the multi-currency feature." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Multi currency configuration" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1336 msgid "Enabling Explicit errors on the CFDI using the XSD local validator (CFDI 3.3)" msgstr "" @@ -7457,6 +8638,10 @@ msgstr "" msgid "Click on \"Action\" and then on \"Download XSD file to CFDI\"." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Download XSD files to CFDI from the Companies list view on Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1354 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 "" @@ -7529,6 +8714,10 @@ msgstr "" 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 "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "Fiscal position error" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1414 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 "" @@ -7546,6 +8735,10 @@ msgstr "" msgid "**Solution**: The payment method is required on your invoice." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "Payment method error" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1434 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 "" @@ -7567,6 +8760,10 @@ msgstr "" msgid "**Solution**: The postal code of your company address is not valid for Mexico, please correct it." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:None +msgid "ZIP code error" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:1465 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 "" @@ -7579,6 +8776,14 @@ msgstr "" 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 "" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "Factor type error" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 +msgid "Rate error" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst:0 msgid "``CCE159``" msgstr "" @@ -7687,6 +8892,10 @@ 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/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "The \"Module\" filter is set on \"Peru\"" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:39 msgid "When you install a database from scratch selecting Peru as country, Odoo automatically installs the base module: Peru - Accounting." msgstr "" @@ -7695,6 +8904,10 @@ 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/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Company data for Peru including RUC and Address type code" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:56 msgid "In case the Address type code is unknown, you can set it as the default value: 0000. Be aware that if an incorrect value is entered, the Electronic invoice validation might have errors." msgstr "" @@ -7766,6 +8979,7 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:106 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:170 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None msgid "Digiflow" msgstr "" @@ -7782,6 +8996,10 @@ 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/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "IAP option as signature providers" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:122 msgid "What is the IAP?" msgstr "" @@ -7924,289 +9142,389 @@ 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/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "EDI Certificate wizard" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:228 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/accounting/fiscal_localizations/localizations/peru.rst:235 -msgid "Please refer to the next section in our documentation for more information about :doc:`multicurrency <../../others/multicurrencies/how_it_works>`." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Bank of Peru is displayed in Multicurrency Service option" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:245 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:235 +msgid "Please refer to the next section in our documentation for more information about :doc:`multicurrencies <../../others/multi_currency>`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:244 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/accounting/fiscal_localizations/localizations/peru.rst:253 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "List of default taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:252 msgid "EDI Configuration" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:255 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:254 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/accounting/fiscal_localizations/localizations/peru.rst:267 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Taxes EDI data for Peru" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:266 msgid "There are two main fiscal positions included by default when you install the Peruvian localization." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:269 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:268 msgid "**Extranjero - Exportación**: Set this fiscal position on customers for Exportation transactions." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:271 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:270 msgid "**Local Peru**: Set this fiscal position on local customers." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:276 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:275 msgid "In some Latin American countries, including Peru, some accounting transactions like invoices and vendor bills are classified by document types, defined by the government fiscal authorities, in this case by the SUNAT." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:280 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:279 msgid "Each document type can have a unique sequence per journal where it is assigned. As part of the localization, the Document Type includes the country on which the document is applicable;the data is created automatically when the localization module is installed." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:284 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:283 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/accounting/fiscal_localizations/localizations/peru.rst:292 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Document Type list" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:291 msgid "Currently the documents supported on customer invoices are: Invoice, Boleta, Debit Note and Credit Note." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:298 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:297 msgid "When creating Sales Journals, the following information must be filled, in addition to the standard fields on the Journals:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:302 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:301 msgid "Use Documents" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:304 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:303 msgid "This field is used to define if the journal uses Document Types. It is only applicable to Purchase and Sales journals, which are the ones that can be related to the different set of document types available in Peru. By default, all the sales journals created use documents." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:309 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:308 msgid "Electronic Data Interchange" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:311 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:310 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/accounting/fiscal_localizations/localizations/peru.rst:319 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Journal EDI field" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:318 msgid "By default, the value Factur-X (FR) is always displayed, make sure you can uncheck it manually." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:327 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:326 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/accounting/fiscal_localizations/localizations/peru.rst:337 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Partner identification type" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:336 msgid "Product" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:339 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:338 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/accounting/fiscal_localizations/localizations/peru.rst:351 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "UNSPC Code on products" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:350 msgid "Customer invoice" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:354 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:353 msgid "EDI Elements" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:356 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:355 msgid "Once you have configured your master data, the invoices can be created from your sales order or manually. Additional to the basic invoice information described on :doc:`our page about the invoicing process <../../receivables/customer_invoices/overview>`, there are a couple of fields required as part of the Peru EDI:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:361 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:360 msgid "**Document type**: The default value is “Factura Electronica” but you can manually change the document type if needed and select Boleta for example." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:368 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:0 +msgid "Invoice document type field on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:367 msgid "**Operation type**: This value is required for Electronic Invoice and indicates the transaction type, the default value is “Internal Sale” but another value can be selected manually when needed, for example Export of Goods." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:376 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:0 +msgid "Invoice operation type field on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:375 msgid "**EDI Affectation Reason**: In the invoice lines, additional to the Tax there is a field “EDI Affectation Reason” that determines the tax scope based on the SUNAT list that is displayed. All the taxes loaded by default are associated with a default EDI affection reason, if needed you can manually select another one when creating the invoice." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:388 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:0 +msgid "Tax affectation reason in invoice line" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:387 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/accounting/fiscal_localizations/localizations/peru.rst:396 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Sending of EDI Invoice in blue" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:395 msgid "Asynchronous means that the document is not sent automatically after the invoice has been posted." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:399 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:493 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:398 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:492 msgid "Electronic Invoice Status" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:401 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:400 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/accounting/fiscal_localizations/localizations/peru.rst:409 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Send EDI manually" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:408 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/accounting/fiscal_localizations/localizations/peru.rst:417 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Message on chatter when the invoice is valid" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:416 msgid "In case there is a validation error the Electronic Invoice status remains in “To be sent” so the corrections can be made and the invoice can be sent again." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:421 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:420 msgid "One credit is consumed each time that you send a document for validation, in this sense if an error is detected on an invoice and you send it one more time, two credits are consumed in total." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:428 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:427 msgid "There are multiple reasons behind a rejection from the OSE or the SUNAT, when this happens Odoo sends a message at the top of the invoice indicating the error details and in the most common cases a hint to fix the issue." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:432 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:431 msgid "If a validation error is received, you have two options:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:434 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:433 msgid "In case the error is related to master data on the partner, customer or taxes, you can simply apply the change on the record (example customer identification type) and once it is done click on the Retry button." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:437 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:436 msgid "If the error is related to some data recorded on the invoice directly (Operation type, missing data on the invoice lines), the correct solution is to reset the invoice to Draft, apply the changes, and then send the invoice again to the SUNAT for another validation." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:446 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:0 +msgid "List of common errors on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:445 msgid "For more detail please refert to `Common errors in SUNAT `_." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:452 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:451 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/accounting/fiscal_localizations/localizations/peru.rst:460 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Invoice PDF report" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:459 msgid "IAP Credits" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:462 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:461 msgid "Odoo’s Electronic IAP offers 1000 credits for free, after these credits are consumed in your production database, your company must buy new credits in order to process your transactions." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:465 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:464 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/accounting/fiscal_localizations/localizations/peru.rst:473 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Buying credits in the IAP" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:472 msgid "In the IAP service includes packages with different pricing based on the number of credits. The price list in the IAP is always displayed in EUR." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:480 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:516 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:479 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:515 msgid "Cancellation process" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:482 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:481 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/accounting/fiscal_localizations/localizations/peru.rst:490 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Request invoice cancellation button" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:489 msgid "In order to cancel an invoice, please provide a cancellation Reason." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:495 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:494 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/accounting/fiscal_localizations/localizations/peru.rst:504 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Cancellation CDR sent by the SUNAT" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:503 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/accounting/fiscal_localizations/localizations/peru.rst:513 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "nvoice after cancellation" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:512 msgid "One credit is consumed on each cancellation request." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:518 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:517 msgid "When creating exportation invoices, take into account the next considerations:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:520 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:519 msgid "The Identification type on your customer must be Foreign ID." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:521 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:520 msgid "Operation type in your invoice must be an Exportation one." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:522 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:521 msgid "The taxes included in the invoice lines should be EXP taxes." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:529 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Exportation invoices main data" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:528 msgid "Advance Payments" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:531 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:530 msgid "Create the advance payment Invoice and apply its related payment." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:532 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:531 msgid "Create the final invoice without considering the advance payment." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:533 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:532 msgid "Create a credit note for the Final invoice with the advance payment amount." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:534 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:533 msgid "Reconcile the Credit note with the final invoice." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:535 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:534 msgid "The remaining balance on the final invoice should be paid with a regular payment transaction." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:539 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:538 msgid "Detraction Invoices" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:541 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:540 msgid "When creating invoices that is subject to Detractions, take into account the next considerations:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:543 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:542 msgid "All the products included in the invoice must have these fields configured:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:549 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:0 +msgid "Detraction fields on products" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:548 msgid "Operation type in your invoice must be ``1001``" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:558 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:0 +msgid "Detraction code on invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:557 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/accounting/fiscal_localizations/localizations/peru.rst:567 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Add Credit Note from invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:566 msgid "When creating your first credit Note, select the Credit Method: Partial Refund, this allows you to define the credit note sequence." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:570 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:569 msgid "By default the Credit Note is set in the document type:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:576 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:None +msgid "Credit Note document type" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:575 msgid "To finish the workflow please follow the instructions on :doc:`our page about Credit Notes <../../receivables/customer_invoices/credit_notes>`." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:580 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:579 msgid "The EDI workflow for the Credit notes works in the same way as the invoices." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:586 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:585 msgid "As part of the Peruvian localization, besides creating credit notes from an existing document you can also create debit Notes. For this just use the button “Add Debit Note”." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:589 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:588 msgid "By default the Debit Note is set in the document type." msgstr "" @@ -8239,7 +9557,7 @@ msgid "You can choose the one you want by going in :menuselection:`Accounting -- msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/spain.rst:20 -msgid "When you create a new SaaS database, the PGCE PYMEs 2008 is installed by default." +msgid "When you create a new Odoo Online database, the PGCE PYMEs 2008 is installed by default." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/spain.rst:23 @@ -8298,6 +9616,10 @@ 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/accounting/fiscal_localizations/localizations/switzerland.rst:None +msgid "Configure your Journal to display your ISR as payment reference on your invoices in Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/switzerland.rst:53 msgid "Currency Rate Live Update" msgstr "" @@ -8315,7 +9637,7 @@ msgid "Starting from the 1st January 2018, new reduced VAT rates will be applied msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/switzerland.rst:71 -msgid "How to update your taxes in Odoo Enterprise (SaaS or On Premise)?" +msgid "How to update your taxes in Odoo Enterprise (Odoo Online or On-premise)?" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/switzerland.rst:73 @@ -8568,6 +9890,10 @@ msgstr "" msgid "Once done, select your country's package, and click on *Save*." msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:None +msgid "Select your country's fiscal localization package in Odoo Accounting." +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:34 msgid "These packages require you to fine-tune your chart of accounts according to your needs, activate the taxes you use, and configure your country-specific statements and certifications." msgstr "" @@ -8587,6 +9913,12 @@ msgstr "" msgid ":doc:`../../getting_started/initial_configuration/chart_of_accounts`" msgstr "" +#: ../../content/applications/finance/accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:44 +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:72 +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:16 +msgid "Todo" +msgstr "" + #: ../../content/applications/finance/accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:44 msgid "update list of linked docs, and link with the future one about country-specific statements." msgstr "" @@ -8891,14 +10223,8 @@ msgstr "" msgid "Initial configuration" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:3 -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:100 -#: ../../content/applications/finance/accounting/getting_started/memento.rst:69 -msgid "Chart of Accounts" -msgstr "" - #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:5 -msgid "The **Chart of Accounts (COA)** is the list of all the accounts used to record financial transactions in the general ledger of an organization." +msgid "The **chart of accounts (COA)** is the list of all the accounts used to record financial transactions in the general ledger of an organization." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:8 @@ -8906,7 +10232,7 @@ msgid "The accounts are usually listed in the order of appearance in the financi msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:11 -msgid "Balance Sheet accounts" +msgid "Balance Sheet accounts:" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:13 @@ -8925,6 +10251,10 @@ msgstr "" msgid "Equity" msgstr "" +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:17 +msgid "Profit & Loss:" +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:91 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:91 @@ -8938,35 +10268,39 @@ msgid "Expense" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:22 -msgid "When browsing your Chart of Accounts, you can filter the accounts by number, in the left column, and also group them by Account Type." +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 +msgid "Group the accounts by type in Odoo Accounting" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:30 -msgid "Configuration of an Account" +msgid "Configuration of an account" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:32 -msgid "The country you select at the creation of your database (or additional company on your database) determines which **Fiscal Localization Package** is installed by default. This package includes a standard Chart of Accounts already configured according to the country's regulations. You can use it directly or set it according to your company's needs." +msgid "The country you select at the creation of your database (or additional company on your database) determines which **fiscal localization package** is installed by default. This package includes a standard chart of accounts already configured according to the country's regulations. You can use it directly or set it according to your company's needs." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:38 -msgid "It is not possible to modify the **Fiscal Localization** of a company once a Journal Entry has been posted." +msgid "It is not possible to modify the **fiscal localization** of a company once a journal entry has been posted." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:41 -msgid "To create a new account, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click on *Create*, and fill out the form." +msgid "To create a new account, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click on :guilabel:`Create`, and fill out the form." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:45 -msgid "Code and Name" +msgid "Code and name" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:47 -msgid "Each account is identified by its **Code** and **Name**, which also indicates the account's purpose." +msgid "Each account is identified by its **code** and **name**, which also indicates the account's purpose." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:54 -msgid "Configuring correctly the **Account Type** is critical as it serves multiple purposes:" +msgid "Correctly configuring the **account type** is critical as it serves multiple purposes:" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:56 @@ -8986,7 +10320,7 @@ msgid "Generate opening entries" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:61 -msgid "To configure an account type, open the **Type** field's drop-down selector and select the right type among the following list:" +msgid "To configure an account type, open the :guilabel:`Type` field's drop-down selector and select the right type among the following list:" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:65 @@ -9067,109 +10401,119 @@ msgid "Off-Balance Sheet" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:105 -msgid "Assets, Deferred Expenses, and Deferred Revenues Automation" +msgid "Assets, deferred expenses, and deferred revenues automation" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:107 -msgid "Some Account Types display a new field **to automate** the creation of :ref:`Assets ` entries, :ref:`Deferred Expenses ` entries, and :ref:`Deferred Revenues ` entries." +msgid "Some **account types** display a new field **to automate** the creation of :ref:`assets ` entries, :ref:`deferred expenses ` entries, and :ref:`deferred revenues ` entries." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:111 -msgid "You have three choices for the **Automation** field:" +msgid "You have three choices for the :guilabel:`Automation` field:" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:113 -#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:240 -#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:177 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:177 -msgid "**No:** this is the default value. Nothing happens." +msgid ":guilabel:`No`: this is the default value. Nothing happens." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:114 -msgid "**Create in draft:** whenever a transaction is posted on the account, a draft entry is created, but not validated. You must first fill out the corresponding form." +msgid ":guilabel:`Create in draft`: whenever a transaction is posted on the account, a draft entry is created, but not validated. You must first fill out the corresponding form." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:116 -msgid "**Create and validate:** you must also select a Model. Whenever a transaction is posted on the account, an entry is created and immediately validated." +msgid ":guilabel:`Create and validate`: you must also select a **model**. Whenever a transaction is posted on the account, an entry is created and immediately validated." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:120 -msgid "Please refer to the related documentation for more information." +#: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:3 +msgid "Default taxes" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:123 -msgid "Default Taxes" -msgstr "" - -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:125 +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:122 msgid "Select a **default tax** that will be applied when this account is chosen for a product sale or purchase." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:129 +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:126 msgid "Tags" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:131 +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:128 msgid "Some accounting reports require **tags** to be set on the relevant accounts. By default, you can choose among the tags that are used by the *Cash Flow Statement*." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:135 -msgid "Account Groups" +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:132 +msgid "Account groups" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:137 -msgid "**Account Groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and thus consolidate reports such as the **Trial Balance**." +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:134 +msgid "**Account groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and thus consolidate reports such as the **Trial Balance**. By default, groups are handled automatically based on the code of the group. For example, a new account `131200` is going to be part of the group `131000`." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:140 -msgid "To create a new Account Group, open the account you want to configure as sub-account, click on the *Group* drop-down selector, select *Create and Edit...*, fill out the form, and save. Next, set all the sub-accounts with the right Account Group." +msgid "Create account groups manually" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:144 -msgid "To display your **Trial Balance** report with your Account Groups, go to :menuselection:`Accounting --> Reporting --> Trial Balance`, then open the *Options* menu and select **Hierarchy and Subtotals**." +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:143 +msgid "Regular users should not need to create account groups manually. The following section is only intended for rare and advanced use cases." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:153 -msgid "Allow Reconciliation" +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:146 +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:155 -msgid "Some accounts, such as accounts made to record the transactions of a payment method, can be used for the reconciliation of journal entries." +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:None +msgid "Account groups creation." msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:158 -msgid "For example, an invoice paid with a credit card can be *marked as paid* if reconciled with the payment. Therefore, the account used to record credit card payments needs to be configured as *allowing reconciliation*." +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:156 +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:162 -msgid "To do so, check the **Allow Reconciliation** box and save." +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:None +msgid "Account Groups in the Trial Balance in Odoo Accounting" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:165 -msgid "Deprecated" +msgid "Allow reconciliation" msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:167 -msgid "It is not possible to delete an account once a transaction has been recorded on it. You can make them unusable by using the **Deprecated** feature." +msgid "Some accounts, such as accounts made to record the transactions of a payment method, can be used for the reconciliation of journal entries." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:170 -msgid "To do so, check the **Deprecated** box and save." -msgstr "" - -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:173 -msgid ":doc:`../../payables/supplier_bills/assets`" +msgid "For example, an invoice paid with a credit card can be marked as :guilabel:`paid` if reconciled with its payment. Therefore, the account used to record credit card payments needs to be configured as **allowing reconciliation**." msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:174 +msgid "To do so, check the :guilabel:`Allow Reconciliation` box in the account's settings, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:177 +msgid "Deprecated" +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:179 +msgid "It is not possible to delete an account once a transaction has been recorded on it. You can make them unusable by using the **Deprecated** feature." +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:182 +msgid "To do so, check the :guilabel:`Deprecated` box in the account's settings, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:185 +msgid ":doc:`../../payables/supplier_bills/assets`" +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:186 msgid ":doc:`../../payables/supplier_bills/deferred_expenses`" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:175 +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:187 msgid ":doc:`../../receivables/customer_invoices/deferred_revenues`" msgstr "" -#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:176 +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:188 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:193 #: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:52 #: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:125 @@ -9201,6 +10545,10 @@ 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 +msgid "Step-by-step onboarding banner in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:28 msgid ":ref:`accounting-setup-company`" msgstr "" @@ -9226,6 +10574,10 @@ 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 +msgid "Add your company's details in Odoo Accounting and Odoo Invoicing" +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:47 msgid "You can also change these settings by going to :menuselection:`Settings --> General Settings --> Settings --> Companies` and clicking on **Update Info**." msgstr "" @@ -9246,6 +10598,26 @@ msgstr "" msgid "If your Bank Institution can’t be synchronized automatically, or if you prefer not to sync it with your database, you may also configure your bank account manually by clicking on *Create it*, and filling out the form." msgstr "" +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:65 +msgid "**Name**: the bank account's name, as displayed on Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:66 +msgid "**Account Number**: your bank account number (IBAN in Europe)." +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:67 +msgid "**Bank**: click on *Create and Edit* to configure the bank's details. Add the bank institution's name and its Identifier Code (BIC or SWIFT)." +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:69 +msgid "**Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By default, Odoo creates a new Journal with this Short Code." +msgstr "" + +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:71 +msgid "**Journal**: This field is displayed if you have an existing Bank Journal that is not linked yet to a bank account. If so, then select the *Journal* you want to use to record the financial transactions linked to this bank account or create a new one by clicking on *Create and Edit*." +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:76 msgid "You can add as many bank accounts as needed with this tool by going to :menuselection:`Accounting --> Configuration`, and clicking on *Add a Bank Account*." msgstr "" @@ -9270,6 +10642,11 @@ msgstr "" msgid "You can also change these settings by going to :menuselection:`Accounting --> Configuration --> Settings --> Fiscal Periods` and updating the values." msgstr "" +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:100 +#: ../../content/applications/finance/accounting/getting_started/memento.rst:69 +msgid "Chart of Accounts" +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:102 msgid "With this menu, you can add accounts to your **Chart of Accounts** and indicate their initial opening balances." msgstr "" @@ -9278,6 +10655,10 @@ 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 +msgid "Setup of the Chart of Accounts and their opening balances in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:113 msgid ":doc:`Click here ` for more information on how to configure your Chart of Accounts." msgstr "" @@ -9298,6 +10679,10 @@ msgstr "" msgid "The Invoicing onboarding banner is composed of four main steps:" msgstr "" +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:None +msgid "Step-by-step onboarding banner in Odoo Invoicing" +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:132 msgid ":ref:`invoicing-setup-company`" msgstr "" @@ -9330,6 +10715,10 @@ 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 +msgid "Document layout configuration in Odoo Invoicing" +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:163 msgid "Add your **bank account number** and a link to your **General Terms & Condition** in the footer. This way, your contacts can find the full content of your GT&C online without having to print them on the invoices you issue." msgstr "" @@ -9369,6 +10758,10 @@ msgstr "" msgid ":doc:`chart_of_accounts`" msgstr "" +#: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:194 +msgid "`Odoo Tutorials: Accounting Basics `_" +msgstr "" + #: ../../content/applications/finance/accounting/getting_started/main_concept.rst:3 msgid "Main accounting concepts" msgstr "" @@ -9989,14 +11382,6 @@ msgstr "" msgid "A typical journal entry generated from a validated invoice will look like as follows:" 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 "" - #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:107 #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:128 msgid "**Partner**" @@ -10007,26 +11392,6 @@ msgstr "" msgid "**Due date**" 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:157 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:54 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:68 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:80 -msgid "**Debit**" -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:157 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:54 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:68 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:80 -msgid "**Credit**" -msgstr "" - #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:109 #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:111 #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:130 @@ -11420,318 +12785,152 @@ msgstr "" msgid "This is because the vendor refund will be made using the original purchase price, so to zero out the effect of the return in the stock input in last operation, we need to reuse the original price. The price difference account located on the product category is used to book the difference between the average cost and the original purchase price." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:3 -msgid "Record exchange rates at payments" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:3 +msgid "Multi-currency system" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:8 -msgid "Any company doing international trade faces the case where the payments are in a different currency." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:5 +msgid "Odoo allows you to issue invoices, receive bills, and record transactions in currencies other than the main currency configured for your company. You can also set up bank accounts in other currencies and run reports on your foreign currency activities." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:11 -msgid "After receiving their payments, you have the option to convert the amount into your company currency. Multi currency payment implies rates fluctuations. The rate differences are automatically recorded by Odoo." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:10 +msgid ":doc:`../bank/setup/foreign_currency`" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:19 -msgid "Enable multi-currencies" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:20 +msgid "Main currency" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:21 -msgid "In the accounting module, Go to :menuselection:`Configuration --> Settings` and flag **Allow multi currencies**, then click on **apply**." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:22 +msgid "The **main currency** is defined by default according to the company's country. You can change it by going to :menuselection:`Accounting --> Configuration --> Settings --> Currencies` and changing the currency in the :guilabel:`Main Currency` setting." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:27 -msgid "Configure the currency rates in :menuselection:`Configuration --> Currencies`. Write down the rate and make sure the currency is active." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:29 +msgid "Enable foreign currencies" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:33 -msgid "In this document, the base currency is **Euro** and we will record payments in **Dollars**." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:31 +msgid "Go to :menuselection:`Accounting --> Configuration --> Currencies`, and enable the currencies you wish to use by toggling the :guilabel:`Active` button." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:40 -msgid "You can automatically fetch the currency rates from the **European Central Bank** or from **Yahoo**. Please read the document : :doc:`how_it_works`." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:None +msgid "Enable the currencies you wish to use." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:45 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:31 -msgid "Configure your journal" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:41 +msgid "Currency rates" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:47 -msgid "In order to register payments in other currencies, you have to **remove the currency constraint** on the journal. Go to the accounting application, Click on **More** on the journal and **Settings**." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:44 +msgid "Manual update" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:54 -msgid "Check if the **Currency** field is empty or in the foreign currency in which you will register the payments. If a currency is filled in, it means that you can register payments only in this currency." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:46 +msgid "To manually create and set a currency rate, go to :menuselection:`Accounting --> Configuration --> Currencies`, click on the currency you wish to change the rate of, and under the :guilabel:`Rates` tab, click :guilabel:`Add a line` to create a new rate." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:62 -msgid "Record a payment in a different currency" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:None +msgid "Create or modify the currency rate." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:64 -msgid "In the **Accounting** application, go to :menuselection:`Sales --> Payments`. Register the payment and indicate that it was done in the foreign currency. Then click on **confirm**." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:55 +msgid "Automatic update" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:71 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:83 -msgid "The journal entry has been posted but not allocated." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:57 +msgid "When you activate a second currency for the first time, :guilabel:`Automatic Currency Rates` appears under :menuselection:`Accounting Dashboard --> Configuration --> Settings --> Currencies`. By default, you have to click on the **Update now** button (:guilabel:`🗘`) to update the rates." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:73 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:85 -msgid "Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and click on **Add** to allocate the payment." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:61 +msgid "Odoo can update the rates at regular intervals. To do so, change the :guilabel:`Interval` from :guilabel:`Manually` to :guilabel:`Daily`, :guilabel:`Weekly`, or :guilabel:`Monthly`. You can also select the web service from which you want to retrieve the latest currency rates by clicking on the :guilabel:`Service` field." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:80 -msgid "Record a bank statement in a different currency" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:69 +msgid "Exchange difference entries" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:82 -msgid "Create or import the bank statement of your payment. The **Amount** is in the company currency. There are two complementary fields, the **Amount currency**, which is the amount that was actually paid and the **Currency** in which it was paid." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:71 +msgid "Odoo automatically records exchange differences entries on dedicated accounts, in a dedicated journal." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:89 -msgid "When reconciling it, Odoo will directly match the payment with the right **Invoice**. You will get the invoice price in the invoice currency and the amount in your company currency." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:74 +msgid "You can define which journal and accounts to use to **post exchange difference entries** by going to :menuselection:`Accounting --> Configuration --> Settings --> Default Accounts` and editing the :guilabel:`Journal`, :guilabel:`Gain Account`, and :guilabel:`Loss Account`." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:97 -msgid "Check the exchange rate differences" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:79 +msgid "If you receive a payment for a customer invoice one month after it was issued, the exchange rate has likely changed since. Therefore, this fluctuation implies some profit or loss due to the exchange difference, which Odoo automatically records in the default **Exchange Difference** journal." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:99 -msgid "Go to :menuselection:`Adviser --> Journal Entries` and look for the **Exchange difference** journal entries. All the exchange rates differences are recorded in it." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:89 +msgid "Each account can have a set currency. By doing so, all moves relevant to the account are forced to have that account's currency." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:106 -msgid "The Exchange difference journal can be changed in your accounting settings." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:92 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Charts of Accounts` and select a currency in the field :guilabel:`Account Currency`. If left empty, all active currencies are handled instead of just one." 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." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:101 +msgid "If a currency is set on a **journal**, that journal only handles transactions in that currency." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:111 -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:147 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/cash_discounts.rst:68 -msgid ":doc:`../../bank/reconciliation/reconciliation_models`" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:103 +msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open the journal you want to edit, and select a currency in the field :guilabel:`Currency`. If left empty, all active currencies are handled instead of just one." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/exchange.rst:112 -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:100 -#: ../../content/applications/finance/accounting/payables/pay/sepa.rst:136 -msgid ":doc:`../../bank/reconciliation/use_cases`" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:None +msgid "Select the currency for the journal to handle." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:3 -msgid "Odoo's multi-currency system" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:114 +msgid "Multi-currency accounting" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:8 -msgid "Choosing to use the multi-currency option in Odoo will allow you to send sales invoices, quotes and purchase orders or receive bills and payments in currencies other than your own. With multi-currency, you can also set up bank accounts in other currencies and run reports on your foreign currency activities." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:119 +msgid "Invoices, bills, and other documents" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:18 -msgid "Turn on multi-currency" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:121 +msgid "For all documents, you can select the currency and journal to use for the transaction." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:20 -msgid "In the accounting module, Go to :menuselection:`Configuration --> Settings` and flag **Allow multi currencies**, then click on **Apply**." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:None +msgid "Select the currency and journal to use." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:27 -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:159 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:109 -msgid "Exchange Rate Journal" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:130 +msgid "Payment registration" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:29 -msgid "The **Rate Difference Journal** records the differences between the payment registration and the expected amount. For example, if a payment is paid 1 month after the invoice was issued, the exchange rate has probably changed. The fluctuation implies some loss or profit that are recorded by Odoo." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:132 +msgid "To register a payment in a currency other than your company's main currency, click on the :guilabel:`Register Payment` payment button of your document and, in the pop-up window, select a **currency** in the :guilabel:`Amount` field." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:35 -msgid "You can change it in the settings:" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:None +msgid "Select the currency and journal to use before registering the payment." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:41 -msgid "View or edit rate being used" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:145 +msgid "When creating or importing bank statements, the amount is in the company's main currency. To see additional fields related to foreign currencies, click on the **columns dropdown button** (:guilabel:`⋮`) next to :guilabel:`Amount`, and check :guilabel:`Amount Currency` and :guilabel:`Foreign Currency`." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:43 -msgid "You can manually configure the currency rates in :menuselection:`Configuration --> Currencies`. Open the currencies you want to use in Odoo and edit it. Make sure the currency is active." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:None +msgid "The extra fields related to foreign currencies." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:50 -msgid "Click on **View Rates** to edit it and to see the history :" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:154 +msgid "When reconciling, Odoo displays both the foreign currency amount and the equivalent amount in your company's main currency." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:55 -msgid "Click on **Create** to add the rate. Fill in the date and the rate. Click on **Save** when you are done." +#: ../../content/applications/finance/accounting/others/multi_currency.rst:160 +msgid "Exchange rate journal entries" msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:62 -msgid "Live Currency Rate" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:162 +msgid "To see **exchange difference journal entries**, go to :menuselection:`Accounting Dashboard --> Accounting --> Journals: Miscellaneous`." msgstr "" -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:64 -msgid "By default, the currencies need to be updated manually. But you can synchronize it with `Yahoo `__ or the `European Central Bank `__. In :menuselection:`Configuration --> Settings`, go to the **Live Currency Rate** section." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:69 -msgid "Choose the interval : Manually, Daily, Weekly or Monthly. You can always force the update by clicking on **Update Now**. Select the provider, and you are set !" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:77 -msgid "Only the **active** currencies are updated" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:80 -msgid "Configure your charts of account" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:82 -msgid "In the accounting application, go to :menuselection:`Adviser --> Charts of Accounts`. On each account, you can set a currency. It will force all moves for this account to have the account currency." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:86 -msgid "If you leave it empty, it means that it can handle all currencies that are Active." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:93 -msgid "Configure your journals" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:95 -msgid "In order to register payments in other currencies, you have to remove the currency constraint on the journal. Go to the accounting application, Click on **More** on the journal and **Settings**." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:102 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:40 -msgid "Check if the currency field is empty or in the foreign currency in which you will register the payments. If a currency is filled in, it means that you can register payments only in this currency." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:110 -msgid "How is Odoo's multi-currency working?" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:112 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:50 -msgid "Now that you are working in a multi-currency environment, all accountable items will be linked to a currency, domestic or foreign." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:116 -msgid "Sales Orders and Invoices" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:118 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:56 -msgid "You are now able to set a different currency than the company one on your sale orders and on your invoices. The currency is set for the whole document." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:126 -msgid "Purchases orders and Vendor Bills" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:128 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:66 -msgid "You are now able to set a different currency than the company one on your purchase orders and on your vendor bills. The currency is set for the whole document." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:136 -msgid "Payment Registrations" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:138 -msgid "In the accounting application, go to :menuselection:`Sales --> Payments`. Register the payment and set the currency." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:145 -msgid "Bank Statements" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:147 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:94 -msgid "When creating or importing bank statements, the amount is in the company currency. But there are now two complementary fields, the amount that was actually paid and the currency in which it was paid." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:154 -msgid "When reconciling it, Odoo will directly match the payment with the right Invoice. You will get the invoice price in the invoice currency and the amount in your company currency." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:161 -msgid "Go to :menuselection:`Adviser --> Journal Entries` and look for the Exchange difference journal entries. All the exchange rates differences are recorded in it." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:170 -msgid ":doc:`invoices_payments`" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/how_it_works.rst:171 -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:121 -msgid ":doc:`exchange`" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:3 -msgid "Manage invoices and payment in multiple currencies" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:8 -msgid "Odoo provides multi-currency support with automatic currency gross or loss entry adjustment. There are a few things Odoo has been to ease the user's life." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:12 -msgid "All the account transactions will be done using the company currency. However you can see two extra fields with the journal entry where secondary currency and amount will visible. You can create multi-currency journals of force a specific currency." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:17 -msgid "When creating an invoice, the currency can be changed very easily; however Odoo takes the company currency as a default assignment. It will convert all the amounts automatically using that currency." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:25 -msgid "Enable Multi-Currency" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:27 -msgid "For information about enabling Multi-Currency, please read the document: :doc:`how_it_works`" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:33 -msgid "In order to register payments in other currencies, you have to remove the currency constraint on the journal. Go to the accounting application, on the journal, click on :menuselection:`More --> Settings`." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:48 -msgid "Multi-currency invoices & Vendor Bills" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:54 -msgid "Invoices" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:74 -msgid "Multi-currency Payments" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:76 -msgid "In the accounting application, go to :menuselection:`Sales --> Payments`. Register the payment and indicate that it was done in the foreign currency. Then click on **Confirm**." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:92 -msgid "Multi- Currency Bank Statements" -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:101 -msgid "When reconciling it, Odoo will directly match the payment with the right invoice. You will get the invoice price in the invoice currency and the amount in your company currency." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:111 -msgid "Go to :menuselection:`Adviser --> Journal Entries` and look for the **Exchange Difference** journal entries. All the exchange rates differences are recorded in it." -msgstr "" - -#: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:120 -msgid ":doc:`how_it_works`" +#: ../../content/applications/finance/accounting/others/multi_currency.rst:None +msgid "Exchange rate journal entry." msgstr "" #: ../../content/applications/finance/accounting/payables.rst:5 @@ -11948,123 +13147,64 @@ msgid "Pay several bills at once" msgstr "" #: ../../content/applications/finance/accounting/payables/pay/multiple.rst:5 -msgid "Odoo provides a simple and effective way to handle several bills at once, with various quick or complex options. With one single process, anyone is able to handle bills and payment in just a few clicks." +msgid "Odoo offers the possibility of grouping multiple bills' payments into one, facilitating the reconciliation process." +msgstr "" + +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:9 +msgid ":doc:`../supplier_bills/manage`" msgstr "" #: ../../content/applications/finance/accounting/payables/pay/multiple.rst:10 -msgid "Pay multiple bills with one payment" +#: ../../content/applications/finance/accounting/payables/pay/sepa.rst:136 +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:47 +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:72 +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:121 +msgid ":doc:`../../bank/reconciliation/use_cases`" msgstr "" #: ../../content/applications/finance/accounting/payables/pay/multiple.rst:13 -msgid "Record several payments" +msgid "Group payments" msgstr "" #: ../../content/applications/finance/accounting/payables/pay/multiple.rst:15 -msgid "In the following example, we will generate some bills. You can control the whole process from your accounting dashboard (first screen you get when you open the accounting application)." +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:22 -msgid "To create a bill, open the Dashboard menu and click on **Vendor Bills**. In the Vendor Bills window, click on **Create**." +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:None +msgid "Register payment button." msgstr "" -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:28 -msgid "Choose the vendor from which you wish to purchase the product, and click on Add an item to add one (or more) product(s). Click on **Save** and then **Validate**." +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:25 +msgid "Payments can only be registered for :guilabel:`posted` bills." +msgstr "" + +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:27 +msgid "When registering the payments, a **pop-up window** appears. From here, you can either create **separate payments** for each bill all at once by clicking :guilabel:`Create Payment`, *or* create one payment by combining **all** bills' payments. To **combine** all payments, tick the :guilabel:`Group Payments` box." msgstr "" #: ../../content/applications/finance/accounting/payables/pay/multiple.rst:33 -msgid "Pay supplier bills, one after the other" +msgid "The :guilabel:`Group Payments` option only appears when selecting two or more bills." msgstr "" -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:38 -msgid "We will now record a payment for one bill only. Open the bill, then click on **Register Payment**. Insert the Payment Method, Date and Amount, and click on **Validate**." +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:None +msgid "Group payments options when registering a payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:39 +msgid "When selecting :guilabel:`Group Payments`, the :guilabel:`amount, currency, date and memo` are all set automatically, but you can modify them according to your needs." +msgstr "" + +#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:43 +msgid "Partial group payments with cash discounts" msgstr "" #: ../../content/applications/finance/accounting/payables/pay/multiple.rst:45 -msgid "Once you have validated the payment, the system will automatically reconcile the payment with the bill, and set the bill as **Paid**. The system will also generate a move from the payment account and reconcile it with the expense transaction." +msgid "In case of **partial group payments with cash discounts**, you can follow the steps found on the :doc:`cash discount documentation page <../../receivables/customer_invoices/cash_discounts>`. Make sure to apply the :doc:`payment terms <../../receivables/customer_invoices/payment_terms>` to the **bills** *instead* of the invoices." msgstr "" #: ../../content/applications/finance/accounting/payables/pay/multiple.rst:51 -msgid "Pay several bills altogether" -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:53 -msgid "In order to illustrate the process thoroughly, create at least 2 more bills following the above standing guide. **Make sure all bills come from the same vendor.**" -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:60 -msgid "In the Vendors Bills, select the new bills you have just created by checking the box next to each of them. In the Action menu located in the middle of the page, click on **Register Payment**." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:67 -msgid "Insert the details of the payment. The system calculated the total amount for both bills, but you can modify it freely. Click on **Validate**." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:71 -msgid "Record the payment, reconcile afterwards" -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:73 -msgid "You can also reconcile a payment with bills after the payment has been recorded." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:76 -msgid "First, we need to create a payment" -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:78 -msgid "This will handle from :menuselection:`Dashboard --> Bank journal --> More Option --> Send Money`" -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:84 -msgid "Creating payment order with check payment method. Selecting related Vendor and amount which remain to pay. After filling all details, we will confirm the payment order which will generate payment transaction with the system." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:92 -msgid "As you can see, bill payment status show what is posted and what is remaining to reconcile." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:95 -msgid "After receiving bank statement from the bank with payment detail, you can reconcile the transaction from the Dashboard. It will automatically map the transaction amount." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:103 -msgid "Partial payments of several supplier bills" -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:106 -msgid "How to pay several supplier bills having cash discounts at once?" -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:108 -msgid "You already learned how to pay bills in various way but what about partial payment? We are taking another example where we will do partial payment for various bills." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:112 -msgid "We are creating multiple bills and partially pay them through bank statements." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:115 -msgid "We are adding payment terms which allow some cash discount where vendor offer us early payment discount." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:121 -msgid "We are creating the following bills with the assignment of the above payment term." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:127 -msgid "We have created the following bills:" -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:132 -msgid "We will pay the invoices by creating bank statement where we will adjust the cash discount our vendor provided under payment terms." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:138 -msgid "Before reconciling this bank statement, we need to create one statement model for cash discount." -msgstr "" - -#: ../../content/applications/finance/accounting/payables/pay/multiple.rst:144 -msgid "Now we are going back to bank statement and opening reconcile view." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/cash_discounts.rst:67 +msgid ":doc:`../../receivables/customer_invoices/payment_terms`" msgstr "" #: ../../content/applications/finance/accounting/payables/pay/sepa.rst:3 @@ -12177,7 +13317,6 @@ msgid "In order to send a SEPA payment, the recipient must be identified by a va msgstr "" #: ../../content/applications/finance/accounting/payables/pay/sepa.rst:134 -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:125 msgid ":doc:`check`" msgstr "" @@ -12248,6 +13387,10 @@ 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 +msgid "Configuration of an Assets Account in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:48 msgid "This account's type must be either *Fixed Assets* or *Non-current Assets*." msgstr "" @@ -12266,6 +13409,10 @@ 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 +msgid "Selection of an Assets Account on a draft bill in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:65 #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:61 msgid "Choose a different Expense Account for specific products" @@ -12276,6 +13423,10 @@ 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 +msgid "Change of the Assets Account for a product in Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:75 msgid "It is possible to :ref:`automate the creation of assets entries ` for these products." msgstr "" @@ -12291,6 +13442,12 @@ 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 +msgid "Modification of a posted journal item's account in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:92 msgid "Assets entries" msgstr "" @@ -12313,10 +13470,18 @@ 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 +msgid "Assets entry in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:113 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 +msgid "Depreciation Board in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:122 #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:114 #: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:113 @@ -12367,6 +13532,10 @@ 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 +msgid "Create Asset Entry from a journal item in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:165 msgid "Modification of an Asset" msgstr "" @@ -12387,6 +13556,10 @@ 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 +msgid "Gross Increase smart button in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:184 msgid "Disposal of Fixed Assets" msgstr "" @@ -12399,6 +13572,10 @@ 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 +msgid "Disposal of Assets in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:194 msgid "Odoo Accounting then generates all the journal entries necessary to dispose of the asset, including the gain or loss on sale, which is based on the difference between the asset's book value at the time of the sale and the amount it is sold for." msgstr "" @@ -12437,6 +13614,10 @@ 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 +msgid "Assets model button in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:232 msgid "Automate the Assets" msgstr "" @@ -12449,6 +13630,12 @@ msgstr "" msgid "You have three choices for the **Automate Assets** field:" msgstr "" +#: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:240 +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:177 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:177 +msgid "**No:** this is the default value. Nothing happens." +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:241 msgid "**Create in draft:** whenever a transaction is posted on the account, a draft *Assets entry* is created, but not validated. You must first fill out the form in :menuselection:`Accounting --> Accounting --> Assets`." msgstr "" @@ -12457,6 +13644,10 @@ 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 +msgid "Automate Assets on an account in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/assets.rst:252 msgid "You can, for example, select this account as the default **Expense Account** of a product to fully automate its purchase. (see: :ref:`product-assets-account`)." msgstr "" @@ -12493,6 +13684,10 @@ msgstr "" msgid "Configure a Deferred Expense Account" msgstr "" +#: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:None +msgid "Configuration of a Deferred Expense Account in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:45 msgid "This account's type must be either *Current Assets* or *Prepayments*" msgstr "" @@ -12501,6 +13696,14 @@ 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 +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 +msgid "Change of the Expense Account for a product in Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:71 msgid "It is possible to automate the creation of expense entries for these products (see: `Automate the Deferred Expenses`_)." msgstr "" @@ -12521,10 +13724,18 @@ 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 +msgid "Deferred Expense entry in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:105 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 +msgid "Expense Board in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:116 msgid "The **Prorata Temporis** feature is useful to recognize your expense the most accurately possible." msgstr "" @@ -12554,6 +13765,11 @@ 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 +msgid "Create Deferred Entry from a journal item in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:142 msgid "Deferred Expense Models" msgstr "" @@ -12578,6 +13794,10 @@ 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 +msgid "Deferred Expense model button in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:170 msgid "Automate the Deferred Expenses" msgstr "" @@ -12598,6 +13818,10 @@ 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 +msgid "Automate Deferred Expense on an account in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/deferred_expenses.rst:190 msgid "You can, for example, select this account as the default **Expense Account** of a product to fully automate its purchase. (see: `Choose a different Expense Account for specific products`_)." msgstr "" @@ -12693,7 +13917,8 @@ msgid "To buy credits, go to :menuselection:`Accounting --> Configuration --> Se msgstr "" #: ../../content/applications/finance/accounting/payables/supplier_bills/invoice_digitization.rst:74 -msgid "If you are on Odoo Online (SaaS) and have the Enterprise version, you benefit from free trial credits to test the feature." +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:45 +msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" #: ../../content/applications/finance/accounting/payables/supplier_bills/invoice_digitization.rst:78 @@ -12936,6 +14161,10 @@ 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 +msgid "Fill out the draft purchase receipt in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/purchase_receipts.rst:27 msgid "You can register the payment by clicking on *Register Payment*, then filling out the payment's details, and clicking on *Validate*." msgstr "" @@ -12952,6 +14181,10 @@ 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 +msgid "Change the accounts used in the journal entry to record a purchase receipt." +msgstr "" + #: ../../content/applications/finance/accounting/payables/supplier_bills/purchase_receipts.rst:44 msgid ":doc:`manage`" msgstr "" @@ -13012,8 +14245,8 @@ msgstr "" msgid "In this case, the customer has not fulfilled the payment term and cannot benefit from the cash discount. When you process the bank statement, match the payment with the two related journal entries." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/cash_discounts.rst:67 -msgid ":doc:`../../receivables/customer_invoices/payment_terms`" +#: ../../content/applications/finance/accounting/receivables/customer_invoices/cash_discounts.rst:68 +msgid ":doc:`../../bank/reconciliation/reconciliation_models`" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/cash_rounding.rst:3 @@ -13211,6 +14444,10 @@ msgstr "" msgid "Configure a Deferred Revenue Account" msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:None +msgid "Configuration of a Deferred Revenue Account in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:44 msgid "This account's type must be either *Current Liabilities* or *Non-current Liabilities*" msgstr "" @@ -13227,6 +14464,10 @@ 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 +msgid "Selection of a Deferred Revenue Account on a draft invoice in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:60 msgid "Choose a different Income Account for specific products" msgstr "" @@ -13235,6 +14476,10 @@ 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 +msgid "Change of the Income Account for a product in Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:70 msgid "It is possible to automate the creation of revenue entries for these products (see: `Automate the Deferred Revenues`_)." msgstr "" @@ -13259,10 +14504,18 @@ 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 +msgid "Deferred Revenue entry in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:104 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 +msgid "Revenue Board in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:115 msgid "The **Prorata Temporis** feature is useful to recognize your revenue the most accurately possible." msgstr "" @@ -13311,6 +14564,10 @@ 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 +msgid "Deferred Revenue model button in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:170 msgid "Automate the Deferred Revenues" msgstr "" @@ -13331,6 +14588,10 @@ 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 +msgid "Automate Deferred Revenue on an account in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/deferred_revenues.rst:190 msgid "You can, for example, select this account as the default **Income Account** of a product to fully automate its sale. (see: `Choose a different Income Account for specific products`_)." msgstr "" @@ -13475,6 +14736,10 @@ 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 +msgid "Select the EDI format you need" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:64 msgid "Once an electronic invoicing format is enabled, XML documents are generated when clicking on :guilabel:`Confirm` in documents such as invoices, credit notes, etc. These documents are either visible in the attachment section, or embedded in the PDF." msgstr "" @@ -13915,6 +15180,11 @@ 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 +msgid "Example of Payment Terms. The last line is the balance due on the 31st of the following\n" +"month." +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:71 msgid "Using Payment Terms" msgstr "" @@ -13971,6 +15241,11 @@ 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 +msgid "The amount debited on the Account Receivable is split into two Journal Items with distinct\n" +"Due Dates" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:107 msgid "In this example, an invoice of $1000 has been issued with the following payment terms: *30% is due on the day of issuance, and the balance is due at the end of the following month.*" msgstr "" @@ -14023,6 +15298,10 @@ msgstr "" msgid "If you would like this option to be a default feature, enable *Send by Post* under *Default Sending Options*." msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:None +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 "" @@ -14031,6 +15310,10 @@ msgstr "" msgid "Open your Invoice, click on the *Send & Print* button and select *Send 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" +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." msgstr "" @@ -14043,10 +15326,6 @@ msgstr "" 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*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:45 -msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." -msgstr "" - #: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:47 msgid "Click `here `_ to know about our *Privacy Policy*." msgstr "" @@ -14083,6 +15362,10 @@ 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 +msgid "Payment Method Types in a journal's advanced settings" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:35 msgid "Your main bank accounts are automatically configured to process batch payments when you activate the feature." msgstr "" @@ -14099,6 +15382,10 @@ 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 +msgid "Registering a customer payment as part of a Batch Deposit in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:53 msgid "Do this step for all checks or payments you want to process in batch." msgstr "" @@ -14115,10 +15402,18 @@ 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 +msgid "Filling out a new Inbound Batch Payment form on Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:69 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 +msgid "Selection of all payments to include in the Batch Deposit" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:76 msgid "Once done, click on *Validate* to finalize your Batch Deposit. You can then click on *Print* to download a PDF file to include with the deposit slip that the bank usually requires to fill out." msgstr "" @@ -14131,6 +15426,10 @@ 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 +msgid "Reconciliation of the Batch Payment with all its transactions" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:95 msgid "If a check, or a payment, couldn't be processed by the bank and is missing, remove the related payment before validating the bank reconciliation." msgstr "" @@ -14167,6 +15466,10 @@ msgstr "" msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`, activate **SEPA Direct Debit (SDD)** and click on *Save*. Enter your company's **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 +msgid "Add a SEPA Creditor Identifier to Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:31 msgid "SEPA Direct Debit Mandates" msgstr "" @@ -14183,6 +15486,10 @@ msgstr "" msgid "To create a new mandate, go to :menuselection:`Accounting --> Customers --> Direct Debit Mandates`, click on *Create*, and fill out the form." msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:None +msgid "Fill out SEPA Direct Debit in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:46 msgid "Export the PDF file by clicking on *Print*. It is then up to your customer to sign this document. Once done, upload the signed file in the **Original Document** field, and click on *Validate* to start running the mandate." msgstr "" @@ -14223,6 +15530,10 @@ msgstr "" msgid "Direct Debit mandates are closed automatically after their *End Date*. If this field is left blank, the mandate keeps being *Active* until it is *Closed* or *Revoked*." msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:None +msgid "Close or Revoke an SDD Mandate in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:85 msgid "Clicking on **Close** updates the mandate’s end day to the current day. This means that invoices issued after the present day will not be processed with an SDD payment." msgstr "" @@ -14267,14 +15578,26 @@ msgstr "" msgid "To generate your XML file for the pending SDD payments, go to the related *bank journal* on your *Accounting dashboard*, then click on *Direct Debit Payments to Collect*." msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:None +msgid "Start the SDD payments collection in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:124 msgid "Select all the payments you want to include in your SDD XML file, then click on *Action* and select *Create Batch Payment*." msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:None +msgid "Create a batch payment with all the SDD payments in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:131 msgid "Odoo then takes you to your *Batch Payment*’s form. Click on *Validate* and download the SDD XML file." msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:None +msgid "Generate an XML file for your SDD payments in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:138 msgid "Finally, upload this file to your online banking interface to process the payments." msgstr "" @@ -14523,6 +15846,10 @@ 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 +msgid "Set debtor's trust level" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/followup.rst:71 msgid "Send reminders in batches" msgstr "" @@ -14539,6 +15866,10 @@ 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 +msgid "Payment acquirer choice after having clicked on \"Pay Now\"" +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:17 msgid "Make sure your :ref:`Payment Acquirers are correctly configured `." msgstr "" @@ -14559,10 +15890,18 @@ 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 +msgid "Email with a link to view the invoice online on the Customer Portal." +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:37 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 +msgid "\"Pay now\" button on an invoice in the Customer Portal." +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_payments/online_payment.rst:45 msgid ":doc:`/applications/finance/payment_acquirers`" msgstr "" @@ -14572,107 +15911,127 @@ msgid "Different ways to record a payment" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:5 -msgid "In Odoo, a payment can either be linked directly to an invoice or be a stand alone record for use on a later date:" +msgid "In Odoo, payments can either be linked automatically to an invoice or bill or be stand-alone records for use at a later date." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:8 -msgid "If a payment is linked to an invoice, it reduces the amount due of the invoice. You can have multiple payments linked to the same invoice." +msgid "If a payment is **linked to an invoice or bill**, it reduces the amount due of the invoice. You can have multiple payments related to the same invoice." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:12 -msgid "If a payment is not linked to an invoice, the customer has an outstanding credit with your company, or your company as an outstanding balance with a vendor. You can use this outstanding credit/debit to pay future invoices or bills." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:11 +msgid "If a payment is **not linked to an invoice or bill**, the customer has an outstanding credit with your company, or your company has an outstanding debit with a vendor. You can use those outstanding amounts to reduce unpaid invoices/bills." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:16 +msgid "Registering payment from an invoice or bill" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:18 -msgid "Paying an invoice" +msgid "When you click on :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new journal entry and changes the amount due according to the amount of the payment. The counterpart is reflected in an outstanding receipts or payments account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when the outstanding account is reconciled with a bank statement line, the invoice or vendor bill changes to the :guilabel:`Paid` status." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:20 -msgid "If you register a payment on a customer invoice or a vendor bill, the payment is automatically reconciled with the invoice reducing the amount due." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:24 +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:27 -msgid "The green icon near the payment line will display more information about the payment. From there you can choose to open the journal entry or reconcile the payment." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:None +msgid "See detailed information of a payment" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:32 -msgid "If you unreconcile a payment, it is still registered in your books but not linked to the specific invoice any longer. If you unreconcile a payment in a different currency, Odoo will create a journal entry to reverse the Currency Exchange Loss/Gain posted at the time of reconciliation." +msgid "The customer invoice or vendor bill should be in the status :guilabel:`Posted` to register the payment." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:38 -msgid "Payments not tied to an invoice" +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:34 +msgid "When clicking on :guilabel:`Register payment`, you can select the amount to pay and make a partial or full payment." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:36 +msgid "If your main bank account is set as :doc:`oustanding account <../../bank/setup/outstanding_accounts>`, and the payment is made in Odoo (not related to a bank statement), invoices and bills are directly registered in the status :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:39 +msgid "If you unreconciled a payment, it still appears in your books but is no longer linked to the invoice." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:41 -msgid "Registering a payment" +msgid "If you (un)reconcile a payment in a different currency, a journal entry is automatically created to post the currency exchange gains/losses (reversal) amount." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:43 -msgid "In the Accounting application, you can create a new payment from the Sales menu (register a customer payment) or the Purchases menu (pay a vendor). If you use these menus, the payment is not linked to an invoice, but can easily be reconciled on an invoice later on." +msgid "If you (un)reconcile a payment and an invoice having cash basis taxes, a journal entry is automatically created to post the cash basis tax (reversal) amount." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:51 -msgid "When registering a new payment, you must select a customer or vendor, the payment method, and the amount of the payment. The currency of the transaction is defined by the payment method. If the payment refers to a document (sale order, purchase order or invoice), set the reference of this document in the memo field." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:50 +msgid "Registering payments not tied to an invoice or bill" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:57 -msgid "Once confirmed, a journal entry will be posted reflecting the transaction just made in the accounting application." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:52 +msgid "When a new payment is registered via the menu :menuselection:`Customers / Vendors --> Payments`, it is not directly linked to an invoice or bill. Instead, the account receivable or the account payable are matched with the outstanding account until they are manually matched with their related invoice or bill." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:61 -msgid "Reconciling invoice payments" +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:58 +msgid "Matching invoices and bills with payments" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:63 -msgid "The easiest way of reconciling a payment with an invoice is to do so on the invoice directly." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:60 +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:66 -msgid "When validating a new invoice, Odoo will warn you that an outstanding payment for this customer or vendor is available. In this case, you can reconcile this payment to the invoice near the totals at the bottom, under \"Outstanding Payments\"." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:None +msgid "Shows the ADD option to reconcile an invoice or a bill with a payment" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:68 +msgid "The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with the bank statement." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:75 -msgid "Reconciling all your outstanding payments and invoices" +msgid "Batch payment" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:77 -msgid "If you want to reconcile all outstanding payments and invoices at once (instead of doing so one by one), you can use the batch reconciliation feature within Odoo." +msgid "Batch payments allow you to group different payments to ease reconciliation. They are also useful when you deposit checks to the bank or for SEPA Payments. Go to :menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the list view of payments, you can select several payments and group them in a batch clicking on :menuselection:`Action > Create Batch Payment`." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:81 -msgid "The batch reconciliation feature is available from the dashboard on the Customer Invoices card and the Vendor Bills card for reconciling Accounts Receivable and Payable, respectively." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:84 +msgid ":doc:`../../receivables/customer_payments/batch`" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:85 +msgid ":doc:`../../receivables/customer_payments/batch_sdd`" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:88 -msgid "The payments matching tool will open all unreconciled customers or vendors and will give you the opportunity to process them all one by one, doing the matching of all their payments and invoices at once." +msgid "Payments matching" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:95 -msgid "During the reconciliation, if the sum of the debits and credits do not match, it means there is still a remaining balance that either needs to be reconciled at a later date, or needs to be written off directly." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:90 +msgid "The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and gives you the opportunity to process them all one by one, doing the matching of all their payments and invoices at once. You can reach this tool from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor Bills`, and click on :guilabel:`⋮` and select :guilabel:`Payments Matching`, or by going to :menuselection:`Accounting --> Reconciliation`." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:100 -msgid "Transferring money from one bank account to another" +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:97 +msgid "During the reconciliation, if the sum of the debits and credits does not match, it means there is a remaining balance that either needs to be reconciled at a later date or needs to be written off directly." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:102 -msgid "Just like making a customer or vendor payment, you transfer cash internally between your bank accounts from the dashboard or from the menus up top." +msgid "Batch payments matching" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:109 -msgid "This will take you to the same screen you have for receiving and making payments." +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:104 +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 +msgid "See the reconcile option" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:114 +msgid "Reconciling payments with bank statements" msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:116 -msgid "When making an internal transfer from one bank account to another, select the bank you want to apply the transfer from in the dashboard, and in the register payments screen, you select the transfer to account. Do not go through this process again in the other bank account or else you will end up with two journal entries for the same transaction." -msgstr "" - -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:124 -msgid ":doc:`online_payment`" -msgstr "" - -#: ../../content/applications/finance/accounting/receivables/customer_payments/recording.rst:126 -msgid ":doc:`followup`" +msgid "Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The next step is to reconcile it with the related bank statement line to have the transaction finalized and the invoice or bill marked as :guilabel:`Paid`." msgstr "" #: ../../content/applications/finance/accounting/reporting/declarations.rst:5 @@ -14743,6 +16102,10 @@ msgstr "" msgid "**Journal**: select the journal in which to record the tax return." msgstr "" +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +msgid "Configure how often tax returns have to be made in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:39 msgid "This is usually configured during the :doc:`app's initial set up <../../getting_started/initial_configuration/setup>`." msgstr "" @@ -14755,10 +16118,18 @@ msgstr "" msgid "Odoo generates Tax Reports based on the **Tax Grids** settings that are configured on your taxes. Therefore, it is crucial to make sure that all the recorded transactions use the right taxes. You can see on each Journal Item which Tax Grid is used for that transaction." msgstr "" +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +msgid "see which tax grids are used to record transactions in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:53 msgid "To configure your taxes' 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 +msgid "Configure taxes and their tax grids in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:62 msgid "Taxes and reports are usually already pre-configured: a *Fiscal Localization Package* is installed according to the country you select at the creation of your database. :doc:`Click here <../../fiscal_localizations/overview/fiscal_localization_packages>` for more information about Fiscal Localization Packages." msgstr "" @@ -14783,6 +16154,10 @@ msgstr "" msgid "To check the current **Tax Lock Date**, or to edit it, go to :menuselection:`Accounting --> Accounting --> Lock Dates`." msgstr "" +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +msgid "Lock your tax for a specific period in Odoo Acounting" +msgstr "" + #: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:91 #: ../../content/applications/finance/accounting/reporting/overview/main_reports.rst:135 msgid "Tax Report" @@ -14800,10 +16175,18 @@ msgstr "" msgid "Make sure to select the right period you want to declare by using the date filter. You can see an overview of your tax report. Then, click on the button *Closing Journal Entry*." msgstr "" +#: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:None +msgid "Select the period for the tax return and create a closing journal entry in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:106 msgid "After having reviewed the generated Journal Entry, click on *Post*. In addition to posting the entry, Odoo automatically creates a PDF file with the **Tax Report** that you can download from the chatter and preview on the right column. It includes 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 +msgid "download the PDF with your Tax Report in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:116 msgid "If you forgot to :ref:`lock your tax date ` before clicking on *Closing Journal Entry*, then Odoo automatically locks your fiscal period on the same date as the Accounting Date of your entry. This automatic lock happens when you click on *Post*. This safety mechanism can prevent some fiscal errors, but it is advised to lock your tax date manually before, as described above." msgstr "" @@ -14916,6 +16299,62 @@ msgstr "" msgid ":doc:`main_reports`" msgstr "" +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:3 +msgid "Data inalterability check report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:5 +msgid "Tax authorities in some countries require companies to **prove their posted accounting entries are inalterable**, meaning that once an entry has been posted, it can no longer be changed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:8 +msgid "To do so, Odoo can use the **SHA-256 algorithm** to create a unique fingerprint for each posted entry. This fingerprint is called a hash. The hash is generated by taking an entry's essential data (the values of the `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and `partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the same input always creates the same output`): any minor modification to the original data would completely change the resulting hash. Consequently, the SHA-256 algorithm is often used, among others, for data integrity verification purposes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:17 +msgid "In addition, the previous entry's hash is always added to the next entry to form a **hash chain**. This is used to ensure a new entry is not added afterward between two posted entries, as doing so would break the hash chain." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:22 +msgid "Hashes generated by the SHA-256 algorithm are theoretically not unique, as there is a finite number of possible values. However, this number is exceptionally high: 2²⁵⁶, which is a lot bigger than the number of atoms in the known universe. This is why hashes are considered unique in practice." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:30 +msgid "Lock posted entries with hash" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:32 +msgid "To start using the hashing function, go to :menuselection:`Accounting --> Configuration > Journals`. Open the journal for which you want to activate the feature, go to the :guilabel:`Advanced Settings` tab, and enable :guilabel:`Lock Posted Entries with Hash`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:37 +msgid "Once you post an entry on a locked journal, you cannot disable the feature anymore, nor edit any posted entry." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:43 +msgid "Report download" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:45 +msgid "To download the data inalterability check report, go to :menuselection:`Accounting --> Configuration --> Settings --> Reporting` and click on :guilabel:`Download the Data Inalterability Check Report`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:48 +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 +msgid "Configuration report for two journals" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/overview/data_inalterability.rst:57 +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 +msgid "Data consistency check report for a journal" +msgstr "" + #: ../../content/applications/finance/accounting/reporting/overview/main_reports.rst:3 msgid "Main reports available" msgstr "" @@ -15096,10 +16535,6 @@ msgstr "" msgid "Taxation" msgstr "" -#: ../../content/applications/finance/accounting/taxation/fiscal_year.rst:5 -msgid "Fiscal year" -msgstr "" - #: ../../content/applications/finance/accounting/taxation/fiscal_year/close_fiscal_year.rst:3 msgid "Do a year end in Odoo (close a fiscal year)" msgstr "" @@ -15416,6 +16851,10 @@ 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 +msgid "Configure Avatax settings" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:25 msgid "Tax mapping" msgstr "" @@ -15428,10 +16867,18 @@ 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 +msgid "Specify Avatax Category on products" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:36 msgid "Avatax Categories may be overridden or set on individual products as well." msgstr "" +#: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:None +msgid "Override product categories as needed" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:45 msgid "Address validation" msgstr "" @@ -15440,10 +16887,18 @@ 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 +msgid "Validate customer addresses" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:54 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 +msgid "Address validation wizard" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:64 msgid "Tax calculation" msgstr "" @@ -15459,103 +16914,140 @@ msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/avatax.rst:74 #: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:39 #: ../../content/applications/finance/accounting/taxation/taxes/eu_distance_selling.rst:68 -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:139 +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:151 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:279 msgid ":doc:`fiscal_positions`" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:3 -msgid "Manage cash basis taxes" +msgid "Cash basis taxes" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:5 -msgid "The cash basis taxes are due when the payment has been done and not at the validation of the invoice (as it is the case with standard taxes). Reporting your income and expenses to the administration based on the cash basis method is legal in some countries and under some conditions." +msgid "Cash basis taxes are due when the payment is made, as opposed to standard taxes that are due when the invoice is confirmed. Reporting your income and expenses to the government based on the cash basis method is mandatory in some countries and under some conditions." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:10 -msgid "Example : You sell a product in the 1st quarter of your fiscal year and receive the payment the 2nd quarter of your fiscal year. Based on the cash basis method, the tax you have to pay to the administration is due for the 2nd quarter." +msgid "You sell a product in the 1st quarter of your fiscal year, and the payment is received in the 2nd quarter. Based on the cash basis method, the tax you must pay is for the 2nd quarter." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:16 -msgid "How to configure cash basis taxes ?" +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and under the :guilabel:`Taxes` section, enable :guilabel:`Cash Basis`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:18 -msgid "You first have to activate the setting in :menuselection:`Accounting --> Configuration --> Settings --> Allow Tax Cash Basis`. You will be asked to define the Tax Cash Basis Journal." +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:19 +msgid "Then, define the :guilabel:`Tax Cash Basis Journal`. Click on the external link button next to the journal to update its default properties such as the :guilabel:`Journal Name`, :guilabel:`Type` or :guilabel:`Short Code`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:27 -msgid "Once this is done, you can configure your taxes in :menuselection:`Accounting --> Configuration --> Taxes`. At first set the proper transitional accounts to post taxes until you register the payment." +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:None +msgid "Select your Tax Cash Basis Journal and click on the external link" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:28 +msgid "By default, the journal entries of the :guilabel:`Cash Basis Taxes` journal are named using the :guilabel:`CABA` short code." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:31 +msgid "Once this is done, go to :menuselection:`Accounting --> Configuration --> Accounting: Taxes` to configure your taxes. You can either :guilabel:`Create` a new tax or update an existing one by clicking on it." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:35 -msgid "In the *Advanced Options* tab you will turn *Tax Due* to *Based on Payment*. You will then have to define the *Tax Received* account in which to post the tax amount when the payment is received and the *Base Tax Received Account* to post the base tax amount for an accurate tax report." +msgid "The :guilabel:`Account` column reflects the proper transitional accounts to post taxes until the payment is registered." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:45 -msgid "What is the impact of cash basis taxes in my accounting ?" +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:None +msgid "Fill in the account column with a transitional accounts where taxes go until the payment\n" +"is registered" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:47 -msgid "Let’s take an example. You make a sale of $100 with a 15% cash basis tax. When you validate the customer invoice, the following entry is created in your accounting:" +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:43 +msgid "In the :guilabel:`Advanced Options` tab, decide of the :guilabel:`Tax Exigilibity`. Select :guilabel:`Based on Payment`, so the tax is due when the payment of the invoice is received. You can then also define the :guilabel:`Cash Basis Transition Account` where the tax amount is recorded as long as the original invoice has not been reconciled." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:52 -msgid "Customer Invoices Journal" +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:None +msgid "Fill in the Cash Basis Transition Account where taxes amounts go until payment\n" +"reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:54 +msgid "Impact of cash basis taxes on accounting" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:56 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:72 -msgid "Receivables $115" -msgstr "" - -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:58 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:82 -msgid "Temporary Tax Account $15" -msgstr "" - -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:60 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:86 -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:88 -msgid "Income Account $100" +msgid "To illustrate the impact of cash basis taxes on accounting transactions, let's take an example with the sales of a product that costs 1,000$, with a cash basis tax of 15%." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:63 -msgid "A few days later, you receive the payment:" +msgid "The following entries are created in your accounting, and the tax report is currently empty." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:66 -msgid "Bank Journal" +msgid "**Customer journal (INV)**" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:70 -msgid "Bank $115" +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:86 +msgid "Receivable $1,150" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:75 -msgid "When you reconcile the invoice and the payment, this entry is generated:" +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:72 +msgid "Income $1,000" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:78 -msgid "Tax Cash Basis Journal" +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:74 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:103 +msgid "Temporary tax account $150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:77 +msgid "When the payment is then received, it is registered as below :" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:80 +msgid "**Bank journal (BANK)**" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:84 -msgid "Tax Received Account $15" +msgid "Bank $1,150" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:92 -msgid "The last two journal items are neutral but they are needed to insure correct tax reports in Odoo with accurate base tax amounts. We advise to use a default revenue account. The balance of this account will then always be at zero." +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:90 +msgid "Once the payment is registered, you can use the :guilabel:`Cash Basis Entries` smart button on the invoice to access them directly." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:3 -msgid "Default taxes" +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:93 +msgid "Finally, upon reconciliation of the invoice with the payment, the below entry is automatically created:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:97 +msgid "**Tax Cash Basis Journal (Caba)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:101 +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:105 +msgid "Income account $1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:107 +msgid "Tax Received $150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:110 +msgid "The journal items :guilabel:`Income account` vs. :guilabel:`Income account` are neutral, but they are needed to ensure correct tax reports in Odoo with accurate base tax amounts." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst:113 +msgid "Using a default :guilabel:`Base Tax Received Account` is recommended so your balance is at zero and your income account is not polluted by unnecessary accounting movements. To do so, go to :menuselection:`Configuration --> Settings --> Taxes`, and select a :guilabel:`Base Tax Received Account` under :guilabel:`Cash Basis`." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:5 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 +msgid "Odoo fills out the Tax field automatically according to the Default Taxes" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:14 msgid ":doc:`Fiscal Positions ` take the Default Tax into account. Therefore, if a Fiscal Position is applied to an invoice, Odoo applies the related tax instead of the Default Taxes, as mapped in the Fiscal Position." msgstr "" @@ -15568,6 +17060,10 @@ 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 +msgid "Define which taxes to use by default on Odoo" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:34 msgid "Databases with multiple companies: the Default Taxes values are company-specific." msgstr "" @@ -15611,6 +17107,10 @@ 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 +msgid "EU intra-community Distance Selling feature in Odoo Accounting settings" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/eu_distance_selling.rst:41 msgid "Please :ref:`upgrade the module ` `l10n_eu_service` if you already installed it before **July 1, 2021**, or if you activated the feature **EU Digital Goods VAT** in the Accounting settings. Then, make sure to :ref:`refresh the tax mapping `." msgstr "" @@ -15651,6 +17151,10 @@ 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 +msgid "Example: Belgian to Intra-Community tax mapping with Fiscal Positions in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:16 msgid "They can be applied in various ways:" msgstr "" @@ -15719,6 +17223,10 @@ msgstr "" msgid "**Country Group** / **Country**: The Fiscal Position is applied to these countries." msgstr "" +#: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:None +msgid "Example of settings to apply a Fiscal Position automatically" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:65 msgid "Taxes on **eCommerce orders** are automatically updated once the visitor has logged in or filled out their billing details." msgstr "" @@ -15747,6 +17255,11 @@ 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 +msgid "Selection of a Fiscal Position on a Sales Order / Invoice / Bill in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/fiscal_positions.rst:98 msgid "Choose Fiscal Positions manually on Sales Orders, Invoices, and Bills" msgstr "" @@ -15818,131 +17331,163 @@ msgid "The printed invoice will show the different amounts in each tax group." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:3 -msgid "Get correct tax rates in the United States using TaxCloud" +msgid "TaxCloud integration" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:5 -msgid "The **TaxCloud** integration allows you to correctly calculate the sales tax for every address in the United States and keeps track of which products are exempt from sales tax and in which states each exemption applies. TaxCloud calculates sales tax in real-time for every state, city, and special jurisdiction in the United States." +msgid "TaxCloud calculates the sales tax rate in real time for every state, city, and special jurisdiction in the United States. It keeps track of which products are exempt from sales tax and in which states each exemption applies." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:15 -msgid "In TaxCloud" +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:10 +msgid "TaxCloud registration" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:16 -msgid "Create a free account on `TaxCloud `__ website." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:12 +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:18 -msgid "Register your Odoo website on TaxCloud to get an *API ID* and an *API Key*." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +msgid "Example of a store's TaxCloud API Keys" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:21 +msgid "Enable TaxCloud" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:23 -msgid "In Settings on TaxCloud, click *Locations* to enter the location of your Office(s) & Warehouse(s)." +msgid "Go to :menuselection:`Accounting Dashboard --> Configuration --> Settings` and in the :guilabel:`Taxes` section enable :guilabel:`TaxCloud`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:24 -msgid "In Settings on TaxCloud, click *Manage Tax States* to verify the states where you collect sales tax." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:25 +msgid "Add the store's :guilabel:`Login ID` under :guilabel:`API ID` and the store's :guilabel:`Key` under :guilabel:`API KEY`. Click on :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:27 -msgid "In Odoo" -msgstr "" - -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:28 -msgid "Go to :menuselection:`Invoicing / Accounting --> Configuration --> Settings` and check *TaxCloud - Compute tax rates based on U.S. ZIP codes* (note: actually uses complete street address)." +msgid "Click the :guilabel:`Refresh` button (:guilabel:`🗘`) next to :guilabel:`Default Category` to import the TIC :dfn:`Taxability Information Codes` product categories from TaxCloud. Some categories may imply specific tax rates or exemptions." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:30 -msgid "Enter your TaxCloud credentials." +msgid "Select a :guilabel:`Default Category` and :guilabel:`Save`. The :guilabel:`Default Category` is applied when no :guilabel:`TaxCloud Category` is set on your products or product categories, or when no product is found on an order/invoice." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:31 -msgid "Click SAVE to store your credentials." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:0 +msgid "Filling in TaxCloud API Keys in Odoo" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:36 -msgid "Click the Refresh Icon next to *Default Category* to import the TIC product categories from TaxCloud (Taxability Information Codes). Some categories may imply specific rates or attract product/service type exemptions." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:39 +msgid "Set TaxCloud categories on products" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:38 -msgid "Select your default *TIC Code*. This will apply to any new product created." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:41 +msgid "If you need to use more than one TIC category (i.e., the :guilabel:`Default Category`), go to the product's :guilabel:`General Information` tab and select a :guilabel:`TaxCloud Category`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:40 -msgid "Set a specific TaxCloud TIC Category on the *General Information* tab of the Product, or on the Product Category." -msgstr "" - -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:42 -msgid "Make sure your company address is complete (including the state and the zip code). Go to :menuselection:`Settings --> Users & Companies --> Companies` to open and edit your Company record." -msgstr "" - -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:47 -msgid "Automatically post taxes to the correct Tax Payable account" +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:44 +msgid "If you want to configure multiple products simultaneously, ensure they share the same :guilabel:`Product Category` and click on the external link button (:guilabel:`🡕`) to set a :guilabel:`TaxCloud Category` on the :guilabel:`Product Category` instead." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:49 -msgid "For each one of your companies that uses TaxCloud, it might be necessary to create a **User-Defined Default** so that the new taxes generated by the TaxCloud integration are created with the correct Tax Payable account:" +msgid "If you set a :guilabel:`TaxCloud Category` on a product and another on its :guilabel:`Product Category`, Odoo only considers the :guilabel:`TaxCloud Category` found on the product itself." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:54 -msgid "A User-Defined Default impacts all records at creation. It means that **every** new tax will be set up to record income in the specified Tax Payable account, unless the tax is manually edited to specify a different income account (or there exists another User-Defined Default that takes precedence)." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:52 +msgid "A :guilabel:`TaxCloud Category` set on a **parent product category** does not apply to its **child product categories**. For example, if you set :guilabel:`TaxCloud Category` on the *All* :guilabel:`Product Category`, it is not applied to the *All/Sales* :guilabel:`Product Category`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:59 -msgid "In :menuselection:`Accounting --> Configuration --> Chart of Accounts`, select the Tax Payable account for the company. Take note of the account's ``id`` in the URL string." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:57 +msgid "Make sure your company address is complete, including the state and the ZIP code. Go to :menuselection:`Settings --> Companies: Update Info` to open and edit your company address." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:66 -msgid "Activate the :ref:`developer mode `, then go to :menuselection:`Settings --> Technical --> Actions --> User-Defined Defaults`, and click on *Create*." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:61 +msgid "Automatically post taxes in the correct tax payable account" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:70 -msgid "Click on *Field*, then, in the drop-down menu, on *Search More*." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:63 +msgid "To make sure the new taxes generated by the TaxCloud integration are created with the correct **Tax Payable** account, create a **user-defined default**. This process should be repeated for each one of your companies that uses TaxCloud." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:76 -msgid "In the pop-up's search box, filter on the model ``tax.repartition.line`` and the field ``account``. Select the ``account`` field of the ``tax.repartition.line`` model." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:68 +msgid "A user-defined default impacts all records at creation. It means that **every** new tax is set up to record income in the specified Tax Payable account unless the tax is manually edited to specify a different income account (or if another user-defined default takes precedence)." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:83 -msgid "In the **Default Value** field, enter the ID of the company's Tax Payable account. Select the company for which this configuration should apply in the *Company* field. Click *Save*." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:72 +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:93 -msgid "How it works" +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +msgid "Example of Tax Payable account id in the URL string" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:95 -msgid "Salestax is calculated in Odoo based on fiscal positions (see :doc:`fiscal_positions`). A Fiscal Position for the United States is created when installing *TaxCloud*. Everything works out-of-the-box." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:81 +msgid "Activate the :ref:`developer mode `, then go to :menuselection:`Settings --> Technical --> Actions: User-defined Defaults` and click on :guilabel:`Create`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:100 -msgid "You can configure Odoo to automatically detect which Customers should use this fiscal position. Go to :menuselection:`Accounting --> Configuration --> Fiscal Positions` to open and edit the record." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:84 +msgid "Click on :guilabel:`Field` drop-down menu and then on :guilabel:`Search More...`." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:107 -msgid "Now, this fiscal position is automatically set on any sales order, web order, or invoice when the customer country is *United States*. This triggers the automated tax computation." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +msgid "User-defined Defaults Field search" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:90 +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 +msgid "Searching for the Tax Repartition Line model and Account field" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:98 +msgid "Once you are back to the :guilabel:`User-defined Defaults` creation, enter the **Tax Payable account ID** you took note of earlier under the :guilabel:`Default Value (JSON format)` field." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:101 +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 +msgid "Example of a User-defined Defaults configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:109 +msgid "Automatically detect the fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:111 +msgid "Sales taxes are calculated in Odoo based on :doc:`fiscal positions `. A fiscal position for the United States is created when enabling TaxCloud." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:114 -msgid "Add your product(s). You have two options to get Sales Tax on the Order. You can confirm it, or you can save it and from the *Action* Menu choose **Update Taxes with TaxCloud**." +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:119 -msgid "Coupons & Promotions" -msgstr "" - -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:121 -msgid "If you use the Coupon or Promotion Programs, the integration with Taxcloud might seem a bit odd." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:None +msgid "Detect Automatically setting on the TaxCloud fiscal position" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:123 -msgid "The problem lies with the fact that Taxcloud does not accept lines with negative amounts as part of the tax computation. This means that the amount of the lines added by the promotion program must be deduced from the total of the lines it impacts. This means, amongst other complications, that orders that use coupons or promotions with a Taxcloud fiscal position **must** be invoiced completely - you cannot create invoices for partial deliveries, etc." +msgid "Now, this fiscal position is automatically set on any order or invoice if the customer country is *United States*. This triggers the automated tax computation." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:129 -msgid "Another specific oddity is possible in the UI: imagine that you sell a product from the Taxcloud category *[20110] Computers* and that you have a promotion program in place that provides a 50% discount on this product. If the tax rate for this particular product is 7%, the tax rate that will be computed from the Taxcloud integration will display 3.5%. This happens because the discount is included in the price that is sent to Taxcloud, but in Odoo this discount is in another line entirely. At the end of the day, your tax computation will be correct (since a 3.5% tax on the full price is the equivalent of a 7% tax on half the price), but this might be surprising from a user point of view." +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:127 +msgid "To get the sales taxes on a sales order, confirm it or click the :guilabel:`Update Taxes` button next to :guilabel:`Add Shipping`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:131 +msgid "Interaction with coupons and promotions" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:133 +msgid "If you use the **Coupon** or **Promotion Programs**, the integration with TaxCloud might behave unexpectedly. Indeed, as TaxCloud does not accept lines with negative amounts as part of the tax computation, the amount of the lines added by the promotion program must be deduced from the total of the lines it impacts." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:139 +msgid "This means, amongst other complications, that orders using coupons or promotions with a TaxCloud fiscal position **must** be invoiced completely - you cannot create invoices for partial deliveries, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/taxcloud.rst:143 +msgid "Another unexpected behavior is possible. For example, you sell a product for which you have a promotion program that provides a 50% discount. If the product's tax rate is 7%, the tax rate computed from the TaxCloud integration displays 3.5%. This happens because the discount is included in the price sent to TaxCloud. However, in Odoo, the discount is on another line entirely. Still, the tax computation is correct. Indeed, a 3.5% tax on the full price is the equivalent of a 7% tax on half the price, but this might be unexpected from a user point of view." msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:5 @@ -15961,10 +17506,18 @@ 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 +msgid "Activate pre-configured taxes in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:31 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 +msgid "Edition of a tax in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:41 msgid "Taxes have three different labels, each one having a specific use. Refer to the following table to see where they are displayed." msgstr "" @@ -16159,6 +17712,10 @@ 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 +msgid "Allocate tax amounts to the right accounts and tax grids" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:163 msgid "**Based On**:" msgstr "" @@ -16191,6 +17748,10 @@ 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 +msgid "The Label on Invoices is displayed on each invoice line" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:193 msgid "Tax Group" msgstr "" @@ -16203,6 +17764,10 @@ 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 +msgid "The Tax Group name is different from the Label on Invoices" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:205 msgid "In the example above, we see a 0% tax for Intra-Community customers in Europe. It records amounts on specific accounts and with specific tax grids. Still, to the customer, it is a 0% tax. That's why the :ref:`Label on the Invoice ` indicates *0% EU*, and the Tax Group name, above the *Total* line, indicates *0%*." msgstr "" @@ -16267,6 +17832,10 @@ 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 +msgid "The eco-tax is taken into the basis of the 21% VAT tax" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:266 msgid "The order in which you add the taxes on a product line has no effect on how amounts are computed. If you add taxes directly on a product line, only the tax sequence determines the order in which they are applied." msgstr "" @@ -16275,6 +17844,10 @@ msgstr "" msgid "To reorder the sequence, go to :menuselection:`Accounting --> Configuration --> Taxes`, and drag and drop the lines with the handles next to the tax names." msgstr "" +#: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:0 +msgid "The taxes' sequence in Odoo determines which tax is applied first" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:3 msgid "VIES VAT numbers validation" msgstr "" @@ -16291,6 +17864,10 @@ 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 +msgid "Enable \"Verify VAT Numbers\" in Odoo Accounting" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:23 msgid "VAT Number validation" msgstr "" @@ -16299,10 +17876,18 @@ 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 +msgid "Fill out the contact form with the country and VAT number before clicking on *Save*" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:31 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 +msgid "Odoo displays an error message instead of saving when the VAT number is invalid" +msgstr "" + #: ../../content/applications/finance/accounting/taxation/taxes/vat_validation.rst:39 msgid "This tool checks the VAT number's validity but does not check the other fields' validity." msgstr "" @@ -16320,7 +17905,7 @@ msgid "**Odoo Documents** allows you to store, view and manage files within Odoo msgstr "" #: ../../content/applications/finance/documents.rst:7 -msgid "You can upload any type of file (max 64MB per file on Odoo Online/SaaS), and organize them in various workspaces." +msgid "You can upload any type of file (max 64MB per file on Odoo Online), and organize them in various workspaces." msgstr "" #: ../../content/applications/finance/documents.rst:11 @@ -16343,6 +17928,10 @@ 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 +msgid "Workflow actions smart button in Odoo Documents" +msgstr "" + #: ../../content/applications/finance/documents.rst:33 msgid "An action applies to all *Child Workspaces* under the *Parent Workspace* you selected." msgstr "" @@ -16375,6 +17964,10 @@ msgstr "" msgid "**Owner**: the files must be associated with the owner set here." msgstr "" +#: ../../content/applications/finance/documents.rst:None +msgid "Example of a workflow action's basic condition in Odoo Documents" +msgstr "" + #: ../../content/applications/finance/documents.rst:59 msgid "If you don't set any conditions, the action button appears for all files located inside the selected workspace." msgstr "" @@ -16391,14 +17984,26 @@ 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 +msgid "Activating the domain condition type in Odoo Documents" +msgstr "" + #: ../../content/applications/finance/documents.rst:76 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 +msgid "Example of a workflow action's domain condition in Odoo Documents" +msgstr "" + #: ../../content/applications/finance/documents.rst:84 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 +msgid "Add a node or a branch to a workflow action's condition in Odoo Documents" +msgstr "" + #: ../../content/applications/finance/documents.rst:93 msgid "Configure the actions" msgstr "" @@ -16471,6 +18076,10 @@ 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 +msgid "Example of a workflow action Odoo Documents" +msgstr "" + #: ../../content/applications/finance/expenses.rst:5 msgid "Expenses" msgstr "" @@ -16728,6 +18337,10 @@ 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 +msgid "Pay online in the customer portal and select which payment acquirer to use." +msgstr "" + #: ../../content/applications/finance/payment_acquirers.rst:34 msgid "Odoo apps delegate the handling of sensitive information to the certified payment acquirer so that you don't ever have to worry about PCI compliance." msgstr "" @@ -16960,6 +18573,10 @@ msgstr "" msgid "To add a new payment acquirer and make it available to your customers, go to :menuselection:`Accounting --> 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 +msgid "Click on install, then on activate to make the payment acquirer available on Odoo." +msgstr "" + #: ../../content/applications/finance/payment_acquirers.rst:248 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 "" @@ -17033,6 +18650,10 @@ msgstr "" msgid "Leave blank to fallback on the default account, which you can see or change in the settings." msgstr "" +#: ../../content/applications/finance/payment_acquirers.rst:None +msgid "A bank journal in the \"Incoming Payments Tab\"." +msgstr "" + #: ../../content/applications/finance/payment_acquirers.rst:311 msgid "You can have the same bank account for the whole company, or for some journals only, or a single payment method... What best suit your needs." msgstr "" @@ -17157,14 +18778,26 @@ msgstr "" 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 +msgid "Configure a webhook." +msgstr "" + #: ../../content/applications/finance/payment_acquirers/adyen.rst:65 msgid "There, in :menuselection:`General --> Server configuration --> URL`, enter your server address followed by `/payment/adyen/notification`." msgstr "" +#: ../../content/applications/finance/payment_acquirers/adyen.rst:None +msgid "Enter the notification URL." +msgstr "" + #: ../../content/applications/finance/payment_acquirers/adyen.rst:72 msgid "Then enter :menuselection:`Security --> HMAC Key --> Generate`. Be careful to copy the key as you will not be allowed to do it later without generating a new one." msgstr "" +#: ../../content/applications/finance/payment_acquirers/adyen.rst:None +msgid "Generate a HMAC key and save it." +msgstr "" + #: ../../content/applications/finance/payment_acquirers/adyen.rst:79 msgid "You have to save the webhook to finalize its creation." msgstr "" @@ -17177,6 +18810,10 @@ msgstr "" msgid "To retrieve the URLs, log into your Adyen account, go to :menuselection:`Developers --> API URLs`. Select one of the URLs listed next to :guilabel:`Classic Recurring API` as your :guilabel:`Recurring API URL` and one listed next to :guilabel:`Checkout API` as your :guilabel:`Checkout API URL`." msgstr "" +#: ../../content/applications/finance/payment_acquirers/adyen.rst:None +msgid "Get the links for the different API." +msgstr "" + #: ../../content/applications/finance/payment_acquirers/adyen.rst:96 msgid "Adyen Account" msgstr "" @@ -17189,6 +18826,10 @@ msgstr "" msgid "To allow payment originated from your website, follow the steps in :ref:`adyen/api_and_client_keys` to navigate to your API user and go to :menuselection:`Add allowed origins`, then add the URLs from where payments will be made (the URLs of the servers hosting your Odoo instances)." msgstr "" +#: ../../content/applications/finance/payment_acquirers/adyen.rst:None +msgid "Allows payments originated from a specific domain." +msgstr "" + #: ../../content/applications/finance/payment_acquirers/adyen.rst:112 #: ../../content/applications/finance/payment_acquirers/alipay.rst:36 #: ../../content/applications/finance/payment_acquirers/authorize.rst:53 @@ -17430,7 +19071,7 @@ msgid "Ogone must now be configured to accept payments from Odoo. Head to :menus msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:52 -msgid "If you need to use another algorithm, such as `sha-256` or `sha-512`, within Odoo, activate the :ref:`developer mode ` and go to :menuselection:`General Settings --> Technical --> System Parameters`. From here, search for `payment_ogone.hash.function` and change the value line to the desired algorithm (`sha-256` or `sha-512`)." +msgid "If you need to use another algorithm, such as `sha-256` or `sha-512`, within Odoo, activate the :ref:`developer mode ` and go to :menuselection:`General Settings --> Technical --> System Parameters`. From here, search for `payment_ogone.hash_function` and change the value line to the desired algorithm (`sha-256` or `sha-512`)." msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:57 @@ -17877,6 +19518,10 @@ 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 +msgid "Select and add icons of the payment methods you want to enable" +msgstr "" + #: ../../content/applications/finance/payment_acquirers/stripe.rst:129 msgid "If a payment icon record does not exist in the database and its related local payment method is listed above, it is considered enabled with Stripe." msgstr "" @@ -18065,6 +19710,10 @@ msgstr "" msgid "Users can freely edit auto-completed fields." msgstr "" +#: ../../content/applications/finance/sign.rst:None +msgid "Company field example in Odoo Sign" +msgstr "" + #: ../../content/applications/finance/sign.rst:110 msgid "You can then change the size of the field by editing the *Default Width* and *Default Height*. Both sizes are defined as a percentage of the full-page expressed as a decimal, with 1 equalling the full-page's width or height. By default, the width of new fields you create is set to 15% (0.150) of a full-page's width, while their height is set to 1.5% (0.015) of a full-page's height." msgstr "" @@ -18072,3 +19721,7 @@ msgstr "" #: ../../content/applications/finance/sign.rst:115 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 +msgid "Tip and placeholder example in Odoo Sign" +msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 91f60d2c1..8c6c02efb 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -32,6 +32,10 @@ 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 +msgid "Add \"Extra\" filter in Odoo Apps" +msgstr "" + #: ../../content/applications/general/apps_modules.rst:16 msgid "Odoo is *not a smartphone*, and its apps shouldn't be installed or uninstalled carelessly. Apply caution when adding or removing apps and modules on your database since this may impact your subscription costs." msgstr "" @@ -254,6 +258,10 @@ msgstr "" 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*." 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." msgstr "" @@ -266,10 +274,18 @@ msgstr "" 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" +msgstr "" + #: ../../content/applications/general/auth/google.rst:45 msgid "Choose one of the options **(Internal / External)** as instructed, and click on *Create*." msgstr "" +#: ../../content/applications/general/auth/google.rst:0 +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*." msgstr "" @@ -286,10 +302,18 @@ msgstr "" msgid "On the left side menu, click on :menuselection:`Credentials`." msgstr "" +#: ../../content/applications/general/auth/google.rst:0 +msgid "Credentials button menu" +msgstr "" + #: ../../content/applications/general/auth/google.rst:65 msgid "Click on *Create Credentials* and select **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 "" @@ -298,6 +322,10 @@ msgstr "" 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" msgstr "" @@ -310,6 +338,10 @@ msgstr "" 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*." 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" msgstr "" @@ -326,6 +358,10 @@ msgstr "" 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*." msgstr "" +#: ../../content/applications/general/auth/google.rst:0 +msgid "Filling out the client id in Odoo settings" +msgstr "" + #: ../../content/applications/general/auth/google.rst:121 msgid "Log in to Odoo with Google" msgstr "" @@ -334,6 +370,10 @@ msgstr "" 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." 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: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." msgstr "" @@ -418,6 +458,10 @@ msgstr "" 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 "" @@ -426,10 +470,18 @@ msgstr "" 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 "" @@ -442,6 +494,10 @@ msgstr "" 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 "" @@ -462,6 +518,10 @@ msgstr "" 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 "" @@ -478,6 +538,10 @@ msgstr "" 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 "" @@ -486,6 +550,10 @@ msgstr "" 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 Calender API Credentials page into their respective fields below the :guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`." msgstr "" @@ -494,14 +562,26 @@ msgstr "" 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 "Synchronization with Outlook's Calendar" msgstr "" @@ -530,10 +610,18 @@ msgstr "" msgid "When configuring your platform settings, choose *Web*." msgstr "" +#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0 +msgid "Adding a platform in Microsoft Azure for Outlook calendar sync in Odoo" +msgstr "" + #: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0 msgid "For the **Redirect URI restrictions**, copy your Odoo database URI followed by ``/microsoft_account/authentication``. Example:" msgstr "" +#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0 +msgid "Odoo's database URI that is accepted when microsoft returns authentication" +msgstr "" + #: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0 msgid "For more information on the restrictions and limitations of URIs, `check this page `_." msgstr "" @@ -550,14 +638,26 @@ msgstr "" msgid "Go to general *Settings* and activate the *Outlook Calendar* feature." msgstr "" +#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None +msgid "Outlook Calendar feature activated in Odoo" +msgstr "" + #: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:50 msgid "From your Azure portal, under *Overview*, copy your *Application (client) ID*, and paste it to *Client ID* in Odoo." msgstr "" +#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None +msgid "Client ID token to be copied from Microsoft to Odoo" +msgstr "" + #: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:57 msgid "Going back to your Azure portal, now under *Certificates & secrets*, copy your *Client Secret Value* and paste it to *Client Secret* in Odoo." msgstr "" +#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None +msgid "Client Secret token to be copied from Microsoft to Odoo" +msgstr "" + #: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:67 msgid "Sync with Outlook" msgstr "" @@ -570,14 +670,26 @@ msgstr "" msgid "To avoid this situation, we recommend *archiving all past events, and removing yourself from future ones in Odoo Calendar before the first sync*. This will prevent events from being created in Outlook, and therefore, no redundant emails will be sent during the first synchronization. After the sync, events will only send one confirmation email." msgstr "" +#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0 +msgid "Archive events in Odoo Calendar" +msgstr "" + #: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:82 msgid "Go to the *Calendar* application and *Sync with Outlook*. You are asked to log in to your account, if you are not already, and grant the required permissions." msgstr "" +#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:None +msgid "Calendar view and the button Sync with Outlook in Odoo Calendar" +msgstr "" + #: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:89 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:None +msgid "View of Odoo's Calendar synched with Outlook's Calendar" +msgstr "" + #: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:97 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' are unique, and represent an organization that helps you to manage a specific instance of Microsoft cloud services for your internal and external users." msgstr "" @@ -606,6 +718,10 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Activate the developer mode`." msgstr "" +#: ../../content/applications/general/developer_mode.rst:None +msgid "Overview of the debug options under settings in Odoo" +msgstr "" + #: ../../content/applications/general/developer_mode.rst:19 msgid "*Activate the developer mode (with assets)* is used by developers; *Activate the developer mode (with tests assets)* is used by developers and testers." msgstr "" @@ -626,6 +742,10 @@ 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 +msgid "View of odoo’s debug icon in a chrome’s toolbar" +msgstr "" + #: ../../content/applications/general/developer_mode.rst:37 msgid "Activate through the command palette" msgstr "" @@ -634,6 +754,10 @@ msgstr "" msgid "The command palette tool has a command to activate the debug mode: open it with the keyboard shortcut `ctrl+k`, then type `debug`: a command will show up to activate the debug mode." msgstr "" +#: ../../content/applications/general/developer_mode.rst:None +msgid "Command palette with debug command" +msgstr "" + #: ../../content/applications/general/developer_mode.rst:48 msgid "Activate through the URL" msgstr "" @@ -642,38 +766,46 @@ msgstr "" msgid "In the URL, add ``?debug=1`` or ``?debug=true`` after *web*. To deactivate the debug mode, add `?debug=0` instead." msgstr "" +#: ../../content/applications/general/developer_mode.rst:None +msgid "Overview of an url with the debug mode command added in Odoo" +msgstr "" + #: ../../content/applications/general/developer_mode.rst:58 msgid "Additional modes are available for developers: `?debug=assets` enables the :ref:`assets mode `, and `?debug=tests` enables the :ref:`tests mode `." msgstr "" -#: ../../content/applications/general/developer_mode.rst:63 +#: ../../content/applications/general/developer_mode.rst:65 msgid "Locate the mode tools" msgstr "" -#: ../../content/applications/general/developer_mode.rst:65 +#: ../../content/applications/general/developer_mode.rst:67 msgid "The Developer mode tools can be accessed from the *Open Developer Tools* button, located on the header of your pages. This menu contains additional tools that are useful to understand or edit technical data, such as the views or the actions. It contains some useful menu items such as:" msgstr "" -#: ../../content/applications/general/developer_mode.rst:70 +#: ../../content/applications/general/developer_mode.rst:72 msgid "edit action" msgstr "" -#: ../../content/applications/general/developer_mode.rst:71 +#: ../../content/applications/general/developer_mode.rst:73 msgid "manage filters" msgstr "" -#: ../../content/applications/general/developer_mode.rst:72 +#: ../../content/applications/general/developer_mode.rst:74 msgid "edit the current view" msgstr "" -#: ../../content/applications/general/developer_mode.rst:73 +#: ../../content/applications/general/developer_mode.rst:75 msgid "see the `fields view get`" msgstr "" -#: ../../content/applications/general/developer_mode.rst:74 +#: ../../content/applications/general/developer_mode.rst:76 msgid "and much more." msgstr "" +#: ../../content/applications/general/developer_mode.rst:None +msgid "Overview of a console page and the debug icon being shown in Odoo" +msgstr "" + #: ../../content/applications/general/digest_emails.rst:3 msgid "Digest Emails" msgstr "" @@ -686,6 +818,10 @@ msgstr "" msgid "Navigate to Digest Emails by going to :menuselection:`Settings --> General Settings --> Statistics`, then activate the **Digest Emails** feature and click on save." msgstr "" +#: ../../content/applications/general/digest_emails.rst:None +msgid "Digest Emails section inside General Settings." +msgstr "" + #: ../../content/applications/general/digest_emails.rst:15 msgid "You can control a variety of settings for your Digest Emails, such as:" msgstr "" @@ -746,6 +882,10 @@ msgstr "" msgid "**Custom** - add your own KPIs (Studio required)" msgstr "" +#: ../../content/applications/general/digest_emails.rst:None +msgid "Customize default Digest Email settings and custom KPIs." +msgstr "" + #: ../../content/applications/general/digest_emails.rst:52 msgid "Custom digest emails" msgstr "" @@ -1135,260 +1275,251 @@ msgid "You access the **System Parameters** in :ref:`developer mode `_ & `Odoo.sh `_." +#: ../../content/applications/general/email_communication/email_servers.rst:17 +msgid "This document is **mainly dedicated to Odoo on-premise users** who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online `_ and `Odoo.sh `_." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:24 -msgid "If no one in your company is used to manage email servers, we strongly recommend that you opt for those Odoo hosting solutions. Their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server's reputation yourself." +#: ../../content/applications/general/email_communication/email_servers.rst:21 +msgid "The following sections below contain information on how to integrate an external email server with Odoo." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:30 -msgid "You will find here some useful information on how to integrate your own email solution with Odoo." +#: ../../content/applications/general/email_communication/email_servers.rst:25 +msgid "If no one in the company is used to managing email servers, Odoo Online and Odoo.sh are strongly recommended. Those Odoo hosting types' email systems work instantly and are monitored by professionals. Nevertheless, a company can use their own email server if they want to manage the email server's reputation themselves." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:34 -msgid "Office 365 email servers don't easily allow to send external emails from hosts like Odoo. Refer to `Microsoft's documentation `_ to make it work." +#: ../../content/applications/general/email_communication/email_servers.rst:31 +msgid "Office 365 email servers don't easily allow the sending of external emails from hosts like Odoo. Refer to `Microsoft's documentation `_ to make it work." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:37 +msgid "Manage outbound messages" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:39 -msgid "How to manage outbound messages" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:40 -msgid "As a system admin, go to :menuselection:`Settings --> General Settings` and check *External Email Servers*. Then, click *Outgoing Mail Servers* to create one and reference the SMTP data of your email server. Once all the information has been filled out, click on *Test Connection*." +msgid "As a system admin, go to :menuselection:`Settings --> General Settings --> Discuss` in Odoo, and enable the :guilabel:`External Email Servers` option. Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers` and click :guilabel:`Create` to create a new outgoing mail server record in Odoo. Reference the SMTP data of the external email server. Once all the information has been filled out, click :guilabel:`Test Connection`." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:45 msgid "Here is a typical configuration for a G Suite server." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:50 -msgid "Then set your email domain name in the General Settings." +#: ../../content/applications/general/email_communication/email_servers.rst:None +msgid "The typical G Suite configuration on Odoo." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:53 -msgid "If you get a ``[AUTHENTICATIONFAILED] Invalid credentials (Failure)`` warning when you *Test Connection* on a Gmail address, activate the *Less secure app access* option. A direct link can be `accessed here `_." +#: ../../content/applications/general/email_communication/email_servers.rst:51 +msgid "Then, go back to :menuselection:`Settings --> General Settings --> Discuss` and set the email domain name in the :guilabel:`Alias Domain` name. Finally, click :guilabel:`Save` to finish setting up the email server." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:57 -msgid "In addition to that, enable the IMAP setting on your Gmail account." +#: ../../content/applications/general/email_communication/email_servers.rst:56 +msgid "If an `[AUTHENTICATION FAILED] Invalid credentials (Failure)` warning appears when :guilabel:`Test Connection` is clicked for a Gmail address, activate the :guilabel:`Less secure app access` option. A direct link can be `accessed here `_." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:61 -msgid "Can I use an Office 365 server" +msgid "In addition to that, enable the :guilabel:`IMAP setting` on the Gmail account." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:62 -msgid "You can use an Office 365 server if you run Odoo on-premise. Office 365 SMTP relays are not compatible with Odoo Online unless you configure Odoo to :ref:`force the outgoing \"From\" address ` ." +#: ../../content/applications/general/email_communication/email_servers.rst:64 +msgid "Use an Office 365 server" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:66 -msgid "Please refer to `Microsoft's documentation `_ to configure a SMTP relay for your Odoo's IP address." +msgid "An Office 365 server can be used if the database's hosting type is **Odoo on-premise**. Office 365 SMTP relays are not compatible with Odoo Online or Odoo.sh unless Odoo is configured to :ref:`force the outgoing \"From\" address `." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:71 -msgid "How to use a G Suite server" +#: ../../content/applications/general/email_communication/email_servers.rst:70 +msgid "Please refer to `Microsoft's documentation `_ to configure an SMTP relay for the Odoo database's IP address." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:72 -msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to setup the SMTP relay service. The configuration steps are explained in `Google documentation `__." +#: ../../content/applications/general/email_communication/email_servers.rst:75 +msgid "Use a G Suite server" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:77 +msgid "A G Suite server can be used for any Odoo hosting type. To do so, set up the SMTP relay service. The configuration steps are explained in `Google documentation `__." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:82 msgid "Restriction" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:78 -msgid "Please note that port 25 is blocked for security reasons on our SaaS and Odoo.sh platform. Try using 465, 587, or 2525." +#: ../../content/applications/general/email_communication/email_servers.rst:84 +msgid "Please note that port 25 is blocked for security reasons on Odoo Online and Odoo.sh platforms. Try using ports 465, 587, or 2525 instead." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:84 +#: ../../content/applications/general/email_communication/email_servers.rst:90 msgid "Use a default \"From\" email address" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:86 +#: ../../content/applications/general/email_communication/email_servers.rst:92 msgid "Sometimes, an email's \"From\" (outgoing) address can belong to a different domain, and that can be a problem." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:89 -msgid "For example, if a customer with address *mary@customer.example.com* responds to a message, Odoo will try to redistribute that same email to other subscribers in the thread. But if the domain *customer.example.com* forbids that kind of usage for security, the Odoo's redistributed email would get rejected by some recipients' mail servers." -msgstr "" - #: ../../content/applications/general/email_communication/email_servers.rst:95 -msgid "To avoid those kind of problems, you should make sure all emails use a \"From\" address from your authorized domain." +msgid "For example, if a customer with the email address *mary\\@customer.example.com* responds to a message, Odoo will try to redistribute that same email to the other subscribers in the thread. However, if the domain *customer.example.com* forbids that kind of usage for security, the email that Odoo is trying to redistribute would get rejected by some recipients' email servers." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:98 -msgid "If your MTA supports `SRS (Sender Rewriting Scheme) `_, you can enable it to handle these situations. However, that is more complex and requires more technical knowledge that is not meant to be covered by this documentation." +#: ../../content/applications/general/email_communication/email_servers.rst:100 +msgid "To avoid that problem, make sure all emails use a \"From\" address from the same authorized domain." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:103 -msgid "Instead, you can also configure Odoo to do something similar by itself:" +#: ../../content/applications/general/email_communication/email_servers.rst:102 +msgid "If the MTA supports `SRS (Sender Rewriting Scheme) `_, SRS can be enabled to handle these situations. However, that is more complex and requires more technical knowledge that is not meant to be covered by this documentation." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:105 -#: ../../content/applications/general/email_communication/email_servers.rst:177 -msgid "Set your domain name in the General Settings." +#: ../../content/applications/general/email_communication/email_servers.rst:106 +msgid "Instead, Odoo can be configured to do something similar by itself:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:110 -msgid "Click on *Outgoing Mail Servers*" +#: ../../content/applications/general/email_communication/email_servers.rst:108 +msgid "Set the :guilabel:`Alias Domain` name in the :menuselection:`Settings --> General Settings --> Discuss`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:112 -msgid "Create a new one." +#: ../../content/applications/general/email_communication/email_servers.rst:0 +msgid "Setting the domain alias configuration on Odoo." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:114 -msgid "Fill its *From Filter*." +msgid "Turn on :doc:`developer mode `." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:119 -msgid "Use a domain (such as ``mycompany.example.com``) to keep the original \"From\" address for mails that come from that domain." +#: ../../content/applications/general/email_communication/email_servers.rst:115 +msgid "Go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:122 -msgid "Use an address (such as ``outgoing@mycompany.example.com``) to allow only that outgoing address." +#: ../../content/applications/general/email_communication/email_servers.rst:116 +msgid "Add one system parameter from the following list:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:125 -msgid "Keep it empty to use this server for any email address." +#: ../../content/applications/general/email_communication/email_servers.rst:118 +msgid "To use the same \"From\" address for *all* outgoing messages, use the key `mail.force.smtp.from` and set that address as value (such as `outgoing@mycompany.example.com`)." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:127 -msgid "With this configuration in place, if Odoo sends an email that doesn't match any of the *from filters*, it will alter the email's \"From\" before sending it to the MTA." +#: ../../content/applications/general/email_communication/email_servers.rst:120 +msgid "To keep the original \"From\" address for emails that use the same domain, but change it for emails that use a different domain, use the key `mail.dynamic.smtp.from` and set the value as the email address that should be used in those cases (such as `outgoing@mycompany.example.com` )." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:131 -msgid "It will use the default outgoing email address, composed like this: ``{mail.default.from}@{mail.catchall.domain}``." +#: ../../content/applications/general/email_communication/email_servers.rst:128 +msgid "Manage inbound messages" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:134 -msgid "In developer mode, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:137 -msgid "Add these system parameters:" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:139 -msgid "``mail.default.from``: local part of default outgoing email address." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:141 -msgid "``mail.catchall.domain``: domain part of default outgoing email address." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:146 -msgid "How to manage inbound messages" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:148 +#: ../../content/applications/general/email_communication/email_servers.rst:130 msgid "Odoo relies on generic email aliases to fetch incoming messages." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:150 +#: ../../content/applications/general/email_communication/email_servers.rst:132 msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:154 +#: ../../content/applications/general/email_communication/email_servers.rst:134 msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing `__ to opt-out invalid recipients." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:158 +#: ../../content/applications/general/email_communication/email_servers.rst:137 msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:161 +#: ../../content/applications/general/email_communication/email_servers.rst:140 msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM `__)," msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:163 +#: ../../content/applications/general/email_communication/email_servers.rst:141 msgid "Support Channel (to create Tickets in `Odoo Helpdesk `__)," msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:165 -msgid "Projects (to create new Tasks in `Odoo Project `__)," +#: ../../content/applications/general/email_communication/email_servers.rst:142 +msgid "Projects (to create new Tasks in `Odoo Project `__)," msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:167 -msgid "Job Positions (to create Applicants in `Odoo Recruitment `__)," +#: ../../content/applications/general/email_communication/email_servers.rst:144 +msgid "Job Positions (to create Applicants in `Odoo Recruitment `__)," msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:169 +#: ../../content/applications/general/email_communication/email_servers.rst:146 msgid "etc." msgstr "" +#: ../../content/applications/general/email_communication/email_servers.rst:148 +msgid "Depending on the mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in the mail server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:151 +msgid "Create the corresponding email addresses in the mail server (catchall@, bounce@, sales@, etc.)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:152 +msgid "Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> General Settings --> Discuss`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:155 +msgid "If the database's hosting type is Odoo on-premise, create an :guilabel:`Incoming Mail Server` in Odoo for each alias. This can be done from the General Settings as well. Fill out the form according to the email provider's settings. Leave the :guilabel:`Actions to Perform on Incoming Mails` field blank. Once all the information has been filled out, click on :guilabel:`TEST & CONFIRM`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:0 +msgid "Incoming mail server configuration on Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:165 +msgid "If the database's hosting type is Odoo Online or Odoo.sh, redirecting incoming messages to Odoo's domain name instead of the external email server is recommended. That way, incoming messages can be received without delay. Odoo Online only fetches incoming messages of external servers once every hour. Redirections for all email addresses should be set to Odoo's domain name in the email server (e.g. *catchall\\@mydomain.ext* to *catchall\\@mycompany.odoo.com*)." +msgstr "" + #: ../../content/applications/general/email_communication/email_servers.rst:171 -msgid "Depending on your mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in your mail server." +msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:175 -msgid "Create the corresponding email addresses in your mail server (catchall@, bounce@, sales@, etc.)." +msgid "To edit catchall and bounce aliases, first activate the :ref:`developer mode `. Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & *mail.bounce.alias*)." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:182 -msgid "If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for each alias. You can do it from the General Settings as well. Fill out the form according to your email provider’s settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*." +#: ../../content/applications/general/email_communication/email_servers.rst:0 +msgid "System parameters with catchall configuration in Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:183 +msgid "By default, inbound messages are fetched every 5 minutes in Odoo on-premise." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:186 +msgid "This value can be changed in :ref:`developer mode `. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for :guilabel:`Mail: Fetchmail Service`." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:191 -msgid "If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming messages to Odoo's domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, Odoo Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to Odoo's domain name in your email server (e.g. *catchall@mydomain.ext* to *catchall@mycompany.odoo.com*)." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:201 -msgid "All the aliases are customizable in Odoo." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:199 -msgid "Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the :ref:`developer mode `." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:203 -msgid "Then go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:209 -msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in :ref:`developer mode `. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:216 msgid "Set up different dedicated servers for transactional and mass mails" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:218 -msgid "Odoo is subject to a :ref:`daily email limit ` to prevent abuse. However, if needed, you can use a separate Mail Transfer Agent (MTA) servers for transactional e-mails and mass mailings. Example: use Odoo's own mail server for transactional e-mails, and Sendgrid, Amazon SES, or Mailgun for mass mailings. Another alternative is to use Postmark for transactional e-mails, and Amazon SES or Sendgrid for mass mailings." +#: ../../content/applications/general/email_communication/email_servers.rst:193 +msgid "In Odoo a separate Mail Transfer Agent (MTA) server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun or Sendgrid for mass mailings." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:226 -msgid "A default outgoing email server is already configured. You should not create an alternative one unless you want to use a specific external outgoing email server for technical reasons." +#: ../../content/applications/general/email_communication/email_servers.rst:198 +msgid "A default outgoing email server is already configured. Do not create an alternative one unless a specific external outgoing email server is needed for technical reasons." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:229 -msgid "To do this, you should first activate the :ref:`developer mode ` and then go to :menuselection:`Settings --> Technical --> Outgoing` e-mail servers. There you have to create two e-mail MTA server settings. One for transactional e-mails and one for mass mail servers. Be sure to mark the priority of transactional e-mail servers as low as the mass email servers." +#: ../../content/applications/general/email_communication/email_servers.rst:201 +msgid "To do this, first activate the :ref:`developer mode `, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two email MTA server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional MTA server." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:234 -msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable *Dedicated Server*. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, you have to set your domain's Sender Policy Framework (SPF) records to include both transactional and mass mail servers. If your server resides with xxxx.odoo.com, the available options are Sendinblue and Mailchimp, as your e-mails would be originated from the xxxx.odoo.com domain." +#: ../../content/applications/general/email_communication/email_servers.rst:207 +msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable :guilabel:`Dedicated Server`. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, the domain's Sender Policy Framework (SPF) records must be set to include both transactional and mass mail servers." msgstr "" #: ../../content/applications/general/email_communication/email_template.rst:3 @@ -1411,10 +1542,18 @@ 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 +msgid "Composer in mass mailing mode after selecting multiple quotations." +msgstr "" + #: ../../content/applications/general/email_communication/email_template.rst:28 msgid "You can also define them by default on the template:" msgstr "" +#: ../../content/applications/general/email_communication/email_template.rst:None +msgid "Reply-to field on template." +msgstr "" + #: ../../content/applications/general/email_communication/email_template.rst:34 msgid "Because of this, setting a value in this field is useless as the value defined will be totally ignored. The default *reply-to* value is the default catchall email address to ensure a communication between your customer and your Odoo database. For more information about the way the catchall works, please check :ref:`how to manage inbound messages `." msgstr "" @@ -1475,10 +1614,18 @@ msgstr "" msgid "Click on the edit button, then on the language button" msgstr "" +#: ../../content/applications/general/email_communication/email_template.rst:0 +msgid "Edit the language of a template" +msgstr "" + #: ../../content/applications/general/email_communication/email_template.rst:92 msgid "A pop-up window with the different languages installed on the database will be displayed. From here, editing the translations will be possible. Don't forget to hit the save button to preserve your changes." msgstr "" +#: ../../content/applications/general/email_communication/email_template.rst:0 +msgid "Translation of the body of the Application template in the different languages installed." +msgstr "" + #: ../../content/applications/general/email_communication/faq.rst:3 msgid "FAQ" msgstr "" @@ -1503,6 +1650,10 @@ 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 +msgid "Red envelope displayed in chatter" +msgstr "" + #: ../../content/applications/general/email_communication/faq.rst:26 msgid "Common error messages" msgstr "" @@ -1511,6 +1662,10 @@ msgstr "" msgid "You reached your daily limit:" msgstr "" +#: ../../content/applications/general/email_communication/faq.rst:None +msgid "Warning in Odoo upon email limit reached" +msgstr "" + #: ../../content/applications/general/email_communication/faq.rst:37 msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, and sometimes even per minute. This is the same for Odoo, we have to limit our customers to prevent our e-mail servers from being blacklisted." msgstr "" @@ -1559,6 +1714,10 @@ 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 +msgid "Retry button of an emails" +msgstr "" + #: ../../content/applications/general/email_communication/faq.rst:70 msgid "The daily limit is global to your database and can rise quickly! By default an internal message, a notification, a note, etc. counts as an email in your daily limit if it notifies someone." msgstr "" @@ -1603,6 +1762,10 @@ 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 +msgid "Email scheduled to be sent later." +msgstr "" + #: ../../content/applications/general/email_communication/faq.rst:113 msgid "By default, the Mass Mailing cron runs every 60 minutes. So, you should wait maximum an hour before the campaign is actually sent." msgstr "" @@ -1632,7 +1795,7 @@ msgid "The folder :file:`~/logs/` (preferably accessed by the command line) of a msgstr "" #: ../../content/applications/general/email_communication/faq.rst:138 -msgid "The **SaaS** users won’t have access to their logs. However you can still contact `Odoo Support `_ , if you have a recurring issue with the same client or domain." +msgid "**Odoo Online** users won’t have access to their logs. However you can still contact `Odoo Support `_ , if you have a recurring issue with the same client or domain." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:143 @@ -1699,10 +1862,18 @@ 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 +msgid "view of the different things to enable/click to export data" +msgstr "" + #: ../../content/applications/general/export_import_data.rst:22 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 +msgid "overview of all the options to take into account when exporting data in Odoo" +msgstr "" + #: ../../content/applications/general/export_import_data.rst:30 msgid "With the *I want to update data* option ticked, the system only shows the fields which can be imported. This is very helpful in case you want to update existing records. Basically, this works like a filter. Leaving the box unticked gives way more field options because it shows all the fields, not just the ones which can be imported." msgstr "" @@ -2149,7 +2320,7 @@ msgid "Each IAP Service relies on prepaid credits to work and has its own pricin msgstr "" #: ../../content/applications/general/in_app_purchase.rst:19 -msgid "If I am on Odoo Online (SAAS) and have the Enterprise version, I benefit from free credits to test our IAP features." +msgid "If I am on Odoo Online and have the Enterprise version, I benefit from free credits to test our IAP features." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:23 @@ -2185,7 +2356,7 @@ msgid "Different services are available depending on the hosting type of your Da msgstr "" #: ../../content/applications/general/in_app_purchase.rst:60 -msgid "*Odoo Online (SAAS)*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);" +msgid "*Odoo Online*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:62 @@ -2228,10 +2399,18 @@ 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 +msgid "View of a group’s form emphasizing the tab users in Odoo" +msgstr "" + #: ../../content/applications/general/users/access_rights.rst:22 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 +msgid "View of a group’s form emphasizing the tab inherited in Odoo" +msgstr "" + #: ../../content/applications/general/users/access_rights.rst:32 msgid "Remember to always test the settings being changed in order to ensure that they are being applied to the needed and right users." msgstr "" @@ -2240,6 +2419,10 @@ 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 +msgid "View of a group’s form emphasizing the tab menus in Odoo" +msgstr "" + #: ../../content/applications/general/users/access_rights.rst:42 msgid "*Access Rights* rules are the first level of rights. The field is composed of the object name, which is the technical name given to a model. For each model, enable the following options as appropriate:" msgstr "" @@ -2260,6 +2443,10 @@ msgstr "" msgid "*Delete*: the values of that object can be deleted by the user." msgstr "" +#: ../../content/applications/general/users/access_rights.rst:None +msgid "View of a group’s form emphasizing the tab access rights in Odoo" +msgstr "" + #: ../../content/applications/general/users/access_rights.rst:55 msgid "As a second layer of editing and visibility rules, *Record Rules* can be formed. They overwrite, or refine, the *Access Rights*." msgstr "" @@ -2268,6 +2455,10 @@ 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 +msgid "View of a group’s form emphasizing the tab record rules in Odoo" +msgstr "" + #: ../../content/applications/general/users/access_rights.rst:65 msgid "Making changes in access rights can have a big impact on the database. For this reason, we recommend you to contact your Odoo Business Analyst or our Support Team, unless you have knowledge about Domains in Odoo." msgstr "" @@ -2288,14 +2479,26 @@ 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 +msgid "Overview of a new company's form in Odoo" +msgstr "" + #: ../../content/applications/general/users/companies.rst:22 msgid "Activate the :ref:`developer mode ` to choose a *Favicon* for each of your companies, and easily identify them by the browser tabs. Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and ICO are extensions accepted." msgstr "" +#: ../../content/applications/general/users/companies.rst:0 +msgid "View of a web browser and the favicon for a specific company chosen in Odoo" +msgstr "" + #: ../../content/applications/general/users/companies.rst:31 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 +msgid "View of the companies menu through the main dashboard in Odoo" +msgstr "" + #: ../../content/applications/general/users/companies.rst:40 msgid "Data such as Products, Contacts, and Equipment can be shared or set to be shown for a specific company only. To do so, on their forms, choose between:" msgstr "" @@ -2308,6 +2511,10 @@ 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 +msgid "View of a product's form emphasizing the company field in Odoo Sales" +msgstr "" + #: ../../content/applications/general/users/companies.rst:51 msgid "Employees' access" msgstr "" @@ -2316,6 +2523,11 @@ msgstr "" msgid "Once companies are created, manage your employees' :doc:`Access Rights ` for *Multi Companies*." msgstr "" +#: ../../content/applications/general/users/companies.rst:None +msgid "View of an user form emphasizing the multi companies field under the access rights tabs\n" +"in Odoo" +msgstr "" + #: ../../content/applications/general/users/companies.rst:62 msgid "If a user has multiple companies *activated* on his database, and he is **editing** a record, the editing happens on the record's related company." msgstr "" @@ -2348,6 +2560,10 @@ 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 +msgid "View of the settings page emphasizing the document layout field in Odoo" +msgstr "" + #: ../../content/applications/general/users/companies.rst:83 msgid "Inter-Company Transactions" msgstr "" @@ -2384,6 +2600,10 @@ 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 +msgid "View of the settings page emphasizing the inter company transaction field in Odoo" +msgstr "" + #: ../../content/applications/general/users/companies.rst:104 msgid "**Synchronize invoice/bills**: generates a bill/invoice when a company confirms a bill/invoice for the selected company." msgstr "" @@ -2392,6 +2612,10 @@ 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 +msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo" +msgstr "" + #: ../../content/applications/general/users/companies.rst:114 msgid "**Synchronize sales/purchase order**: generates a drafted purchase/sales order using the selected company warehouse when a sales/purchase order is confirmed for the selected company. If instead of a drafted purchase/sales order you rather have it validated, enable *Automatic Validation*." msgstr "" @@ -2400,6 +2624,10 @@ 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 +msgid "View of the purchase created on JS Store US from JS Store Belgium in Odoo" +msgstr "" + #: ../../content/applications/general/users/companies.rst:127 msgid "Products have to be configured as *Can be sold* and must be shared between the companies." msgstr "" @@ -2413,7 +2641,7 @@ msgid ":doc:`Multi-company Guidelines `" msgstr "" #: ../../content/applications/general/users/companies.rst:134 -msgid ":doc:`../../finance/accounting/others/multicurrencies/how_it_works`" +msgid ":doc:`../../finance/accounting/others/multi_currency`" msgstr "" #: ../../content/applications/general/users/language.rst:3 @@ -2496,6 +2724,10 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Manage Users` and click on *Create*." msgstr "" +#: ../../content/applications/general/users/manage_users.rst:None +msgid "View of the settings page emphasizing the manage users field in Odoo" +msgstr "" + #: ../../content/applications/general/users/manage_users.rst:27 msgid "Fill in the form with the needed information. Under the tab :doc:`Access Rights ` choose the group within each application the user can have access to." msgstr "" @@ -2504,10 +2736,18 @@ 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 +msgid "View of a user’s form emphasizing the access rights tab in Odoo" +msgstr "" + #: ../../content/applications/general/users/manage_users.rst:34 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 +msgid "View of a user’s form with a notification that the invitation email has been sent in Odoo" +msgstr "" + #: ../../content/applications/general/users/manage_users.rst:42 msgid "Remember that subscription prices follow the number of users. Refer to our `pricing page `_ for more information." msgstr "" @@ -2516,6 +2756,10 @@ msgstr "" msgid "With the :ref:`developer mode ` activated, *User Types* can be selected." msgstr "" +#: ../../content/applications/general/users/manage_users.rst:None +msgid "View of a user’s form in developer mode emphasizing the user type field in Odoo" +msgstr "" + #: ../../content/applications/general/users/manage_users.rst:53 msgid "The *Portal* and *Public* options do not allow you to choose access rights. Members have specific ones (such as record rules and restricted menus) and usually do not belong to the usual Odoo groups." msgstr "" @@ -2552,6 +2796,10 @@ msgstr "" msgid "To do so, go to :menuselection:`Settings --> Permissions`, activate **Password Reset** and *Save*." msgstr "" +#: ../../content/applications/general/users/manage_users.rst:None +msgid "Enabling Password Reset in Odoo Settings" +msgstr "" + #: ../../content/applications/general/users/manage_users.rst:94 msgid "Send reset instructions to users" msgstr "" @@ -2568,6 +2816,10 @@ 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 +msgid "Example of an email with a password reset link for an Odoo account" +msgstr "" + #: ../../content/applications/general/users/manage_users.rst:114 msgid "Change users’ passwords" msgstr "" @@ -2576,6 +2828,10 @@ 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 +msgid "Change another user's password on Odoo" +msgstr "" + #: ../../content/applications/general/users/manage_users.rst:123 msgid "Enter a new password and confirm by clicking on *Change Password*." msgstr "" @@ -2600,6 +2856,10 @@ 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 +msgid "View of a user’s form emphasizing the multi companies field in Odoo" +msgstr "" + #: ../../content/applications/general/users/manage_users.rst:152 msgid ":doc:`companies`" msgstr "" @@ -2821,6 +3081,10 @@ msgstr "" msgid "Go to :menuselection:`Apps` and install the **VoIP Module**." msgstr "" +#: ../../content/applications/general/voip/axivox.rst:None +msgid "VoIP module installation on an Odoo database" +msgstr "" + #: ../../content/applications/general/voip/axivox.rst:24 msgid "Go to :menuselection:`Settings --> General Settings --> Integrations`, and fill out the **Asterisk (VoIP)** field:" msgstr "" @@ -2837,6 +3101,10 @@ msgstr "" msgid "**VoIP Environment**: set as *Production*" msgstr "" +#: ../../content/applications/general/voip/axivox.rst:None +msgid "Integration of Axivox as VoIP provider in an Odoo database" +msgstr "" + #: ../../content/applications/general/voip/axivox.rst:37 msgid "Configure the VOIP user in the Odoo's user" msgstr "" @@ -2853,10 +3121,18 @@ msgstr "" msgid "**SIP Password**: the Axivox *SIP Password*" msgstr "" +#: ../../content/applications/general/voip/axivox.rst:None +msgid "Integration of Axivox user in the Odoo user preference" +msgstr "" + #: ../../content/applications/general/voip/axivox.rst:50 msgid "You can find all this information by logging in at https://manage.axivox.com/, selecting the user you want to configure, and referring to the fields as pictured below." msgstr "" +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "SIP credentials in the Axivox manager" +msgstr "" + #: ../../content/applications/general/voip/axivox.rst:58 msgid "Phone Calls" msgstr "" @@ -2873,14 +3149,26 @@ msgstr "" msgid "Your number is the one provided by Axivox." msgstr "" +#: ../../content/applications/general/voip/axivox.rst:None +msgid "Incoming VoIP call in Odoo" +msgstr "" + #: ../../content/applications/general/voip/axivox.rst:72 msgid "If you see a *Missing Parameter* message in the **Odoo softphone**, refresh your Odoo window and try again." msgstr "" +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "\"Missing Parameter\" error message in the Odoo softphone" +msgstr "" + #: ../../content/applications/general/voip/axivox.rst:80 msgid "If you see an *Incorrect Number* message in the Odoo softphone, make sure to use the international format, leading with the plus (+) sign followed by the international country code. E.g., +16506913277 (where +1 is the international prefix for the United States)." msgstr "" +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "\"Incorrect Number\" error message in the Odoo softphone" +msgstr "" + #: ../../content/applications/general/voip/onsip.rst:3 msgid "Use VoIP services in Odoo with OnSIP" msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index ee5007307..079d6102a 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 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-09-01 15:11+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -349,15 +349,19 @@ msgstr "" #: ../../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/inventory_adjustments/cycle_counts.rst:14 #: ../../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/uom.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:14 #: ../../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/reporting/integrating_landed_costs.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:42 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:14 -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:10 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:82 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:15 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:13 @@ -928,6 +932,10 @@ msgstr "" 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 "" @@ -940,6 +948,10 @@ msgstr "" 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 "" @@ -960,6 +972,10 @@ msgstr "" 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 "" @@ -972,18 +988,39 @@ msgstr "" 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 "" @@ -1048,6 +1085,171 @@ msgstr "" 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/inventory_adjustments.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:3 +msgid "Inventory adjustments" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:5 +msgid "In any warehouse management system, the recorded inventory counts in the database might not always match the actual inventory counts in the warehouse. The discrepancy between the two counts can be due to theft, damages, human errors, or other factors. As such, inventory adjustments must be made to reconcile the differences, and ensure that the recorded counts in the database match the actual counts in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:11 +msgid "In Odoo, inventory adjustments can be accessed through :menuselection:`Inventory --> Operations --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:14 +msgid "The :guilabel:`Inventory Adjustments` page shows all products that are currently in stock. Each line contains the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:17 +msgid ":guilabel:`Product`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:18 +msgid ":guilabel:`Lot/Serial Number`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:19 +msgid ":guilabel:`On Hand Quantity`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:22 +msgid "Add a new line" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:24 +msgid "To add an inventory adjustment line, click :guilabel:`Create` and fill in the :guilabel:`Product` and :guilabel:`Counted Quantity` fields. Then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:27 +msgid "At this stage, the count is recorded but not yet *applied*. Meaning the quantity on hand is not yet updated to match the new :guilabel:`Counted Quantity`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:30 +msgid "To apply the new :guilabel:`Counted Quantity`, click :guilabel:`Apply` on the line or the :guilabel:`Apply All` button on the top of the page. If :guilabel:`Apply All` is clicked, a reference or reason can be entered before clicking :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:None +msgid "Apply all option applies the inventory adjustment once a reason is specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:40 +msgid "Count products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:42 +msgid "Counting products is a recurring activity in a warehouse. Once a count is complete, go to :menuselection:`Inventory --> Operations --> Inventory Adjustments` to update the :guilabel:`Counted Quantity` column for each product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:46 +msgid "If a count matches the :guilabel:`On Hand Quantity` recorded in the database, click on :guilabel:`Set`, which will copy the value in the :guilabel:`On Hand Quantity` field and paste it in the :guilabel:`Counted Quantity` field. A move with `0.00` :guilabel:`Quantity Done` will be recorded in the product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:51 +msgid "If a count does *not* match the :guilabel:`On Hand Quantity` recorded in the database, record the count in the :guilabel:`Counted Quantity` field. When :guilabel:`Apply` is clicked, a move with the difference between the :guilabel:`On Hand Quantity` and :guilabel:`Counted Quantity` will be recorded in the product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:None +msgid "Inventory Adjustments History dashboard detailing a list of prior product moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:61 +msgid "Sometimes a count occurs, but can not be applied in the database right away. In the time between the actual count and applying the inventory adjustment, product moves can occur. In that case, the :guilabel:`On Hand Quantity` in the database can change and will not be consistent with the counted quantity. As an extra caution measure, Odoo will ask for confirmation before applying the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:68 +msgid "Plan counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:70 +msgid "Each inventory adjustment line contains the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:72 +msgid ":guilabel:`Scheduled Date`: the date at which a count should be made." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:73 +msgid ":guilabel:`User`: the person in charge of the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:74 +msgid ":guilabel:`Accounting Date`: the date at which the adjustments will be accounted. The column is hidden by default, but can be made visible by opening the column options icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:78 +msgid "In the Barcode app, users can only view counts assigned to them that are scheduled for today or earlier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:81 +msgid "To plan big counts, select the desired product lines on the :guilabel:`Inventory Adjustments` page. Then, click :guilabel:`Request a Count` and fill in the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:84 +msgid ":guilabel:`Inventory Date`: the planned date of the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:85 +msgid ":guilabel:`User`: the user responsible for the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:86 +msgid ":guilabel:`Accounting Date`: the date at which the inventory adjustment will be accounted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:87 +msgid ":guilabel:`Count`: to leave the :guilabel:`On Hand Quantity` of each product line blank, select :guilabel:`Leave Empty`. To prefill the :guilabel:`On Hand Quantity` of each product line with the current value recorded in the database, select :guilabel:`Set Current Value`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:91 +msgid "Finally, click :guilabel:`Confirm` to request the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:93 +msgid "By default, after an inventory adjustment is applied, the scheduled date for the next count is the 31st of December of the current year. To modify the default scheduled date, go to :menuselection:`Inventory --> Configuration --> Settings --> Operations` and change the date in the :guilabel:`Annual Inventory Day and Month` setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:None +msgid "Adjust the next inventory count date with the Annual Inventory Day and Month setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:3 +msgid "Cycle counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:5 +msgid "In most companies, the stock is only counted once a year. That's why by default, after making an inventory adjustment in Odoo, the scheduled date for the next count is set on the 31st of December. However, for some businesses it's crucial to have an accurate inventory count at all times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:10 +msgid "The goal of cycle counts is to keep critical stock levels accurate by counting more often at key locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:16 +msgid "In Odoo, cycle counts are location-based. The frequency of the counts is defined by the storage location. To activate storage locations, go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and activate the :guilabel:`Storage Locations` setting. Next, click :guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:None +msgid "Enable Storage Locations in Odoo settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:26 +msgid "Change the inventory frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:28 +msgid "To change a location's inventory frequency, first, go to the locations by clicking :menuselection:`Inventory --> Configuration --> Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:31 +msgid "Then, click on a location to open the location settings. Next, click on :guilabel:`Edit`. In the :guilabel:`Inventory Frequency (Days)` field, set the number of days. For example, a location that needs an inventory count every 30 days would set the :guilabel:`Inventory Frequency (Days)` value to `30`. Once the value is entered, click :guilabel:`Save` to apply the setting to the location. Now, once an inventory adjustment is applied to this location, the next scheduled count date will be automatically set based on the number of days in the :guilabel:`Inventory Frequency (Days)` setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:None +msgid "Edit a location to change the inventory frequency." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers.rst:5 msgid "Lots and Serial Numbers" msgstr "" @@ -1395,22 +1597,43 @@ 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 +msgid "View of the inventory settings. Process to enable the batch pickings option in the Odoo Inventory app" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:20 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 +msgid "View of the new menu, Batch Transfers, under operations" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:27 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 +msgid "View of a Batch Transfers form" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:34 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 +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 "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:42 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 +msgid "View of a batch transfer list. Products to pick with their source and target locations" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:51 msgid "Create a Batch Transfer from the Transfers List View" msgstr "" @@ -1419,10 +1642,18 @@ 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 +msgid "View of the process to add transfers to a batch transfer from the transfers list view" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:61 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 +msgid "Option to add a responsible to a batch transfer so it can be confirmed" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:69 msgid "Process a Batch Transfer" msgstr "" @@ -1431,10 +1662,23 @@ 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 +msgid "View of an in progress batch transfer" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:80 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 +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 +msgid "View of how backorders are handled in Odoo's batch transfers" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:93 msgid "Process a Batch Transfer from the Barcode app" msgstr "" @@ -1443,18 +1687,34 @@ msgstr "" msgid "Enter the *Barcode* application, select the *Batch Transfers* menu." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:None +msgid "View of the Odoo Barcode app dashboard" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:101 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 +msgid "View of the batch transfers dashboard inside of the Barcode app" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:108 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 +msgid "View of an in progress batch transfer with the Odoo Barcode application" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:116 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 +msgid "View of a ready and completed batch transfer inside of the Odoo Barcode application" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:123 msgid "Once all the products have been picked, click on *Validate* (on the last page) to mark the batch transfer as done." msgstr "" @@ -1495,6 +1755,82 @@ msgstr "" msgid "Once the receipt is validated, the products enter your stock but still belong to the owner. They don’t impact your inventory valuation." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:3 +msgid "Process wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:5 +msgid "While a batch transfer is a group of several pickings, a **wave transfer** only contains some parts of different pickings. Both methods are used to pick orders in a warehouse, and depending on the situation, one method may be a better fit than the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:9 +msgid "To handle orders of a specific product category, or fetch products that are at the same location, wave transfers are the ideal method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:12 +msgid "In Odoo, wave transfers are actually batch transfers with an extra step: transfers are split before being grouped in a batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:18 +msgid "Before a wave transfer can be created, the :guilabel:`Batch Transfers` and :guilabel:`Wave Transfers` options must be activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:21 +msgid "First, go to :menuselection:`Inventory --> Configuration --> Settings`. In the :guilabel:`Operations` section, enable :guilabel:`Batch Transfers` and :guilabel:`Wave Transfers`. Then, click :guilabel:`Save` to apply the settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:None +msgid "View of Odoo Inventory app settings to enable the wave transfers option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:30 +msgid "Add products to a wave" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:32 +msgid "Now that the settings are activated, start a wave transfer by adding products to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:34 +msgid "Wave transfers can only contain product lines from transfers of the same operation type. To view all the transfers and product lines in a specific operation, first go to the :guilabel:`Inventory` dashboard and locate the desired operation type's card. Then, open the options menu (the three dots icon in the corner of the operation type's card) and click :guilabel:`Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:None +msgid "How to get an operation type's list of operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:43 +msgid "On the operations page, select the product lines you want to add in a new or existing wave. Then, click :guilabel:`Add to Wave`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:None +msgid "Select lines to add to the wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:51 +msgid "Use the :guilabel:`Filters` in the search bar to group lines with the same product, location, carrier, etc..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:54 +msgid "After that, a pop-up box appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:56 +msgid "To add the selected lines to an existing wave transfer, select the :guilabel:`an existing wave transfer` option and select the existing wave transfer from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:59 +msgid "To create a new wave transfer, select the :guilabel:`a new wave transfer` option. If creating a new wave transfer, an employee can also be set in the optional :guilabel:`Responsible` field. Once the desired options are selected, click :guilabel:`Confirm` to add the product lines to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:64 +msgid "View wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:66 +msgid "To view all wave transfers and their statuses, go to :menuselection:`Inventory --> Operations --> Wave Transfers`. Wave transfers can also be viewed in the :guilabel:`Barcode` app by going to :menuselection:`Barcode --> Batch Transfers`." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning.rst:5 msgid "Planning" msgstr "" @@ -1559,10 +1895,19 @@ 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 +msgid "View of the delivery settings to have the delivery lead time taken into account" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:79 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 +msgid "View of the error that occurs when trying to choose an earlier date than what calculated\n" +"by Odoo" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:87 msgid "But, for all of this properly working, it is still necessary to configure all the lead times that could occur." msgstr "" @@ -1575,6 +1920,10 @@ 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 +msgid "View of the customer lead time configuration from the product form" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:103 msgid "For example, product B is ordered on the 2nd of April but the *Customer Lead Time* is two days. In that case, the expected delivery date is the 4th of April." msgstr "" @@ -1597,6 +1946,10 @@ 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 +msgid "View of the security lead time for sales configuration from the sales settings" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:124 msgid "For example, product B is scheduled to be delivered on the 6th of April but the *Security Lead Time* is one day. In that case, the scheduled date for the delivery order is the 5th of April." msgstr "" @@ -1633,10 +1986,18 @@ 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 +msgid "View of the way to add vendors to products" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:166 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 +msgid "View of the delivery lead time configuration from a vendor form" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:176 msgid "It is possible to add different vendors and, thus, different lead times depending on the vendor." msgstr "" @@ -1649,6 +2010,10 @@ 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 +msgid "View of the security lead time for purchase from the inventory settings" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:194 msgid "Doing so, every time the system generates purchase orders, those are scheduled that many days earlier to cope with unexpected vendor delays." msgstr "" @@ -1665,6 +2030,10 @@ 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 +msgid "View of the manufacturing lead time configuration from the product form" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:211 msgid "When working with *Manufacturing Lead Times*, the *Deadline Start* of the *MO* is **Commitment Date - Manufacturing Lead Time**. For example, the MO’s deadline start date for an order having a commitment date on the 10th of July is June 27th." msgstr "" @@ -1677,6 +2046,10 @@ 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 +msgid "View of the security lead time for manufacturing from the manufacturing app settings" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:230 msgid "For example, a customer orders B with a delivery date scheduled on the 20th of June. The *Manufacturing Lead Time* is 14 days and the *Security Lead Time* is 3 days, so the manufacturing of B needs to start at the latest on the 3rd of June, which is the MO’s planned date." msgstr "" @@ -1739,144 +2112,253 @@ msgid "Products" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:3 -msgid "How to select the right replenishment strategy" +msgid "Select a replenishment strategy" 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." +msgid "In Odoo, there are two strategies for 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 purchase or manufacturing order. 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:10 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:6 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:14 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:48 +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:16 +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:58 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:18 +msgid "Reordering rules are used to ensure that 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:23 +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:26 msgid "Make to Order" 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 "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:33 -msgid "Minimum stock rules" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:31 +msgid "Unlike products replenished using reordering rules, Odoo automatically links the sales order to the purchase order (PO) or manufacturing order (MO) generated by the MTO route. Another difference between reordering rules and MTO is with MTO, Odoo generates a draft :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` immediately after the sales order is confirmed. With reordering rules, Odoo generates a draft :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` when the product's forecasted stock falls below the set minimum quantity. In addition, Odoo will automatically add quantities to the :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` as the forecast changes, as long as the :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` is not confirmed." 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:41 +msgid "The MTO route is the best replenishment strategy for products that are customized and should be used for this purpose only." 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:50 +msgid "To access the replenishment report, go to :menuselection:`Inventory --> Operations --> Replenishment`. By default, the replenishment report shows every product that needs to be manually reordered. If there is no specific rule for a product, Odoo assumes that the :guilabel:`Minimum Quantity` and :guilabel:`Maximum Quantity` stock are both `0.00`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:47 -msgid "Then, click on your product to access the related product form and, on the \"Inventory submenu\", do not forget to select a supplier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:54 -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:None +msgid "The replenishment report shows products that need to be reordered manually." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:60 -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 "For products that don't have a set reordering rule, Odoo calculates the forecast as sales orders, deliveries, and receipts are confirmed. 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:64 -msgid "On the product form, under Inventory, click on \"Make To Order\"." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:65 +msgid "Before creating a new reordering rule, make sure the product has a vendor or a bill of materials configured on the product form. Also, make sure the :guilabel:`Product Type` is set to `Storable Product` on the product form. By definition, a consumable product does not have its inventory levels tracked, so Odoo can not account for a consumable product in the stock valuation." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:70 -msgid "Choice between the two options" +msgid "To create a new reordering rule from the replenishment report, go to :menuselection:`Inventory --> Operations --> Replenishment`, click :guilabel:`Create`, and set the :guilabel:`Product`. If desired, set a :guilabel:`Min Quantity` and a :guilabel:`Max Quantity`. Finally, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:72 -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:75 +msgid "To create a new reordering rule from the product form, go to :menuselection:`Inventory --> Products --> Products`, select a product to open its product form, click the :guilabel:`Reordering Rules` smart button, and click :guilabel:`Create`. Then, fill out the fields and save the new reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:80 +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, 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:85 +msgid "To automate replenishment, click :guilabel:`Automate Orders`. When this button is clicked, Odoo will automatically generate a draft :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` 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:91 +msgid "A reordering rule can be temporarily deactivated for a given period by using the :guilabel:`Snooze` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:None +msgid "Snooze feature to temporarily deactivate reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:98 +msgid "A :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` created by a manual replenishment will have `Replenishment Report` as the source document. A :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` created by an automated reordering rule will have the sales order(s) reference number(s) that triggered the rule as the source document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:None +msgid "Look at the source panel showing where RFQ/MFG orders originated from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:108 +msgid "Make to order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:110 +msgid "Since the Make to Order (MTO) route is only recommended for customized products, the route is hidden by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:113 +msgid "To activate the Make to Order (MTO) route in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:115 +msgid "Go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:116 +msgid "Activate :guilabel:`Multi-Step Routes` setting and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:117 +msgid "Go to :menuselection:`Inventory --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:118 +msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:119 +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:123 +msgid "Activating the :guilabel:`Multi-Step Routes` setting also activates :guilabel:`Storage Locations` setting. 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:127 +msgid "To set a product's procurement route to MTO, go to :menuselection:`Inventory --> Products --> Products`, click on a product to open the product form, and click :guilabel:`Edit`. Then, click on the :guilabel:`Inventory` tab and in the :guilabel:`Routes` options, select :guilabel:`Replenish on Order (MTO)`. For products purchased directly from a vendor, make sure the :guilabel:`Buy` route is selected in addition to the MTO route and a vendor is configured in the :guilabel:`Purchase` tab. For products manufactured in-house, make sure the :guilabel:`Manufacture` route is selected in addition to the MTO route and a bill of materials is configured for the product. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:None +msgid "Enable the Replenish on Order (MTO) route on the product settings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:3 -msgid "Use Different Units of Measure" +msgid "Use different units of measure" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:5 -msgid "In some cases, handling products in different units of measure is necessary. For example, if you buy products in a country where the metric system is of application and sell in a country where the imperial system is used, you will need to convert the units. Another common use case is buying products in bigger packs to your supplier and selling them in units to your customers." +msgid "In some cases, handling products in different units of measure is necessary. For example, a business can buy products from a country that uses the metric system, and then sell those products in a country that uses the imperial system, so the business needs to convert the units. Another case for unit conversion is when a business buys products in a big pack from a supplier and then sells those products in individual units." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:12 -msgid "You can set up Odoo to work with different units of measure for one product." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:11 +msgid "Odoo can be set up to use different units of measure for one product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:18 -msgid "In the *Inventory* application, go to :menuselection:`Configuration --> Settings`. In the *Products* section, activate *Units of Measure*, then *Save*." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:16 +msgid "To use different units of measure in Odoo, first go to :menuselection:`Inventory --> Configuration --> Settings --> Products` and activate the :guilabel:`Units of Measure` setting. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:None +msgid "Enable Units of Measure in the Inventory settings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:25 -msgid "Create New Units of Measure" +msgid "Units of measure categories" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:27 -msgid "In the *Inventory* application go to :menuselection:`Configuration --> UoM`. There, hit *Create*. As an example, we will create a Box of 6 units that we will use for the Egg product." +msgid "After enabling the units of measure setting, view the default units of measure categories in :menuselection:`Inventory --> Configuration --> Units of Measures --> UoM Categories`. The category is important for unit conversion, Odoo can only convert a product's units from one unit to another only if both units belong to the same category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:34 -msgid "The category is important for unit conversion, you will be able to convert products from one unit to another only if those units belong to the same category. The box of 6 is 6 times bigger than the reference unit of measure for the category which is “Units” here." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:None +msgid "Set units of measure categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:43 -msgid "Specify Units of Measure on your Products" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:36 +msgid "Each units of measure category has a reference unit. The reference unit is highlighted in blue in the :guilabel:`Uom` column of the :guilabel:`Units of Measure Categories` page. Odoo uses the reference unit as a base for any new units." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:45 -msgid "In the :menuselection:`Inventory application --> Master Data --> Products`, open the product which you would like to change the purchase/sale unit of measure, and click on *Edit*." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:40 +msgid "To create a new unit, first select the correct category. For example, to sell a product in a box of six units, click on the :guilabel:`Unit` category line. Next, click :guilabel:`Edit`. After that, click :guilabel:`Add a line`. Then, in the :guilabel:`Unit of Measure` field, title the new unit `Box of 6`. In the :guilabel:`Type` field, select :guilabel:`Bigger than the reference Unit of Measure`. In the :guilabel:`Ratio` field, enter `6.00000` since a box of six is six times bigger than the reference unit (`1.00000`). Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:47 +msgid "Click on the :guilabel:`Unit` category." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:49 -msgid "In the *General Information* tab, you can select the *Unit of Measure* in which the product will be sold, which is also the unit in which internal transfers will take place. You can also select the *Purchase Unit of Measure*, which is the unit in which you purchase the product." +msgid "Click :guilabel:`Add a line`. As an example, we will create a Box of 6 units that we will use for the Egg product. The box of 6 is 6 times bigger than the reference unit of measure for the category which is “Units” here." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:59 -msgid "Transfer from One Unit to Another" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:None +msgid "Convert products from one unit to another as long as they belong to the same category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:62 -msgid "Buy in the Purchase UoM" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:58 +msgid "Specify a product's units of measure" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:64 -msgid "In the *Purchase* application, *Create* a new request for quotation in which you include the product with the different *Units of Measure* and *Confirm* it." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:60 +msgid "To set units of measure on a product, first go to :menuselection:`Inventory --> Products --> Products` and click on a product to open its settings. Then, click on :guilabel:`Edit`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:71 -msgid "On the automatically generated purchase orders, the UoM used is the Box of 6, meaning the Purchase UoM. You have of course the possibility to manually modify the UoM if necessary. When you enter the *Receipt* which is linked to the purchase order, you can observe that the 10 boxes of 6 units have been converted in 60 units. Indeed, the stock is managed in units." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:63 +msgid "In the :guilabel:`General Information` tab, edit the :guilabel:`Unit of Measure` field to specify the unit of measure that the product is sold in. The specified unit will also be the unit used to keep track of the product's inventory and internal transfers. Edit the :guilabel:`Purchase UoM` field to specify the unit of measure that the product is purchased in." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:69 +msgid "Unit conversion" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:72 +msgid "Buy products in the Purchase UoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:74 +msgid "When creating a new request for quotation (RFQ) in the Purchase app, Odoo automatically uses the product's specified purchase unit of measure. However, if needed, the :guilabel:`UoM` can be manually edited on the RFQ." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:78 +msgid "After the RFQ is confirmed into a purchase order (PO), click on the :guilabel:`Receipt` smart button at the top right corner of the PO. Odoo automatically converts the purchase unit of measure into the product's sales/inventory unit of measure, so the :guilabel:`Demand` column of the delivery receipt shows the converted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:83 +msgid "For example, if the product's purchase UoM is `Box of 6` and its sales/inventory unit of measure is `Units`, the PO shows the quantity in boxes of six, and the delivery receipt shows the quantity in units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:88 msgid "Replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:84 -msgid "When doing a replenishment via the *Replenish* button on the product form, you have the possibility to use a different unit of measure." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:90 +msgid "A request for quotation for a product can also be generated directly from the product form using the :guilabel:`Replenish` button. After clicking :guilabel:`Replenish`, a replenish assistant box pops up. The purchase unit of measure can be manually edited here if needed. Then, click :guilabel:`Confirm` to create the RFQ." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:94 -msgid "Sell in bigger UoM" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:95 +msgid "Next, click the :guilabel:`Units Forecasted` smart button on the product form and scroll down to :menuselection:`Forecasted Inventory --> Requests for quotation`. Click on the RFQ reference number to open the draft RFQ. The purchase UoM can also be edited here if needed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:96 -msgid "You can choose the unit of measure on the sale order document and decide to sell the eggs by the dozen. When doing so, the price is automatically computed from Units UoM to adapt to the selected *UoM*." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:100 +msgid "Sell in a different UoM" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:103 -msgid "In the delivery order, the *UoM* used in the sale order is converted to the *UoM* used for stock management, in our use case, the Units." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:102 +msgid "When creating a new quotation in the Sales app, Odoo automatically uses the product's specified unit of measure. However, if needed, the :guilabel:`UoM` can be manually edited on the quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:105 +msgid "After the quotation is sent to the customer and confirmed into a sales order (SO), click on the :guilabel:`Delivery` smart button at the top right corner of the SO. Odoo automatically converts the unit of measure into the product's inventory unit of measure, so the :guilabel:`Demand` column of the delivery shows the converted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:110 +msgid "For example, if the product's UoM on the SO was changed to `Box of 6`, but its inventory unit of measure is `Units`, the SO shows the quantity in boxes of six, and the delivery shows the quantity in units." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:3 @@ -1884,51 +2366,75 @@ msgid "When Should you Use Packages, Units of Measure or Special Packaging?" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:6 -msgid "Units of Measure" +msgid "Units of measure" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:8 msgid "Units of measure specify the unit used to handle a product. In Odoo, you have the possibility to specify the unit of measure in which you manage your stock and the one which is used when purchasing the product to your supplier." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:None +msgid "Specify unit of measure for handling a product vs. when it's purchased." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:16 -msgid "The *conversion* between the different units of measure is done automatically. The only condition is that all the units have to be in the *same category* (Unit, Weight, Volume, Length,...)" +msgid "Once a product has a :guilabel:`Unit of Measure` and a :guilabel:`Purchase UoM` set on the product form, Odoo can automatically convert the different units in the product's purchase/sales orders and the orders' respective delivery orders/receipts. The only condition is that all the units have to be in the *same category* (Unit, Weight, Volume, Length, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:20 -msgid "For example, if I have the following reordering rule for the egg and I run the scheduler, the quantity added in the automatically generated purchase order will be in dozens but what will enter the stock will be units." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:21 +msgid "For example, a product can have its :guilabel:`Unit of Measure` set to `feet (ft)` and its :guilabel:`Purchase UoM` set to `centimeters (cm)`. When a purchase order (PO) is created for that product, it will list the quantity in centimeters. Then, when the PO is confirmed, Odoo automatically generates a receipt and converts the centimeters to feet. The receipt will list the quantity in feet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:28 msgid "Packages" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:37 -msgid "The package is the physical container in which you put one or several products from a picking. For example, when you deliver a product, you can decide to separate the quantity into two different packages. It then allows you to have a report with the quantity of products for each package." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:30 +msgid "A package refers to the physical container that holds one or several products from a picking. For example, when a product is ready for delivery, its quantities can be separated into two different packages. In Odoo, the quantity of products in each package can be recorded in the database. Make sure the :guilabel:`Packages` option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Operations`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:43 -msgid "To separate a delivery into different packages you will have to set the done quantity to the desired package quantity then click on \"PUT IN PACK\", do this for each package." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:36 +msgid "On a delivery order, separate the products into different packages by setting the :guilabel:`Done` quantity to the desired quantity in the first package. Then, click :guilabel:`Put in Pack` to record the first package. Repeat for each package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:None +msgid "Separate delivery into different packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:None +msgid "Separate delivery package details" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:49 +msgid "Packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:51 +msgid "Packaging refers to a standard container that holds several unit of a product. For example, cans of soda can be in a 6-pack, 15-pack, or even a pallet for the packaging." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:54 -msgid "Packaging" +msgid "In Odoo, packagings are used for indicative purposes on sales/purchase orders and inventory transfers. The main difference between packagings and units of measure is that packagings are defined at the product level while UoMs are generic." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:56 -msgid "The packaging is the physical container that protects your product. If you are selling computers, the packaging contains the computer with the notice and the power plug." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:None +msgid "Different product packaging examples." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:60 -msgid "In Odoo, packagings are used for indicative purposes on sale orders. They can be specified on the product form, in the inventory tab." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:None +msgid "Package field on purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:70 -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." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:67 +msgid "Packaging is also useful during product reception. When scanning the barcode of the packaging, Odoo automatically adds the number of units contained in the packing on the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:71 +msgid ":doc:`uom`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies.rst:5 -msgid "Inventory Adjustment" +msgid "Replenishment strategies" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst:3 @@ -1939,6 +2445,10 @@ msgstr "" 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 "" @@ -1964,51 +2474,75 @@ msgid "Integrating additional costs to products (landed costs)" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:5 -msgid "The landed cost feature in Odoo allows to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product." +msgid "The landed cost feature in Odoo allows the user to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:10 -msgid "Landed costs can only be applied to products with a FIFO or AVCO costing method and an automated inventory valuation (which requires the accounting application to be installed)." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:11 +msgid "First, go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation` and activate the :guilabel:`Landed Costs` feature. Odoo also gives the option to set a :guilabel:`Default Journal` in which the landed costs accounting entries will be recorded." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:17 -msgid "First, you need to go in :menuselection:`Inventory --> Configuration --> Settings` and activate the landed costs feature. You can also determine the default journal in which the landed cost accounting entries will be recorded." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:None +msgid "Activate the landed cost feature in Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:20 msgid "Add costs to products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:28 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:23 msgid "Receive the vendor bill" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:30 -msgid "Let’s imagine I receive a bill from custom duties for a shipment. I’ll tick the box *Landed Costs* on the vendor bill line." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:25 +msgid "After a vendor fulfills a purchase order and sends a bill, click :guilabel:`Create Bill` on the purchase order to create a vendor bill in Odoo. If the vendor bill includes landed costs, such as custom duties, tick the box in the :guilabel:`Landed Costs` column on the vendor bill invoice line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:None +msgid "Enable Landed Costs option on vendor bill line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:33 +msgid "For charges that are always landed costs, create a landed cost product in Odoo. That way, the landed cost product can be quickly added to the vendor bill as an invoice line instead of manually entering the landed cost information every time a vendor bill comes in." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:37 -msgid "The landed cost product must be of type service." +msgid "First, create a new product in :menuselection:`Inventory --> Products --> Products --> Create`. Next, name the landed cost product. Then, set the :guilabel:`Product Type` to :guilabel:`Service`. A landed cost product must always be a service product type. After that, go to the :guilabel:`Purchase` tab and check the box next to :guilabel:`Is a Landed Cost`. Finally, click :guilabel:`Save` to finish creating the landed cost product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:43 msgid "If this product is always a landed cost, you can also define it on the product and avoid having to tick the box on each vendor bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:45 -msgid "At the top of my vendor bill, I’ll see a button *create landed costs*. I click on this button and a landed cost is automatically created. I can now decide on which picking those additional costs should apply." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:None +msgid "Option to define a product as a landed cost." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:52 -msgid "I can now click on *Compute* and go in the tab *Valuation Adjustments* to see the impact on my products costs. The last step is to validate the landed cost." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:50 +msgid "Once the landed cost is added to the vendor bill (either by checking the :guilabel:`Landed Cost` option on the invoice line or adding a landed cost product to the bill), click the :guilabel:`Create Landed Costs` button at the top of the bill. Odoo automatically creates a landed cost record with the set landed cost pre-filled in the :guilabel:`Additional Costs` product lines. From here, decide which picking the additional costs apply to by clicking :guilabel:`Edit` and selecting the picking reference number from the :guilabel:`Transfers` drop-down menu. Finally, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:56 -msgid "I can access the journal entry that has been created by the landed cost by clicking on the journal entry." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:None +msgid "Use a warehouse transfer to cover a landed cost in the accounting journal." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:63 -msgid "You are not forced to start from the vendor bill, you can also go in :menuselection:`Inventory --> Operations --> Landed Costs` and directly create the landed cost from there." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:62 +msgid "After setting the picking, click :guilabel:`Compute` on the landed cost record. Then, go to the :guilabel:`Valuation Adjustments` tab to see the impact of the landed costs. Finally, click :guilabel:`Validate` to post the landed cost entry to the accounting journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:66 +msgid "The user can access the journal entry that has been created by the landed cost by clicking on the :guilabel:`Journal Entry`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:70 +msgid "The product that the landed cost is applied to must have a product category set to a :abbr:`FIFO (First In, First Out)` or an :abbr:`AVCO (Average Costing)` method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:None +msgid "Landed cost journal entry" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:78 +msgid "Landed cost records can also be directly created in :menuselection:`Inventory --> Operations --> Landed Costs`, it is not necessary to create a landed cost record from the vendor bill." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:7 @@ -2666,36 +3200,168 @@ msgstr "" msgid "Warehouses" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:3 -msgid "What is the difference between warehouses and locations?" +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:3 +msgid "Resupply from another warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:5 -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." +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:5 +msgid "A common use case for multiple warehouses is to have one central warehouse that resupplies multiple shops, and in this case, each shop is considered a local warehouse. When a shop wants to replenish a product, the product is ordered to the central warehouse. Odoo allows the user to easily set which warehouse(s) can resupply another warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:9 -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." +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:13 +msgid "To resupply from another warehouse, first go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and activate :guilabel:`Multi-Step Routes`. Then, click :guilabel:`Save` to apply the setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:15 -msgid "There are 3 types of locations:" +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:None +msgid "Enable Multi-Step Routes in Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:17 -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." +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:21 +msgid "View all the configured warehouses by going to :menuselection:`Inventory --> Configuration --> Warehouses`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:21 -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." +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:24 +msgid "Create a new warehouse by clicking :guilabel:`Create`. Then, give the warehouse a name and a :guilabel:`Short Name`. Finally, click :guilabel:`Save` to finish creating the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:25 -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**)." +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:27 +msgid "After that, go back to the :guilabel:`Warehouses` page and open the warehouse that will be resupplied by the second warehouse. Then, click :guilabel:`Edit`. In the :guilabel:`Warehouse Configuration` tab, locate the :guilabel:`Resupply From` field, and check the box next to the second warehouse's name. If the warehouse can be resupplied by more than one warehouse, make sure to check those warehouses' boxes too. Finally, click :guilabel:`Save` to apply the setting. Now, Odoo knows which warehouses can resupply this warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst:31 -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." +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:None +msgid "Supply one warehouse with another in the Warehouse Configuration tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:39 +msgid "Set route on a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:41 +msgid "After configuring which warehouse(s) to resupply from, a new route is now available on all product forms. The new route appears as :guilabel:`Supply Product from [Warehouse Name]` under the :guilabel:`Inventory` tab on a product form. Use the :guilabel:`Supply Product from [Warehouse Name]` route with a reordering rule or the make to order (MTO) route to replenish stock by moving the product from one warehouse to another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:None +msgid "Route setting which enables a product to resupplied from a second warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:51 +msgid "When a product's reordering rule is triggered and the product has the :guilabel:`Supply Product from [Warehouse Name]` route set, Odoo automatically creates two pickings. One picking is a *delivery order* from the second warehouse, which contains all the necessary products, and the second picking is a *receipt* with the same products for the main warehouse. The product move from the second warehouse to the main warehouse is fully tracked in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:57 +msgid "On the picking/transfer records created by Odoo, the :guilabel:`Source Document` is the product's reordering rule. The location between the delivery order and the receipt is a transit location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:None +msgid "A reordering rule automatically creates two receipts for stock between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:None +msgid "A warehouse order for resupplying one warehouse's stock with another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:None +msgid "A receipt for stock received to one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:3 +msgid "Manage Warehouses and Locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:9 +msgid "Warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:11 +msgid "In Odoo, a **Warehouse** is the actual building/place in which a company's items are stocked. Multiple warehouses can be set up in Odoo and the user can create moves between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:15 +msgid "Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:17 +msgid "A **Location** is a specific space within the warehouse. It can be a sublocation of the warehouse (a shelf, a floor, an aisle, and so on). Therefore, a location is part of one warehouse only and it is not possible to link one location to multiple warehouses. In Odoo, as many locations can be configured as needed under one warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:22 +msgid "There are three types of locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:24 +msgid "The **Physical Locations** are internal locations that are part of the warehouses that the company owns. They can be the loading and unloading areas of the warehouse, a shelf, a department, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:28 +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 they are not owned by the user's company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:32 +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 recording lost products (**Inventory Loss**), or accounting for products that are on their way to the warehouse (**Procurements**)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:37 +msgid "In Odoo, locations are structured hierarchically. Locations can be structured as a tree, dependent on a parent-child relationship. This gives more detailed levels of analysis of the stock operations and the organization of the warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:44 +msgid "To activate locations, go to :menuselection:`Configuration --> Settings` and enable :guilabel:`Storage Locations`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:None +msgid "Enable the storage location feature in Odoo Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:52 +msgid "To manage several routes within the warehouses, also enable :guilabel:`Multi-Step Routes` and check :doc:`../../routes/concepts/use_routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:56 +msgid "Create a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:58 +msgid "To create a warehouse, go to :menuselection:`Configuration --> Warehouse Management --> Warehouses` and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:61 +msgid "Then, fill out a :guilabel:`Warehouse Name` and a :guilabel:`Short Name`. The short name is five characters maximum." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:None +msgid "Short name field of a warehouse on Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:69 +msgid "The :guilabel:`Short Name` appears on transfer orders and other warehouse documents. Odoo recommends using an understandable one like \"WH/[first letters of location]\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:72 +msgid "Now, go back to the :guilabel:`Inventory` dashboard. There, new operations related to the newly created warehouse have been automatically generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:None +msgid "Inventory app dashboard displaying new transfer types for the recently created warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:80 +msgid "Adding a second warehouse will automatically activate the :guilabel:`Locations` setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:83 +msgid "Create a new location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:85 +msgid "To create a location, go to :menuselection:`Configuration --> Warehouse Management --> Locations` and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:88 +msgid "Then, fill out a :guilabel:`Location Name` and a :guilabel:`Parent Location` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:None +msgid "Create a new warehouse location in Odoo Inventory." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes.rst:5 @@ -2763,111 +3429,83 @@ 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." +msgid "When owning several warehouses, goods might need to be transferred from one warehouse to another. This type of transfer is called an *inter-warehouse transfer*. While physically performing the inter-warehouse transfer might be simple, the administrative part can be complex. Fortunately, Odoo comes with an intuitive flow that helps save time when registering inter-warehouse 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: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: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: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: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: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 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:11 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:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:13 +msgid "The following paragraphs detail a sample inter-warehouse transfer, referred to as an *internal transfer*, use case. The sample use case assumes that the user has already configured their second warehouse." 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`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:17 +msgid "To transfer eight units of a product from the first warehouse to another one, proceed as follows:" 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)." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:19 +msgid "From the :guilabel:`Inventory` dashboard, select an internal movement operation of one of the two warehouses. To do so, click on the three vertical dots icon on the top right corner of the operation card and select :guilabel:`Planned Transfer`." 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." +#: ../../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:96 -msgid "If you selected **Immediate Transfer**, Odoo processes the transfer automatically after you clicked on **Validate**." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:27 +msgid "On the new planned transfer form, select the :guilabel:`Source Location` (in this case, the first warehouse) and the :guilabel:`Destination Location` (in this case, the second warehouse)." 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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:30 +msgid "Next, add the products that will be transferred by clicking on :guilabel:`Add a line`, then click on :guilabel:`Save` and :guilabel:`Mark as ToDo` once done. After that, Odoo puts the transfer in the :guilabel:`Waiting` status. Then, click on :guilabel:`Reserve` to reserve the number of products in the source warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:102 +#: ../../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:40 +msgid "If :guilabel:`Immediate Transfer` was selected instead of :guilabel:`Planned Transfer`, Odoo processes the transfer automatically after the :guilabel:`Validate` button is clicked on the internal transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:44 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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:46 +msgid "On the :guilabel:`Inventory` dashboard, open the souce location's internal transfer operation page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:110 -msgid "Select the right transfer order." +#: ../../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: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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:53 +msgid "Open the desired transfer order form." 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**." +#: ../../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:128 -msgid "Create a backorder if you expect to process the remaining products later." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:59 +msgid "Click on the pencil icon in the lower right corner to open the operation details window. In this new window, the quantity of products can be manually set." 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." +#: ../../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:67 +msgid "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 a *backorder* should be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:70 +msgid "Create a backorder if it is expected that the remaining products will be processed later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst:71 +msgid "Do not create a backorder if the remaining products will not be supplied/received." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:3 @@ -2906,285 +3544,373 @@ msgstr "" msgid "Once you have done it, you can convert it to a sales order. Then, a delivery order will be automatically generated, with a product reserved in warehouse A and one in warehouse B." msgstr "" -#: ../../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/use_routes.rst:3 +msgid "Routes and Pull/Push Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:5 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:5 +msgid "In inventory management, the supply chain strategy determines when products should be purchased/manufactured, delivered to distribution centers, and made available to the retail channel." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:9 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:9 +msgid "In Odoo, a product's supply chain strategy can be configured using *Routes*, which feature *Pull and Push Rules*. Once everything is properly configured, the Inventory app can automatically generate transfers following the configured push/pull rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:14 msgid "Inside the warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:18 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:16 +msgid "In a generic warehouse, there are receiving docks, a quality control area, storage locations, picking and packing areas, and shipping docks. All products go through all these locations. As the products move through the locations, each location triggers the products' specified route and rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:27 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of a generic warehouse with stock and quality control area." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:25 +msgid "In this example, vendor trucks unload pallets of ordered products at the receiving docks. Operators then scan the products in the receiving area. Depending on the product's route and rules, some of these products are sent to a quality control area (for example, products that are components used in the manufacturing process), while others are directly stored in their respective locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of a generic push to rule when receiving products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:34 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:48 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:45 -msgid "How does it work?" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of a generic pull from rule when preparing deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:51 -msgid "Pull Rules" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:45 +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:47 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 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:50 +msgid "Pull Rules are used to fulfill a sales order. 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*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:65 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:54 +msgid "In this 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:72 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:57 +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*. Finally, other pull 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:77 -msgid "Push Rules" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:63 +msgid "All these product transfers are automatically generated by Odoo based on the pull rules, starting from the end (the customer location) and going backward (the stock warehouse). While working, the operator processes these transfers in the opposite order: first the picking, then the packing, and finally the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:79 -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.\"" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:69 +msgid "Push rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:84 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:71 +msgid "On the other hand, *Push Rules* are much easier to understand. Instead of generating documents based on needs, they are triggered in real time 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:89 -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*." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:75 +msgid "An example of a push rule would be: when a product arrives in the *Receipt Area*, move it to the *Storage Location*. As different push rules can be applied to different products, the user can assign different storage locations for different products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:94 -msgid "*Push Rules* can be triggered only if no *Pull Rule* pre-generated the upstream transfers." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:79 +msgid "Another push 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:98 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:83 +msgid "Push rules can only be triggered if there are no pull rules that have already generated the product transfers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:105 -msgid "Use Routes and Rules" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:87 +msgid "Sets of push/pull rules like those are called *Routes*. The grouping on the rule decides if products are grouped in the same transfer or not. For example, during the picking operation, all orders and their products 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:107 -msgid "Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you manage advanced routes configuration such as:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:93 +msgid "Use routes and rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:110 -msgid "Manage product manufacturing chains;" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:95 +msgid "Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you manage advanced route configurations such as:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:111 -msgid "Manage default locations per product;" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:98 +msgid "Manage product manufacturing chains." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:112 -msgid "Define routes within your warehouse according to business needs, such as quality control, after-sales services, or supplier returns;" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:99 +msgid "Manage default locations per product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:100 +msgid "Define routes within the stock 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:102 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 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:104 +msgid "To configure a route for a product, first, open the :guilabel:`Inventory` application and go to :menuselection:`Configuration --> Settings`. Then, in the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` feature and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:126 -msgid "The *Storage Locations* feature is automatically activated with the *Multi-Step Routes*." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "Activate the Multi-Step Routes feature in Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:129 -msgid "Once this first step is completed, you have the choice between pre-configured routes or custom ones. Both are explained below." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:113 +msgid "The :guilabel:`Storage Locations` feature is automatically activated with the :guilabel:`Multi-Step Routes` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:133 -msgid "Pre-configured Routes" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:116 +msgid "Once this first step is completed, the user can use pre-configured routes that come with Odoo, or they can create custom routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:135 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:120 +msgid "Pre-configured routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:144 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:122 +msgid "To access Odoo's pre-configured routes, go to :menuselection:`Inventory --> Configuration --> Warehouses`. Then, open a warehouse form. In the :guilabel:`Warehouse Configuration` tab, the user can view the warehouse's pre-configured routes for :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:153 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "A preconfigured warehouse in Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:161 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:131 +msgid "Some more advanced routes, such as pick-pack-ship, are also available. The user can select the route that best fits their business needs. Once the :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` routes are set, head to :menuselection:`Inventory --> Configuration --> Routes` to see the specific routes that Odoo generated." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:171 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of all the preconfigured routes Odoo offers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:140 +msgid "On the :guilabel:`Routes` page, click on a route to open the route form. In the route form, the user can view which places the route is :guilabel:`Applicable On`. The user can also set the route to only apply on a specific :guilabel:`Company`. This is useful for multi-company environments; for example, a user can have a company and warehouse in Country A and a second company and warehouse in Country B." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of a route example applicable on product categories and warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:150 +msgid "At the bottom of the route form, the user can view the specific :guilabel:`Rules` for the route. Each :guilabel:`Rule` has an :guilabel:`Action`, a :guilabel:`Source Location`, and a :guilabel:`Destination Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "An example of rules with push & pull actions in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:159 msgid "Custom Routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:173 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:161 +msgid "To create a custom route, go to :menuselection:`Inventory --> Configuration --> Routes`, and click on :guilabel:`Create`. Next, choose the places where this route can be selected. A route can be applicable on a combination of places." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:182 -msgid "Each place has a different behavior, so it is important to tick only the useful ones and adapt each route accordingly." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of a pick-pack-ship route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:185 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:169 +msgid "Each place has a different behavior, so it is important to tick only the useful ones and adapt each route accordingly. Then, configure the :guilabel:`Rules` of the route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:195 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:172 +msgid "If the route is applicable on a product category, the route still needs to be manually set on the product category form by going to :menuselection:`Inventory --> Configuration --> Product Categories`. Then, select the product category and open the form. Next, click :guilabel:`Edit` and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:203 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:177 +msgid "When applying the route on a product category, all the rules configured in the route are applied to **every** product in the category. This can be helpful if the business uses the dropshipping process for all the products from the same category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:211 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of a route applied to the \"all\" product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:218 -msgid "Then, the route can be chosen on each line of the document." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:185 +msgid "The same behavior applies to the warehouses. If the route can apply to :guilabel:`Warehouses`, all the transfers occurring inside the chosen warehouse that meet the conditions of the route's rules will then follow that route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:224 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of the warehouse drop-down menu when selecting applicable on warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:232 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:193 +msgid "If the route is applicable on :guilabel:`Sales Order Lines`, it is more or less the opposite. The route must be manually chosen when creating a quotation. This is useful if some products go through different routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:240 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:197 +msgid "Remember to toggle the visibility of the :guilabel:`Route` column on the quotation/sales order. Then, the route can be chosen on each line of the quotation/sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:245 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +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:204 +msgid "Finally, there are routes that can be applied to products. Those work more or less like the product categories: once selected, the route must be manually set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:207 +msgid "To set a route on a product, go to :menuselection:`Inventory --> Products --> Products` and select the desired product. Then, go to the :guilabel:`Inventory` tab and under the :guilabel:`Operations` section, select the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of a product form, where the route must be selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:216 +msgid "Rules must be set on the route in order for the route to work." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:219 msgid "Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:247 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:221 +msgid "The rules are defined on the route form. First, go to :menuselection:`Inventory --> Configuration --> Routes` and open the desired route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` section, click on :guilabel:`Add a line`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:255 -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:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +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:259 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:229 +msgid "The available rules trigger various actions. If Odoo offers *Push* and *Pull* rules, others are also available. Each rule has an :guilabel:`Action`:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:264 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:232 +msgid ":guilabel:`Pull From`: this rule is triggered by a need for the product in a specific location. The need can come from a sales order being validated or from a manufacturing order requiring 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:268 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:236 +msgid ":guilabel:`Push To`: this rule is triggered by the arrival of some products in the defined source location. In the case of the user moving 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:274 -msgid "**Buy**: when products are needed at the destination location, a request for quotation is created to fulfill the need." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:239 +msgid ":guilabel:`Pull & Push`: this rule allows the generation of 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:276 -msgid "**Manufacture**: when products are needed in the source location, a manufacturing order is created to fulfill the need." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:244 +msgid ":guilabel:`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:283 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:246 +msgid ":guilabel:`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:288 -msgid "On the other hand, the *Supply Method*, allows defining what happens at the source location:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "Overview of a \"Pull From\" rule that creates a transfer between the stock and the packing\n" +"zone." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:291 -msgid "**Take From Stock**: the products are taken from the available stock of the source location;" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:254 +msgid "The :guilabel:`Operation Type` must also be defined on the rule. This defines which kind of picking is created from the rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:293 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:257 +msgid "If the rule's :guilabel:`Action` is set to :guilabel:`Pull From` or :guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The :guilabel:`Supply Method` defines what happens at the source location:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:296 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:261 +msgid ":guilabel:`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:301 -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*." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:263 +msgid ":guilabel:`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:309 -msgid "What about a full flow?" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:265 +msgid ":guilabel:`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:311 -msgid "Do you remember our Pick - Pack - Ship custom route? Let’s use it to try a full flow with an advanced custom route." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:269 +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." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:314 -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:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:273 +msgid "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:318 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:277 +msgid "Sample full route flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:321 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:279 +msgid "In this example, let's use a custom *Pick - Pack - Ship* route to try a full flow with an advanced custom route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:324 -msgid "**Trigger Another Rule**: When products are needed in Partner Locations/Customers, Delivery Orders are created from WH/Output to fulfill the need." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:282 +msgid "First, a quick look at the route's rules and their supply methods. There are three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply Methods` for each rule are the following:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:332 -msgid "This means that, when a customer orders products, a delivery order is created to fulfill the order." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:285 +msgid ":guilabel:`Take From Stock`: When products are needed in the :guilabel:`WH/Packing Zone`, *picks* (internal transfers from :guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from :guilabel:`WH/Stock` to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:340 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:288 +msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`WH/Output`, *packs* (internal transfers from :guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from :guilabel:`WH/Packing Zone` to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:348 -msgid "To prepare the order, conveyors need products packed at the output area, so an internal transfer is requested from the packing zone." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:291 +msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`Partner Locations/Customers`, *delivery orders* are created from :guilabel:`WH/Output` to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:355 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +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:299 +msgid "This means that, when a customer orders products that have a *pick - pack - ship* route set on it, a delivery order is created to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of the operations created by a pull from transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:307 +msgid "If the source document for multiple tranfers is the same sales order, the status is not the same. The status will be :guilabel:`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 +msgid "View of the transfers' various statuses at the beginning of the process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:315 +msgid "To prepare the delivery order, packed products are needed 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 +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:322 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:363 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +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:370 -msgid "In our case, the product is delivered to the customer when all the rules have been triggered and the transfers done." +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:329 +msgid "As explained in the introduction of the documentation, the last step in the process (for this route, 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 the 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:334 +msgid "In this example, the product is delivered to the customer when all the rules have been triggered and the transfers are done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:None +msgid "View of the transfers' statuses when the route is completed." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies.rst:5 @@ -3196,47 +3922,183 @@ msgid "What is a Putaway Rule?" 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 "A good warehouse implementation makes sure that products automatically move to their appropriate destination location. To make that process easier, Odoo uses *Putaway Rules*. Putaway is the process of taking products from the received shipments and putting them into the appropriate location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:7 -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: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." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:12 -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:17 +msgid "In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> Settings` and activate the :guilabel:`Multi-Step Routes` feature. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:19 -msgid "Setting up a Putaway Rule" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:None +msgid "Activate Multi-Step Routes in Inventory configuration settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:21 -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:26 +msgid "Setting up a putaway rule" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:23 -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:28 +msgid "In some cases, like for a retail shop storing fruits and vegetables, products should be stored in different locations depending on several factors like frequency, size, product category, specific environment needs, and so on." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:25 -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:32 +msgid "In this example, suppose there is one warehouse location, **WH/Stock**, with the following sub-locations:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:31 -msgid "The putaway rules can be defined either per product or per product category." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:35 +msgid "WH/Stock/Pallets" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:36 -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:37 +msgid "WH/Stock/Pallets/PAL1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:38 +msgid "WH/Stock/Pallets/PAL2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:39 +msgid "WH/Stock/Pallets/PAL3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:41 +msgid "WH/Stock/Shelf 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:43 +msgid "WH/Stock/Shelf 2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:45 +msgid "WH/Stock/Shelf 2/Small Refrigerator" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:47 +msgid "WH/Stock/Shelf 3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:49 +msgid "Manage those locations with putaway rules. To create a putaway rule, open the :guilabel:`Inventory` app and go to :menuselection:`Configuration --> Putaway Rules`. Then, click on :guilabel:`Create` and configure a putaway rule that indicated the main location the product will enter before being redirected to the right storage location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:55 +msgid "The putaway rules can be defined either per product/product category and/or package type (the :guilabel:`Packages` setting must be enabled for that). Putaway rules are read sequentially until a match is found." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:59 +msgid "Take the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:61 +msgid "If water (category All/drinks) is received, whatever the package, it will be redirected to WH/Stock/Shelf 2/Small Refrigerator." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:63 +msgid "If orange juice cans, packaged in boxes, are received, they will be redirected to WH/Stock/Shelf 2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:65 +msgid "If water or apple juice bottles, packaged in boxes, are received, they will be redirected to WH/Stock/Shelf 3." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:67 +msgid "If a pallet of lemonade cans are receieved, it will be redirected to WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:None +msgid "Some examples of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:75 +msgid "Using Storage Categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:77 +msgid "A *Storage Category* is an extra location attribute. Storage categories allow the user to define the quantity of products that can be stored in the location and how the location will be selected with putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:84 +msgid "In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> Settings` and activate the :guilabel:`Storage Categories` feature. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:89 +msgid "Create a Storage Category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:91 +msgid "To create a storage category, go to :menuselection:`Inventory --> Configuration --> Storage Categories` and click :guilabel:`Create`. Then, click :guilabel:`Save` and click :guilabel:`Storage Categories` or go to :menuselection:`Configuration --> Storage Categories` to create a new storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:None +msgid "Create Storage Categories inside Odoo Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:100 +msgid "First, click :guilabel:`Create` and type a name for the storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:102 +msgid "Then, there are options to limit the capacity by weight, by product, or by package type. The :guilabel:`Allow New Product` field defines when the location is considered available to store a product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:106 +msgid ":guilabel:`If location is empty`: a product can be added there only if the location is empty." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:107 +msgid ":guilabel:`If products are the same`: a product can be added there only if the same product is already there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:109 +msgid ":guilabel:`Allow mixed products`: several different products can be stored in this location at the same time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:112 +msgid "Once the storage category settings are saved, the storage category can be linked to a location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:None +msgid "When a Storage Category is created, it can be linked to a warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:119 +msgid "Storage categories in putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:121 +msgid "To continue the example from above, apply the \"High Frequency Pallets\" on the PAL1 and PAL2 locations and rework the putaway rules as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:124 +msgid "Assume one pallet of lemonade cans is received:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:126 +msgid "If PAL1 and PAL2 are empty, the pallet will be redirected to WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:127 +msgid "If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:128 +msgid "If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:None +msgid "Storage Categories used in a variety of putaway rules." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:3 -msgid "What is a Removal Strategy (FIFO, LIFO, and FEFO)?" +msgid "What is a Removal Strategy (FIFO, LIFO, FEFO, Closest location)?" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:5 -msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products to optimize the distance for the worker, for quality control purposes, or to first move the products with the closest expiration date." +msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products, optimize the distance for the worker, for quality control purposes, or to first move products with the closest expiration date." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:9 @@ -3248,205 +4110,286 @@ msgid "What happens inside the warehouse?" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:16 -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." +msgid "Imagine a generic warehouse plan, with receiving docks and areas, 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 +msgid "Empty stock waiting for deliveries at the docks." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:24 -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." +msgid "Here, vendor trucks unload pallets of goods at the docks. Then, operators scan the products in the receiving area with the reception 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 +msgid "Products entering stock via the receiving area." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:32 -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." +msgid "Next, several orders for the same product are made, but in this example, the goods weren't received on the same day and they don't have the same expiration date. In that situation, logically, sending those with the closest date first is preferred. Depending on the chosen removal strategy, Odoo generates a transfer with the products that fit the settings the best." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:42 -msgid "On the transfer form, you can find the product’s lot/serial number to pick for delivery." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid ":alt: Products being packed at the packing area for delivery, taking expiration dates into\n" +"account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:43 +msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:46 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:49 msgid "First In, First Out (FIFO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:50 -msgid "When using a **First In, First Out** strategy, a demand for some products triggers a removal rule which requests a transfer for the lot/serial number that has entered your stock the first." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:51 +msgid "When using a *First In, First Out* (FIFO) strategy, a demand for some products triggers a removal rule, which requests a transfer for the lot/serial number that has entered the stock first." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:53 -msgid "To be clearer, let’s imagine that you have three lots of nails in your warehouse. Those three have the following lot numbers: 00001, 00002, 00003, each with 5 nails boxes in it. 00001 entered the stock on the 23rd of May, 00002 on the 25th of May, and 00003 on the 1st of June. A customer orders you 6 boxes on the 11th of June. With the *FIFO* strategy selected, a transfer is requested for the five boxes of 00001 and one of the boxes in 00002 because 00001 has entered your stock before the others. The box from 00002 is taken because it has the oldest enter date after 00001." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:54 +msgid "For example, imagine there are three lots of nails in the warehouse. Those three have the following lot numbers: :guilabel:`00001`, :guilabel:`00002`, :guilabel:`00003`, each with five boxes of nails in it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:60 -msgid "So, for every order of a product with the *FIFO* strategy selected, Odoo requests a transfer for the good that has been in your stock for the longest period." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:58 +msgid ":guilabel:`00001` entered the stock on the 23rd of May, :guilabel:`00002` on the 25th of May, and :guilabel:`00003` on the 1st of June. A customer orders six boxes on the 11th of June. With the :abbr:`FIFO (First In, First Out)` removal strategy selected, a transfer is requested for the five boxes of :guilabel:`00001` and one of the boxes in :guilabel:`00002`, because :guilabel:`00001` entered the stock before the others. The box from :guilabel:`00002` is taken next because it has the oldest reception date after :guilabel:`00001`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:65 +msgid "So, for every order of a product with the :abbr:`FIFO (First In, First Out)` strategy selected, Odoo requests a transfer for the products that have been in the stock for the longest period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:69 msgid "Last In, First Out (LIFO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:66 -msgid "The same way as for FIFO, the **Last In, First Out** strategy is based on moving products based on the date they entered the stock. Here, a demand for some products triggers a removal rule that requests a transfer for the lot/serial number that has entered your stock the last." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:70 -msgid "To better understand, let’s imagine three lots of screws in your warehouse. Those three have the following numbers: 10001, 10002, 10003, each with 10 screw boxes in it. 10001 has entered the stock on the 1st of June, 10002 on the 3rd of June, and 10003 on the 6th of June. A customer orders 7 boxes on the 8th of June. With the *LIFO* strategy selected, a transfer is requested for seven boxes of 10003 because that lot is the last one to have entered the stock." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:71 +msgid "Similar to :abbr:`FIFO (First In, First Out)`, the *Last In, First Out* (LIFO) strategy moves products based on the date they entered the stock. Here, a demand for some products triggers a removal rule that requests a transfer for the lot/serial number that has entered the stock most recently." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:76 -msgid "So, basically, for every order of a product with the *LIFO* strategy used, a transfer for the last one to have entered the stock is requested." +msgid "For example, imagine there are three lots of screws in the warehouse. Those three have the following numbers: :guilabel:`10001`, :guilabel:`10002`, and :guilabel:`10003`, each with 10 boxes of screws in it." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:80 -msgid "This strategy is banned in many countries and can lead to only have old or obsolete products in your stock." +msgid ":guilabel:`10001` entered the stock on the 1st of June, :guilabel:`10002` on the 3rd of June, and :guilabel:`10003` on the 6th of June. A customer orders seven boxes on the 8th of June. With the :abbr:`LIFO (Last In, First Out)` removal strategy selected, a transfer is requested for seven boxes of :guilabel:`10003` because that lot is the last one to have entered the stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:84 -msgid "First Expire, First Out (FEFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:86 -msgid "The **First Expire, First Out** strategy is a bit different from the two others. Here, it is the expiration date that is important and not the date the product entered the stock." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:85 +msgid "Basically, for every order of a product with the :abbr:`LIFO (Last In, First Out)` strategy used, a transfer for the last lot to have entered the stock is requested." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:89 -msgid "Let’s imagine three lots of 6-eggs boxes (in this specific case, don’t forget to use :doc:`units of measure <../../management/products/uom>`). Those three have the following numbers: 20001, 20002, and 20003, each with 5 boxes in it. 20001 has entered the stock on the 1st of July and expires on the 15th of July, 20002 on the 2nd and expires on the 14th of July, and 20003 on the 4th and expires on the 21st of July. A customer orders 6 boxes on the 5th of July. With the *FEFO* strategy selected, a transfer is requested for the five boxes of 20002 and one from 20001. The transfer for all the boxes of the lot 20002 is because they have the closest expiration date. The transfer also requests one box from 20001 because it’s the lot that expires the sooner after 20002." +msgid "The :abbr:`LIFO (Last In, First Out)` strategy is banned in many countries and can lead to only having old or obsolete products in the stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:98 -msgid "Then, you can remember that for every order of a product with the *FEFO* strategy, a transfer is requested for the product that has the nearest expiration date from the order date." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:93 +msgid "First Expire, First Out (FEFO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:102 -msgid "Use Removal Strategies" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:95 +msgid "The *First Expired, First Out* (FEFO) strategy is a bit different from the other two removal strategies. For :abbr:`FEFO (First Expired, First Out)`, the expiration date is important, not the date the product entered the stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:104 -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*." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:99 +msgid "For example, imagine there are three lots of six-egg boxes (in this specific case, don't forget to use :doc:`units of measure <../../management/products/uom>`). Those three lots have the following numbers: :guilabel:`20001`, :guilabel:`20002`, and :guilabel:`20003`, each with five boxes in it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:113 -msgid "To work with the *FEFO* strategy, activate the *Expiration Dates* feature." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:103 +msgid ":guilabel:`20001` entered the stock on the 1st of July and expires on the 15th of July, :guilabel:`20002` entered on the 2nd and expires on the 14th of July, and :guilabel:`20003` entered on the 4th and expires on the 21st of July. A customer orders six boxes on the 5th of July. With the :abbr:`FEFO (First Expired, First Out)` strategy selected, a transfer is requested for the five boxes of :guilabel:`20002` and one from :guilabel:`20001`. The transfer for all the boxes in lot :guilabel:`20002` is because they have the closest expiration date. The transfer also requests one box from :guilabel:`20001` because has the next closest expiration date after lot :guilabel:`20002`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:115 -msgid "Next, you need to define your removal strategy, on *Product Categories* via :menuselection:`Inventory --> Configuration --> Product Categories`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:112 +msgid "Basically, for every sales order of a product with the :abbr:`FEFO (First Expired, First Out)` strategy, a transfer is requested for the product that has the nearest expiration date from the order date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:117 +msgid "Closest Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:119 +msgid "The *Closest Location* strategy is completely different from the other removal strategies. It is not related to the date of entry in the warehouse, but rather the location of the product. It is commonly used for products that do not deteriorate with time." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:123 -msgid "FIFO (First In, First Out)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:125 -msgid "As said, a *FIFO* strategy implies that products stocked first move out first. Companies should use that method if they are selling products with short demand cycles, such as clothes, and to ensure they are not stuck with outdated styles in stock." +msgid "The aim is to avoid making the warehouse worker take a long journey to the bottom of the stock when the product is also located at a near location. This method is only available if the :guilabel:`Storage Locations` setting is on. The closest location is actually the one that comes first in the alphabetic order." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:129 -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." +msgid "Use removal strategies" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:137 -msgid "The lot 000001 contains 5 shirts, 000002 contains 3 shirts, and 000003 contains 2. As it can be seen above, 000001 has entered the stock first. Let’s create a sale order of six white shirts to check that products from that lot are the first ones to move out." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:131 +msgid "To differentiate some units from others, the units need to be tracked, either by *lot* or by *serial number*. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Location`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "Features to enable in order to properly use removal strategies." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:141 -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." +msgid "To work with the :abbr:`FEFO (First Expired, First Out)` strategy, also activate the :guilabel:`Expiration Dates` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:149 -msgid "LIFO (Last In, First Out)" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:144 +msgid "Next, go to :menuselection:`Inventory --> Configuration --> Product Categories` to define the removal strategy on a product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:151 -msgid "With a *LIFO* strategy, that’s quite the opposite. In fact, the products that are brought the last move out the first. It is mostly used in case of products without a shelf life." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "Force removal strategy set up as first in first out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:152 +msgid "FIFO (First In, First Out)" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:154 -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*." +msgid "As explained, a :abbr:`FIFO (First In, First Out)` removal strategy implies that products stocked first move out first. Companies should use this method if they are selling products with short demand cycles, such as clothes, and to ensure they are not stuck with outdated styles in stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:162 -msgid "Now, create a sale order for 4 white shirts and check that the reserved products are from lots 000003 and 000002." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:158 +msgid "In this example, there are three lots of white shirts. The shirts are from the :guilabel:`All/Clothes` category, where *FIFO* is set as the removal strategy. In the stock location (:guilabel:`WH/Stock`), the user can find the three lots available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:170 -msgid "Don’t forget that the *LIFO* strategy is banned in many countries!" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "View of the white shirt lots inventory valuation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:173 -msgid "FEFO (First Expiry, First Out)" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:166 +msgid "Lot :guilabel:`000001` contains five shirts, :guilabel:`000002` contains three shirts, and :guilabel:`000003` contains two shirts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:175 -msgid "With the *FEFO* strategy, the way products are picked is not based on the reception date. In this particular case, they are dispatched according to their expiration date." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:169 +msgid "As seen above, :guilabel:`000001` entered the stock first. Now, create a sales order of six white shirts to check that those products from lot :guilabel:`000001` are the first ones to move out." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:179 -msgid "To have more information about Expiration date, please have a look at :doc:`the related doc <../../management/lots_serial_numbers/expiration_dates>`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:172 +msgid "On the delivery order linked to the picking, the oldest lot numbers should have been reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "Two lots being reserved for a sales order with the FIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:180 +msgid "LIFO (Last In, First Out)" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:182 -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`." +msgid "With a *LIFO* strategy, that's quite the opposite. In fact, the products that are received last move out first. :abbr:`LIFO (Last In, First Out)` is mostly used for products without a shelf life." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:190 -msgid "Lots are picked based on their removal date, from earliest to latest. Lots without a removal date defined are picked after lots with removal dates." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:185 +msgid "In this example, let's use the white shirts again to test the :abbr:`LIFO (Last In, First Out)` strategy. First, open the product category via :menuselection:`Inventory --> Configuration --> Product Categories` and change the removal strategy to :abbr:`LIFO (Last In, First Out)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:194 -msgid "Other dates are for informational and reporting purposes only. If not removed from the stock, lots that are past the expiration dates may still be picked for delivery orders!" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "Last in first out strategy set up as forced removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:197 -msgid "To use the *FEFO* strategy, once again go to :menuselection:`Inventory --> Configuration --> Product Categories` and choose *FEFO* as the *Force Removal Strategy*." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:193 +msgid "Then, create a sales order for four white shirts and check that the reserved products are from lots :guilabel:`000003` and :guilabel:`000002`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "Two lots being reserved for sale with the LIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:201 +msgid "Don't forget that the :abbr:`LIFO (Last In, First Out)` strategy is banned in many countries!" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:204 -msgid "For this particular case, let’s use hand cream. As usual, we have three lots of them." +msgid "FEFO (First Expired, First Out)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:207 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:206 +msgid "With the :abbr:`FEFO (First Expired, First Out)` removal strategy, the way products are picked is not based on the reception date. In this particular case, they are dispatched according to their expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211 +msgid "For have more information about expiration dates, please have a look at :doc:`the related doc <../../management/lots_serial_numbers/expiration_dates>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:214 +msgid "By activating the :guilabel:`Expiration Dates` feature, it becomes possible to define different expiration dates on the serial/lot numbers that will be used in :abbr:`FEFO (First Expired, First Out)`. These expiration dates can be set by going to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "View of the removal date for 0000001." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:223 +msgid "Lots are picked based on their removal date, from earliest to latest. Lots without a removal date defined are picked after lots with removal dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:227 +msgid "Other dates are for informational and reporting purposes only. If not removed from the stock, lots that are past the expiration dates may still be picked for delivery orders!" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:230 +msgid "To use the :abbr:`FEFO (First Expired, First Out)` strategy, go to :menuselection:`Inventory --> Configuration --> Product Categories` and set :abbr:`FEFO (First Expired, First Out)` in the :guilabel:`Force Removal Strategy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "View of the FEFO strategy being set up as forced removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:238 +msgid "For this particular case, the stock has hand cream. There are three lots of them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 msgid "**Lot / Serial No**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:207 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 msgid "**Product**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:207 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 msgid "**Expiration Date**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 msgid "0000001" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:209 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:213 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 msgid "Hand Cream" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 msgid "09/30/2019" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 msgid "0000002" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 msgid "11/30/2019" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:213 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 msgid "0000003" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:213 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 msgid "10/31/2019" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:216 -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." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:250 +msgid "When a sales order for 25 units of Hand Cream is created, Odoo automatically reserves the lots with the closest expiration date, :guilabel:`0000001` and :guilabel:`0000003`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:None +msgid "Two hand cream lots reserved for sell with the FEFO strategy." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping.rst:5 @@ -4127,124 +5070,160 @@ msgstr "" msgid "Manufacturing several different products simultaneously at the same work center is a common issue for manufacturing companies. Although in practice, employees can manufacture the goods at another work center instead of waiting for one to be available, it's not always simple to have visibility on which work center is busy and plan resources accordingly in real-time." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:10 msgid "With Odoo, you can configure alternative work centers to solve this issue. This automatically checks which work center is busy and which equivalent ones are free, and schedules orders and maintenance accordingly." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:14 msgid "This way, your process becomes more efficient, as work center utilisation is optimised." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:19 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:17 msgid "Configure your Work Centers" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:21 -msgid "First, go to the :menuselection:`Manufacturing app --> Configuration --> Settings`. Then, enable the Work Orders feature and hit save." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:19 +msgid "First, go to the :menuselection:`Manufacturing app --> Configuration --> Settings`. Then, enable the :guilabel:`Work Orders` feature and hit :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:29 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:None +msgid "Work order settings ticked in Odoo Manufacturing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:26 msgid "Now, go to :menuselection:`Configuration --> Work Centers` and create two new work centers. Add the second work center as an alternative to the first one and vice versa." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:38 -msgid "Next, go to :menuselection:`Products --> Bills of Materials`, choose your product, and add these work centers to the operations of your BOM." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:None +msgid "Create a secondary work center as an alternate to the first." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:33 +msgid "Next, go to :menuselection:`Products --> Bills of Materials`, choose your product, and add these work centers to the operations of your :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:None +msgid "Add work centers to Bill of Materials operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:41 msgid "Create your Work Orders" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:50 -msgid "Now that everything is configured, you can create your *Work Orders*. Go to :menuselection:`Operations --> Manufacturing Orders`, and hit **Create**. There, add your product to your manufacturing order and plan it. You can then retrieve them from the Work Orders list view, under Operations > Work Orders." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:43 +msgid "Now that everything is configured, you can create your *Work Orders*." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:55 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:45 +msgid "Go to :menuselection:`Operations --> Manufacturing Orders`, and hit :guilabel:`Create`. There, add your product to your manufacturing order and plan it. You can then retrieve them from the :guilabel:`Work Orders` list view, under :menuselection:`Operations > Work Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:49 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, as shown below." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:64 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:None +msgid "Work order creation and scheduling." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:57 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" 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 make or deliver a finished product. Additionally, it can also include various operations and individual step guidelines needed to complete a production process." +msgid "A *Bill of Materials* (or *BoM* for short) is a document that defines the quantity of each component required to make or deliver a finished product. It can also include various operations and the individual step guidelines needed to complete a production process." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:10 -msgid "With Odoo's MRP solution, multiple BOMs can also be linked to each product, so that even product variants can have their *own* tailored BOM." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:9 +msgid "In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so that even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:13 -msgid "This will help you to optimize your manufacturing process and save time as a result." +#: ../../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 save 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 bill of baterials (BoM)" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 -msgid "The simplest BoM set up is one without operations or instructions. In this case, you will manage your production using Manufacturing Orders only." +msgid "The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations or instructions, only components. In this case, the production is solely managed using *Manufacturing Orders*." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:22 -msgid "To create a BoM from the Manufacturing module, go to :menuselection:`Products --> Bills of Materials`. If you click **Create**, the first thing you'll have to do is to specify the final product. For an existing product, simply select it from the list, or create a new one on the spot. Note that if you go through the product form to create your BOM, the product will already be set for you." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:21 +msgid "To create a :abbr:`BoM (Bill of Materials)` from the :guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills of Materials`. Then, click :guilabel:`Create`. Next, specify the :guilabel:`Product`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:27 -msgid "For a standard Bill of Material, keep the default *BoM* type, which is *Manufacture this Product*. Now specify the various components that make up the production of your final product and their respective quantities. You can create components as you go, on the BOM, or create products beforehand, by going to the :menuselection:`Top Menu --> Products --> Create`, and add them later on." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:26 +msgid "A :abbr:`BoM (Bill of Materials)` can also be created directly from the product form, in which case the :guilabel:`Product` field is pre-filled." 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:29 +msgid "For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type` to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line` to specify the various components that make up the production of the final product and their respective quantities. New components can be created quickly through the :abbr:`BoM (Bill of Materials)`, or can be created beforehand in :menuselection:`Manufacturing --> Products --> Products --> Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:None +msgid "Set up a Bill of Materials." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:41 -msgid "Using the same BoM to describe Variants" +msgid "Specify a bill of materials (BoM) for a product variant" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 -msgid "As suggested above, you can use *BOMs* for specific *Product Variants*. Once the various attributes have been configured on the product form, there are two ways to configure the appropriate BoM for the respective product combination." +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:47 -msgid "Either create one BoM per variant, by specifying the Product Variant in the dedicated field below the product name. Or use one BOM, that contains all of the components and for each component, indicate which variant it applies to, using the *Apply on Variants* column, as shown below." +msgid "In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, the product's variant attributes must already be configured on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:57 -msgid "Adding Operations" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:50 +msgid "The first method is to create one :abbr:`BoM (Bill of Materials)` per variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the :guilabel:`Product Variant`. The second method is to create one master :abbr:`BoM (Bill of Materials)` that contains all of the components, and specify which variant each component applies to using the :guilabel:`Apply on Variants` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:59 -msgid "You can also add operations to your *BoM*, if you want workers to follow instructions or register time spent. To use this feature, enable the *Work Orders* feature in the *Manufacturing* app settings, as shown below." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:None +msgid "Product Variants in the Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:60 +msgid "Set up operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62 +msgid "Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify instructions for production and register time spent on an operation. To use this feature, first enable the :guilabel:`Work Orders` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:67 -msgid "Each operation is unique as it is always linked to only one BOM. This being said, Operations Operations can be re-used when configuring a new BOM, with the *Copy Existing Operations* feature." +msgid "Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the :guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new operation. In the :guilabel:`Create Operations` box, give the operation a name, specify the :guilabel:`Work Center` and duration settings. Like components, Odoo gives the option to specify a product variant in the :guilabel:`Apply on Variants` field so the operation only applies to that variant. Finally, click :guilabel:`Save & Close`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:74 -msgid "Finally, just like for components, operations can also be variant specific only, as shown below." +msgid "Each operation is unique, as it is always exclusively linked to one :abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing Operations` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:82 -msgid "Adding By-Products" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:None +msgid "Copy Existing Operations feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:84 -msgid "A *by-product* is a product that is produced on top of the main product of a *BoM*. As opposed to the primary product, there can be more than one on a BOM." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:83 +msgid "Add by-products to a bill of materials (BoM)" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87 -msgid "To add *by-products* to a *BoM*, you will first need to enable the by-product feature from the *Manufacturing* app settings." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85 +msgid "A *By-Product* is a residual product that is created during production in addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike the primary 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:93 -msgid "Once the feature is enabled, you can add *by-products* to your *BoMs*. Note that if you have Operations, you'll need to specify in which operation the by-product is produced." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:89 +msgid "To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`By-Products` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:92 +msgid "Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill of Materials)` by clicking on the :guilabel:`Operations` tab and clicking :guilabel:`Add a line`. Then, name the by-product and indicate the :guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM (Bill of Materials)` has configured operations, specify exactly which operation the by-product is produced from in the :guilabel:`Produced in Operation` field. Finally, click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3 @@ -4316,27 +5295,47 @@ msgid "Finally, note that if there were any Operations in the Kit BOM, these wou msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3 -msgid "Variants BOM Management" +msgid "Managing BoMs for product variants" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:5 -msgid "Odoo allows you to use one bill of materials for multiple variants of the same product. To activate variants, simply go to :menuselection:`Configuration --> Settings --> Variants`." +msgid "Odoo allows one bill of materials (BoM) to be used for multiple variants of the same product. Having a consolidated BoM for a product with variants saves time by preventing the need to manage multiple BoMs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:10 +msgid "Activate product variants" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:12 -msgid "You will then be able to specify which BOM component lines are to be used in the manufacture of each product variant. You may specify multiple variants for each line. If no variant is specified on a component line, then this component will be used in the BOM of all variants." +msgid "To activate variants, simply navigate to :menuselection:`Inventory --> Configuration --> Settings --> Products`, and then enable the :guilabel:`Variants` option. After that, click :guilabel:`Save` to apply the setting. For more information on configuring product variants, refer to :doc:`this page <../../../sales/sales/products_prices/products/variants>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:17 -msgid "When defining variant BoMs on a line-item-basis, the **Product Variant** field in the main section of the BoM should be left blank as shown below. This field is used when creating a BoM for one specific variant of a product only." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:None +msgid "Selecting \"Variants\" from Inventory app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:26 -msgid "Note that the same principle applies for the configuration of operations." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:22 +msgid "Apply BoM components to product variants" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:32 -msgid "And for the production of by-products." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:24 +msgid "Next, create a new BoM or edit an existing one by going to :menuselection:`Manufacturing --> Products --> Bills of Materials`. Then, click :guilabel:`Edit`. The :guilabel:`Apply on Variants` option to assign components to specific product variants on the BoM is available once the :guilabel:`Variants` setting is activated from the :guilabel:`Inventory` application. If the :guilabel:`Apply on Variants` field is not immediately visible, activate it from the additional options menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:None +msgid "\"Apply on Variants\" option on the additional options menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:35 +msgid "Each component can be assigned to multiple variants. Components with no variants specified are used in every variant of the product. The same principle applies when configuring operations and by-products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:39 +msgid "When defining variant BoMs by component assignment, the :guilabel:`Product Variant` field in the main section of the BoM should be left blank, as shown below. This field is used only when creating a BoM specifically for one product variant." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:None +msgid "Applying components to multiple variants." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:3 @@ -4735,6 +5734,10 @@ 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 +msgid "Reporting dashboard in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:22 msgid "While the data initially presented is useful, there are several tools and features you can use to get even more insights on your purchases." msgstr "" @@ -4775,6 +5778,10 @@ 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 +msgid "Reporting filters in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:59 msgid "Add custom filters" msgstr "" @@ -4783,6 +5790,10 @@ 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 +msgid "Custom reporting filter in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:74 msgid "To avoid having to recreate custom filters every time, save them by clicking on :menuselection:`Favorites --> Save current search --> Save`. The customized search filter can then be accessed by clicking on *Favorites* or can even be set as the default filter when you open the reporting dashboard." msgstr "" @@ -4795,6 +5806,10 @@ 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 +msgid "Switch reporting view in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:92 msgid "Visualize your data" msgstr "" @@ -4803,6 +5818,10 @@ 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 +msgid "Reporting graph view in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:102 msgid "For bar and line charts, the selected measure is your y-axis, and the first group you select is used to create the x-axis. Adding more group adds additional lines (line chart) or transforms your bar chart into a stacked bar chart. For pie charts, the more groups you select, the more slices are displayed." msgstr "" @@ -4815,6 +5834,10 @@ 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 +msgid "Pivot table view in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:121 msgid "You can insert your pivot table's data directly in the Spreadsheet app or export it as an Excel file." msgstr "" @@ -4847,6 +5870,10 @@ 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 +msgid "Enable purchase agreements in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:30 msgid "Configure or create new types of purchase agreements" msgstr "" @@ -4871,6 +5898,10 @@ 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 +msgid "Configure purchase agreements types in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:59 msgid "Set up a blanket order" msgstr "" @@ -4883,6 +5914,10 @@ 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 +msgid "Set up a blanket order in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:73 msgid "You can also write any *Terms and Conditions* at the bottom of the agreement. Once you are satisfied with your blanket order, click on *Confirm*. Its status then changes from *Draft* to *Ongoing* and it's ready to be used." msgstr "" @@ -4899,6 +5934,10 @@ 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 +msgid "Create new quotations for an ongoing blanket order in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:93 msgid "You can also create a *Request for Quotation* the usual way and then link it to an existing *Blanket Order*." msgstr "" @@ -4911,6 +5950,10 @@ 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 +msgid "Blanket order added to product configuration in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:108 msgid "Set up a call for tenders" msgstr "" @@ -4927,6 +5970,10 @@ 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 +msgid "Set up a call for tenders in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:126 msgid "Requests quotations from the call for tenders" msgstr "" @@ -4935,14 +5982,26 @@ 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 +msgid "Request a quotation from a call for tenders in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:138 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 +msgid "Validate a call for tenders and view all quotations in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:146 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 +msgid "Confirm an order in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:3 msgid "Control and know when vendor bills should be paid" msgstr "" @@ -4963,6 +6022,11 @@ 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 +msgid "Vendor bills default control setting for new products in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:23 msgid "By selecting *On ordered quantities*, you can create a vendor bill as soon as you confirm an order. The quantities mentioned in the purchase order are used to generate the draft bill." msgstr "" @@ -4971,6 +6035,10 @@ 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 +msgid "No invoiceable line error message in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:36 msgid "Change a specific product's control policy" msgstr "" @@ -4987,6 +6055,10 @@ 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 +msgid "Purchase order billing status in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:56 msgid "Below you can find a list of the different *Billing Status*, and when they are displayed, depending on the products' bill control policy." msgstr "" @@ -5051,6 +6123,10 @@ 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 +msgid "3-way-matching setting in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:81 msgid "3-way matching is intended to work with the bill control policy set to *On received quantities*." msgstr "" @@ -5063,6 +6139,10 @@ 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 +msgid "Should Be Paid field under a vendor bill in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:93 msgid "As you can't create a bill until you have received your products - and if you haven't received all of them, Odoo only includes the products you have received in the draft bill - the *Should Be Paid* status is set to *Yes* when you create one." msgstr "" @@ -5075,6 +6155,10 @@ 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 +msgid "Paid bill in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:109 msgid "The *Should Be Paid* status is set automatically by Odoo. However, you can change the status manually when you are viewing a bill in edit mode." msgstr "" @@ -5099,6 +6183,10 @@ msgstr "" msgid "Open or create a product with its *Product Type* set to *Storable Product*." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None +msgid "Set the product type in Odoo" +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." msgstr "" @@ -5107,6 +6195,10 @@ msgstr "" 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." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None +msgid "Add vendor to a product 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`" msgstr "" @@ -5115,6 +6207,10 @@ msgstr "" 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*." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None +msgid "Choose product routes in Odoo" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:50 msgid "Set up your reordering rule" msgstr "" @@ -5123,6 +6219,10 @@ msgstr "" msgid "Open your product and click on the *Reordering Rules* button." 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*." msgstr "" @@ -5151,6 +6251,10 @@ msgstr "" 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." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:None +msgid "Create a reordering rule in Odoo" +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." msgstr "" @@ -5183,6 +6287,10 @@ 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 +msgid "Enable the units of measure option in Odoo Sales" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:29 msgid "Specify sales and purchase units of measure" msgstr "" @@ -5207,6 +6315,10 @@ 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 +msgid "Configure a product's units of measure in Odoo" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:56 msgid "Create new units of measure and units of measure categories" msgstr "" @@ -5223,6 +6335,10 @@ 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 +msgid "Create a new units of measure category in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:73 msgid "The next step is to create the two units of measures. To do so, go to :menuselection:`Configuration --> Units of Measure`." msgstr "" @@ -5235,6 +6351,10 @@ 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 +msgid "Create a new reference unit of measure in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:89 msgid "If you use a *Rounding Precision* inferior to 0.01, a warning message might appear stating that it is higher than the *Decimal Accuracy* and that it might cause inconsistencies. If you wish to use a *Rounding Precision* lower than 0.01, first activate the :ref:`developer mode `, then go to :menuselection:`Settings --> Technical --> Database Structure --> Decimal Accuracy`, select *Product Unit of Measure* and edit *Digits* accordingly. For example, if you want to use a rounding precision of 0.00001, set *Digits* to 5." msgstr "" @@ -5255,6 +6375,14 @@ msgstr "" msgid "For your curtain roll, the ratio should be set to 100." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:None +msgid "Create a second unit of measure in Odoo Purchase" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:112 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 +msgid "Set a product's units of measure using your own units in Odoo Purchase" +msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index f91a66890..2ef5b7b33 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-09-01 15:11+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,6 +49,14 @@ msgstr "" msgid "Let’s consider the example below:" msgstr "" +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None +msgid "Metrics in Odoo Marketing Automation" +msgstr "" + #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:19 msgid "The *Target* - business object - is *Lead/Opportunity* and was narrowed down to the ones whose *Tag Name* contain the description “Product”, and have an email address set." msgstr "" @@ -129,6 +137,10 @@ 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 +msgid "GSM7 in Odoo SMS Marketing" +msgstr "" + #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:25 msgid "**UNICODE** is the format applied if a special character, that *is not* in the GSM7 list, is used. Limit per SMS: 70 characters." msgstr "" @@ -153,6 +165,12 @@ msgstr "" msgid "The number of SMSs a message represents will be always available to you in your database." msgstr "" +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None +msgid "SMS pricing and FAQ Odoo SMS Marketing" +msgstr "" + #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:51 msgid "How do I buy credits?" msgstr "" @@ -166,7 +184,7 @@ msgid "Or go to :menuselection:`Settings --> View my Services`." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:67 -msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." +msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:72 @@ -297,6 +315,10 @@ msgstr "" msgid "When creating your survey, choose a *Title* and *Category*. The *Category* field is used to know in which context the survey is being conducted, as different applications might use it for different purposes such as recruitment, certification, or employee appraisal." msgstr "" +#: ../../content/applications/marketing/surveys/overview/create.rst:None +msgid "Form view of a survey with a title and category being chosen in Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/create.rst:22 msgid "Tab: Questions" msgstr "" @@ -325,6 +347,10 @@ msgstr "" msgid "*Matrix Type*: choose if you would like to have one or multiple choices per row." msgstr "" +#: ../../content/applications/marketing/surveys/overview/create.rst:None +msgid "Sections and questions view of a survey in Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/create.rst:44 msgid "Tab: Description" msgstr "" @@ -333,6 +359,10 @@ msgstr "" msgid "Write a *Description* to be displayed under the title of the survey's homepage." msgstr "" +#: ../../content/applications/marketing/surveys/overview/create.rst:None +msgid "Frontend of a survey showing the title and description of a survey for Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/create.rst:53 msgid "Click on *Edit* to personalize your pages with the website builder." msgstr "" @@ -345,6 +375,10 @@ msgstr "" msgid "Under the tab *Options*, choose the *Layout* of your questions. If choosing *One page per section* or *One page per question*, an option *Back Button* becomes available, which allows the user to go back pages." msgstr "" +#: ../../content/applications/marketing/surveys/overview/create.rst:None +msgid "Form view of a survey emphasizing the layout feature under options in Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/create.rst:67 msgid "Test and share the survey" msgstr "" @@ -357,6 +391,10 @@ msgstr "" msgid "By default, a filter *Except Test Entries* is applied to keep the list of entries clean with only real participants." msgstr "" +#: ../../content/applications/marketing/surveys/overview/create.rst:None +msgid "View list of the participations of a survey in Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/create.rst:79 msgid "Another way to access detailed answers is by going to :menuselection:`Participations --> Participations`." msgstr "" @@ -365,6 +403,10 @@ msgstr "" msgid "Click on *See results* to be redirected to an analytical page." msgstr "" +#: ../../content/applications/marketing/surveys/overview/create.rst:None +msgid "View of an analytical page for Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/create.rst:87 #: ../../content/applications/marketing/surveys/overview/time_random.rst:34 msgid ":doc:`scoring`" @@ -387,14 +429,27 @@ msgstr "" msgid "On your survey’s form, click on *Add a question* and, under the tab *Options*, choose between *Scoring with answers at the end* or *Scoring without answers at the end*. Now, on your question’s form, set the right answer and score." msgstr "" +#: ../../content/applications/marketing/surveys/overview/scoring.rst:None +msgid "Form view of a survey showing a list of answers in Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/scoring.rst:17 msgid "Set the percentage score the user needs to achieve to have successfully taken the survey. If enabling *Certificate*, choose its template. The certification is automatically sent by email to the users who successfully finish it." msgstr "" +#: ../../content/applications/marketing/surveys/overview/scoring.rst:None +msgid "Form view of a survey emphasizing the scoring and candidates section in Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/scoring.rst:25 msgid "Enable *Login required* to be able to *Give Badges*. Badges are related to the eLearning section of your website. Besides the logged-in user, visitors of the website that access the page *Courses* can also see the granted badges." msgstr "" +#: ../../content/applications/marketing/surveys/overview/scoring.rst:None +msgid "View of the courses tab emphasizing the latest achievements section on the website for\n" +"Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/time_random.rst:3 msgid "Time and Randomize Questions" msgstr "" @@ -411,6 +466,10 @@ msgstr "" msgid "Set the *Time limit* under the tab *Options*." msgstr "" +#: ../../content/applications/marketing/surveys/overview/time_random.rst:None +msgid "View of a survey form emphasizing the time limit feature in Odoo Surveys" +msgstr "" + #: ../../content/applications/marketing/surveys/overview/time_random.rst:17 msgid "A timer is shown on the pages so the user can keep track of the remaining time. Surveys not \\ submitted by the *Time limit* do not have their answers saved." msgstr "" @@ -426,3 +485,7 @@ msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:27 msgid "To do so, under the tab *Options*, enable *Randomized per section*. Now, under the tab *Questions*, set how many of the questions in that section should be taken into account during the shuffling." msgstr "" + +#: ../../content/applications/marketing/surveys/overview/time_random.rst:None +msgid "View of a survey form emphasizing the random questions count column in Odoo Surveys" +msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 50cedd32e..21db9e94d 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-09-01 15:11+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -68,6 +68,10 @@ msgstr "" msgid "For :guilabel:`What is your goal today?`, select :guilabel:`3rd party integrations`." msgstr "" +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:None +msgid "The Twilio welcome page." +msgstr "" + #: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:34 msgid "If necessary, change the billing country. Finally, click :guilabel:`Get Started with Twilio`." msgstr "" @@ -80,6 +84,10 @@ msgstr "" msgid "To locate the Account SID and Auth Token, go to the Twilio account dashboard. Then, click :guilabel:`Develop` on the sidebar. In the :guilabel:`Account Info` section, locate the :guilabel:`Account SID` and the :guilabel:`Auth Token`. Both of these are needed to connect Twilio to Odoo." msgstr "" +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:None +msgid "The Twilio Account SID and Auth Token can be found uner the Account Info section." +msgstr "" + #: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:49 msgid "Connect Twilio to Odoo" msgstr "" @@ -88,6 +96,10 @@ msgstr "" msgid "Open the Odoo database and go to :menuselection:`Settings --> General Settings --> Discuss`. Check the box next to :guilabel:`Use Twilio ICE servers` and enter the Twilio account's :guilabel:`Account SID` and :guilabel:`Auth Token`. Finally, click :guilabel:`Save` to apply these changes." msgstr "" +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:None +msgid "Enable the \"Use Twilio ICE servers\" option in Odoo General Settings." +msgstr "" + #: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:61 msgid "Define a list of custom ICE servers" msgstr "" @@ -100,10 +112,18 @@ msgstr "" msgid "In :menuselection:`Settings --> General Settings --> Discuss`, click the :guilabel:`ICE Servers` button under :guilabel:`Custom ICE server list`." msgstr "" +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:None +msgid "The \"ICE Servers\" button in Odoo General Settings." +msgstr "" + #: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:74 msgid "Odoo will redirect to the :guilabel:`ICE servers` page. Here you can define your own list of ICE servers." msgstr "" +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:None +msgid "The \"ICE servers\" page in Odoo." +msgstr "" + #: ../../content/applications/productivity/discuss/overview.rst:5 msgid "Overview" msgstr "" @@ -124,6 +144,10 @@ 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 +msgid "View of the preferences page for Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/get_started.rst:23 msgid "By default, the field is set as *Handle by Emails* making messages, notes, and notifications where you were mentioned or that you follow, to be sent through email. By choosing *Handle in Odoo*, they are shown in the *Inbox*." msgstr "" @@ -132,10 +156,18 @@ msgstr "" msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*." msgstr "" +#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +msgid "View of an inbox message and its action options in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/get_started.rst:30 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 +msgid "View of messages marked as todo in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/get_started.rst:38 msgid "Start Chatting" msgstr "" @@ -144,6 +176,11 @@ 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 +msgid "View of the messages under the messaging menu emphasizing the request for push\n" +"notifications for Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/get_started.rst:50 msgid "To stop receiving desktop notifications, reset the notifications settings of your browser." msgstr "" @@ -152,6 +189,10 @@ 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 +msgid "View of discuss’s panel emphasizing the titles channels and direct messages in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/get_started.rst:60 msgid "You can also create :doc:`public and private channels `." msgstr "" @@ -168,6 +209,10 @@ 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 +msgid "View of a couple of chat window messages for Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/get_started.rst:75 msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task’s followers, and secondly on *Employees*. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners." msgstr "" @@ -196,6 +241,10 @@ msgstr "" msgid "Airplane = out of the office" msgstr "" +#: ../../content/applications/productivity/discuss/overview/get_started.rst:None +msgid "View of the contacts’ status for Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/get_started.rst:97 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:65 msgid ":doc:`team_communication`" @@ -221,6 +270,10 @@ 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 +msgid "View of crm leads page emphasizing the activities menu for Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:20 msgid "Plan activities" msgstr "" @@ -229,6 +282,10 @@ 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 +msgid "View of crm leads and the option to schedule an activity for Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:31 msgid "Set your activity types" msgstr "" @@ -237,6 +294,10 @@ 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 +msgid "View of the settings page emphasizing the menu activity types for Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:42 msgid "If you need to create an activity type with an available calendar, make sure to create it with an *Action to Perform* set as *Meeting*." msgstr "" @@ -249,10 +310,20 @@ 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 +msgid "View of an activity type form emphasizing the field recommended next activities for Odoo\n" +"Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:55 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 +msgid "View of an activity being schedule emphasizing the recommended activities field being\n" +"shown for Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:115 msgid ":doc:`get_started`" @@ -274,6 +345,10 @@ 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 +msgid "View of discuss’s sidebar and a channel being created in Odo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:21 msgid "A public channel is best used when many employees need to access information (such as company announcements), whereas a private channel could be used whenever information should be limited to specific groups (such as a specific department)." msgstr "" @@ -286,6 +361,10 @@ 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 +msgid "View of a channel’s settings form in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:36 msgid "Privacy and Members" msgstr "" @@ -298,6 +377,10 @@ 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 +msgid "View of Discuss’ sidebar emphasizing the option to invite members in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:49 msgid "For *Selected group of users*, the option *Auto Subscribe Groups* automatically add its members as followers. In other words, while *Authorized Groups* limits which users can access the channel, *Auto Subscribe Groups* automatically adds the user as a member as long as they are part of the group." msgstr "" @@ -314,6 +397,10 @@ 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 +msgid "View of a message with a pending moderation status in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:66 msgid "Under the *Moderation* tab choose as many moderators as you need, and if you would like them to receive an *Automatic notification*." msgstr "" @@ -322,10 +409,18 @@ msgstr "" msgid "Mark *Send guidelines to new subscribers* to automatically send instructions to newcomers." msgstr "" +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +msgid "View of a channel’s settings form emphasizing the tab moderation in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:73 msgid "Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* messages." msgstr "" +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:None +msgid "View of a message to be moderated in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:80 msgid "Members of a mailing channel receive messages through email regardless of their :doc:`notification preference `." msgstr "" @@ -334,6 +429,10 @@ 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 +msgid "View of a channel’s setting form emphasizing the ban Lists menu in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:91 msgid "Quick search bar" msgstr "" @@ -342,6 +441,10 @@ 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 +msgid "View of the Discuss’ sidebar emphasizing the quick search bar in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:103 msgid "Finding channels" msgstr "" @@ -354,6 +457,10 @@ 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 +msgid "View of a channel being searched through filters in Odoo Discuss" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:116 msgid ":doc:`plan_activities`" msgstr "" @@ -497,7 +604,7 @@ msgid "A computer or tablet with an up-to-date web browser" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:17 -msgid "A running SaaS or Odoo instance with the Point of Sale and IoT apps installed" +msgid "A running Odoo Online or Odoo instance with the Point of Sale and IoT apps installed" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:20 @@ -541,18 +648,18 @@ msgid "**Scale**: Connect your scale and power it on." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:51 -msgid "**Customer Display**: Connect a monitor to the IoT Box using an HDMI cable. You can also access the Customer Display from any other computer by accessing the IoT Box homepage and clicking on the *POS Display* button." +msgid "**Customer Display**: Connect a screen to the IoT Box to display the PoS order. Please refer to :doc:`/applications/productivity/iot/devices/screen`." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:56 +#: ../../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 `." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:60 +#: ../../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." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:68 +#: ../../content/applications/productivity/iot/config/pos.rst:67 msgid "Set up is done, you can launch a new PoS Session." msgstr "" @@ -712,6 +819,7 @@ msgstr "" #: ../../content/applications/productivity/iot/devices/footswitch.rst:13 #: ../../content/applications/productivity/iot/devices/printer.rst:11 #: ../../content/applications/productivity/iot/devices/scale.rst:10 +#: ../../content/applications/productivity/iot/devices/screen.rst:18 msgid "Connection" msgstr "" @@ -948,10 +1056,18 @@ msgstr "" 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." msgstr "" +#: ../../content/applications/productivity/iot/devices/scale.rst:None +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." msgstr "" +#: ../../content/applications/productivity/iot/devices/scale.rst:None +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 "" @@ -960,14 +1076,139 @@ msgstr "" 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." msgstr "" +#: ../../content/applications/productivity/iot/devices/scale.rst:None +msgid "View of the IoT box feature inside of the PoS settings." +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." msgstr "" +#: ../../content/applications/productivity/iot/devices/scale.rst:None +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." msgstr "" +#: ../../content/applications/productivity/iot/devices/scale.rst:None +msgid "Electronic Scale dashboard view when no items are being weighed." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:3 +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." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:None +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." +msgstr "" + +#: ../../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:25 +msgid "IoT Box model 4" +msgstr "" + +#: ../../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 usage below)." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:30 +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." +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." +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." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:43 +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 +msgid "The default \"POS Client Display\" screen that appears when a screen display is successfully\n" +"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." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:None +msgid "An example of a screen display name shown on the IoT Box homepage." +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." +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:66 +msgid "Usage" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:69 +msgid "Show Point of Sales orders to customers" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:71 +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:75 +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." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:82 +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." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:0 +msgid "The \"screen\" icon on the Point of Sale display shows the connection status with the screen." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:89 +msgid "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are performed on the order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:None +msgid "An example of a PoS order on a screen display." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:97 +msgid "Display a website" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:99 +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." +msgstr "" + #: ../../content/applications/productivity/mail_plugins.rst:5 msgid "Mail Plugins" msgstr "" @@ -1074,14 +1315,26 @@ msgstr "" msgid "Click on *Publish* then *Deploy from manifest...*" msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +msgid "Deploying from manifest the Gmail Plugin from the Apps Script project" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/gmail.rst:35 msgid "Make sure you are using the legacy editor; otherwise the *Deploy from manifest* functionality may not be available." msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +msgid "Using the legacy editor in the Gmail Plugin Apps Script project" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/gmail.rst:42 msgid "Click on *Install add-on*. A \"Deployment installed\" notification should appear. You can then click on *Close*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +msgid "Installing the Gmail Plugin from the Apps Script project" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/gmail.rst:52 msgid "Configure your Gmail mailbox" msgstr "" @@ -1090,19 +1343,36 @@ msgstr "" msgid "Open any email in your Gmail mailbox. On the right-side panel, click on the Odoo icon and then *Authorize Access*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +msgid "Authorizing access to the Gmail Plugin" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/gmail.rst:61 msgid "Choose the right Google account." msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +msgid "Choosing your Google account" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/gmail.rst:67 msgid "Allow the Gmail Plugin to access some of your data." msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +msgid "Allowing the Gmail Plugin to access Google data" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/gmail.rst:73 #: ../../content/applications/productivity/mail_plugins/outlook.rst:68 msgid "The right-side panel can now display **Company Insights**. At the bottom, click on *Login*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Logging in your Odoo database" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/gmail.rst:80 #: ../../content/applications/productivity/mail_plugins/outlook.rst:75 msgid "Only a limited amount of *Company Insights* (*Lead Enrichment*) requests are available as a trial. This feature requires :ref:`prepaid credits `." @@ -1113,6 +1383,11 @@ msgstr "" msgid "Enter your Odoo database URL and click on *Login*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Entering your Odoo database URL" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/gmail.rst:89 #: ../../content/applications/productivity/mail_plugins/outlook.rst:105 msgid "If you aren't logged into your database, enter your credentials." @@ -1122,6 +1397,10 @@ msgstr "" msgid "Click on *Allow* to let the Gmail Plugin connect to your database." msgstr "" +#: ../../content/applications/productivity/mail_plugins/gmail.rst:0 +msgid "Allowing the Gmail Plugin to connect to a database" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:3 msgid "Outlook Plugin" msgstr "" @@ -1142,22 +1421,42 @@ msgstr "" msgid "Click on the *More actions* button and select *Get Add-ins*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "More actions button in Outlook" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:31 msgid "Select the *My add-ins* tab." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "My add-ins in Outlook" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:37 msgid "Under *Custom add-ins*, click on *+ Add a custom add-in*, and then on *Add from URL...*" msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Custom add-ins in Outlook" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:43 msgid "Enter the following URL `https://download.odoo.com/plugins/v15/outlook/manifest.xml` and press *OK*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Entering the add-in URL in Outlook" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:50 msgid "Read the warning and click on *Install*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Custom add-in installation warning in Outlook" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:59 msgid "Connect your database" msgstr "" @@ -1166,6 +1465,10 @@ msgstr "" msgid "Open any email in your Outlook mailbox, click on the *More actions* button, and select *Odoo for Outlook*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Odoo for Outlook add-in button" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:79 msgid "If, after a short while, the panel is still empty, it is possible that your browser cookie settings prevented it from loading. Note that these settings also change if you are in \"Incognito\" mode on your browser." msgstr "" @@ -1186,10 +1489,18 @@ msgstr "" msgid "Click on *Allow* to open the pop-up window." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "New window pop-up warning" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:107 msgid "Click on *Allow* to let the Outlook Plugin connect to your database." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Allowing the Outlook Plugin to connect to a database" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:116 msgid "Add a shortcut to the plugin" msgstr "" @@ -1202,10 +1513,19 @@ msgstr "" msgid "In your Outlook mailbox, click on *Settings*, then on *View all Outlook settings*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Viewing all Outlook settings" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:127 msgid "Select *Customize actions* under *Mail*, click on *Odoo for Outlook*, and then *Save*." msgstr "" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Odoo for Outlook customized action" +msgstr "" + #: ../../content/applications/productivity/mail_plugins/outlook.rst:133 msgid "Open any email; the shortcut should be displayed." msgstr "" @@ -1214,43 +1534,43 @@ msgstr "" msgid "Studio" msgstr "" -#: ../../content/applications/productivity/studio.rst:16 +#: ../../content/applications/productivity/studio.rst:17 msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, on any app, add or modify:" msgstr "" -#: ../../content/applications/productivity/studio.rst:19 +#: ../../content/applications/productivity/studio.rst:20 msgid ":doc:`Fields `" msgstr "" -#: ../../content/applications/productivity/studio.rst:20 +#: ../../content/applications/productivity/studio.rst:21 msgid ":doc:`Views `" msgstr "" -#: ../../content/applications/productivity/studio.rst:21 +#: ../../content/applications/productivity/studio.rst:22 msgid ":doc:`Models `" msgstr "" -#: ../../content/applications/productivity/studio.rst:22 +#: ../../content/applications/productivity/studio.rst:23 msgid ":doc:`Automated actions `" msgstr "" -#: ../../content/applications/productivity/studio.rst:23 -msgid "PDF reports" -msgstr "" - #: ../../content/applications/productivity/studio.rst:24 -msgid "Approval rules" +msgid ":doc:`PDF reports `" msgstr "" #: ../../content/applications/productivity/studio.rst:25 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:26 msgid "Security rules" msgstr "" -#: ../../content/applications/productivity/studio.rst:27 +#: ../../content/applications/productivity/studio.rst:28 msgid "Or you can :doc:`build an app from scratch `." msgstr "" -#: ../../content/applications/productivity/studio.rst:30 +#: ../../content/applications/productivity/studio.rst:31 msgid "`Odoo Tutorials: Studio `_" msgstr "" @@ -1270,6 +1590,10 @@ msgstr "" msgid "For every automated action you create, the following elements should be defined: the :ref:`studio/automated-actions/model`, the :ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-actions/apply-on`, and the :ref:`studio/automated-actions/action`." msgstr "" +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of an automated action on the Subscription model" +msgstr "" + #: ../../content/applications/productivity/studio/automated_actions.rst:25 msgid "Model" msgstr "" @@ -1318,6 +1642,10 @@ msgstr "" msgid "If you want the automated action to happen when an email address is set on a contact, define the :guilabel:`Before Update Domain` to `Email is not set`, and the :guilabel:`Apply on` domain to `Email is set`." msgstr "" +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of an On Update trigger" +msgstr "" + #: ../../content/applications/productivity/studio/automated_actions.rst:72 msgid "On Creation & Update" msgstr "" @@ -1366,6 +1694,10 @@ msgstr "" msgid "If you want to send a reminder email 30 minutes before the start of a calendar event, select the :guilabel:`Start (Calendar Event)` under :guilabel:`Trigger Date` and set the :guilabel:`Delay after trigger date` to **-30** :guilabel:`Minutes`." msgstr "" +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Based on Timed Condition trigger" +msgstr "" + #: ../../content/applications/productivity/studio/automated_actions.rst:121 msgid "By default, the scheduler checks for trigger dates every 4 hours." msgstr "" @@ -1430,6 +1762,10 @@ msgstr "" msgid "If an automated action creates a new task in a project, you can assign it to a specific user by setting the :guilabel:`Field` to :guilabel:`Responsible User (Project)`, the :guilabel:`Evaluation Type` to :guilabel:`Reference`, and the :guilabel:`Record` to a specific user." msgstr "" +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Create a new Record action" +msgstr "" + #: ../../content/applications/productivity/studio/automated_actions.rst:181 msgid ":guilabel:`Python expression`: used to dynamically define the newly created record’s value for a field using Python code in the :guilabel:`Value` column." msgstr "" @@ -1482,6 +1818,10 @@ msgstr "" msgid "After a lead is turned into an opportunity, you want your automated action to set up a call for the user responsible for the lead. To do so, set the :guilabel:`Activity` to :guilabel:`Call` and set the :guilabel:`Activity User Type` to :guilabel:`Generic User From Record`." msgstr "" +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Create Next Activity action" +msgstr "" + #: ../../content/applications/productivity/studio/automated_actions.rst:243 msgid "Send SMS Text Message" msgstr "" @@ -1565,6 +1905,10 @@ msgstr "" msgid ":guilabel:`URL`: the value becomes a clickable URL." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:66 msgid "Multiline Text (`text`)" msgstr "" @@ -1573,6 +1917,10 @@ msgstr "" msgid "The :guilabel:`Multiline Text` field is used for longer text containing any type of character. Two text lines are displayed on the UI when filling out the field." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:82 msgid "Integer (`integer`)" msgstr "" @@ -1594,6 +1942,10 @@ msgstr "" msgid ":guilabel:`Handle`: displays a drag handle icon to order records manually in :ref:`List view `." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:103 msgid "Decimal (`float`)" msgstr "" @@ -1622,6 +1974,10 @@ msgstr "" msgid ":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum of 59 minutes." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:131 msgid "Monetary (`monetary`)" msgstr "" @@ -1634,6 +1990,10 @@ msgstr "" msgid "When you first add a :guilabel:`Monetary` field, you are prompted to add a :guilabel:`Currency` field if none exists already on the model. Odoo offers to add the :guilabel:`Currency` field for you. Once it is added, add the :guilabel:`Monetary` field again." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:149 msgid "Html (`html`)" msgstr "" @@ -1646,6 +2006,10 @@ msgstr "" msgid ":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing raw HTML." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:164 msgid "Date (`date`)" msgstr "" @@ -1658,6 +2022,10 @@ msgstr "" msgid ":guilabel:`Remaining Days`: the remaining number of days before the selected date is displayed (e.g., *In 5 days*), based on the current date." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:180 msgid "Date & Time (`datetime`)" msgstr "" @@ -1674,6 +2042,10 @@ msgstr "" msgid ":guilabel:`Remaining days`: displays the remaining number of days before the selected date (e.g., *In 5 days*), based on the current date and time." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:198 msgid "Checkbox (`boolean`)" msgstr "" @@ -1690,6 +2062,10 @@ msgstr "" msgid ":guilabel:`Toggle`: displays a toggle button. The widget works without switching to the edit mode." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:215 msgid "Selection (`selection`)" msgstr "" @@ -1715,6 +2091,10 @@ msgstr "" msgid "By default, radio buttons are organized vertically. Tick :guilabel:`display horizontally` to switch the way they are displayed." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:243 msgid "Priority (`selection`)" msgstr "" @@ -1727,6 +2107,10 @@ msgstr "" msgid "To change the number of available stars by adding or removing values, click :guilabel:`Edit Values`. Note that the first value is equal to 0 stars (i.e., when no selection is made), so having four values results in a three-star rating system, for example." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:266 msgid "File (`binary`)" msgstr "" @@ -1747,6 +2131,10 @@ msgstr "" msgid ":guilabel:`Sign`: users can electronically sign the form. This has the same effect as selecting the :ref:`Sign field `." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:288 msgid "Image (`binary`)" msgstr "" @@ -1791,6 +2179,10 @@ msgstr "" msgid "On the *Sales Order* model, the :guilabel:`Customer` field is a :guilabel:`Many2One` field pointing at the *Contact* model. This allows **many** sales orders to be linked to **one** contact (customer)." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:345 msgid "To prevent users from creating a new record in the linked model, tick :guilabel:`Disable creation`." msgstr "" @@ -1819,6 +2211,10 @@ msgstr "" msgid "You could add a :guilabel:`One2Many` field on the *Contact* model to look at **one** customer's **many** sales orders." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:371 msgid "To use a :guilabel:`One2Many` field, the two models must have been linked already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search of existing Many2One relations is performed." msgstr "" @@ -1835,6 +2231,10 @@ msgstr "" msgid "To modify the columns, click on the :guilabel:`Lines` field and then :guilabel:`Edit List View`. To edit the form that pops up when a user clicks on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:397 msgid "Many2Many (`many2many`)" msgstr "" @@ -1847,6 +2247,10 @@ msgstr "" msgid "On the *Task* model, the :guilabel:`Assignees` field is a :guilabel:`Many2Many` field pointing at the *Contact* model. This allows a single user to be assigned to **many** tasks and **many** users to be assigned to a single task." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:413 msgid ":guilabel:`Checkboxes`: users can select several values using checkboxes." msgstr "" @@ -1867,6 +2271,10 @@ msgstr "" msgid "To display tags with different background colors, tick :guilabel:`Use colors`." msgstr "" +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + #: ../../content/applications/productivity/studio/fields.rst:441 msgid "Related Field (`related`)" msgstr "" @@ -1963,6 +2371,10 @@ msgstr "" msgid "Creating a model with the :ref:`studio/models-modules-apps/suggested-features/picture` and :ref:`studio/models-modules-apps/suggested-features/pipeline-stages` features enabled adds the image in the card layout of the :ref:`Kanban view `." msgstr "" +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + #: ../../content/applications/productivity/studio/models_modules_apps.rst:39 msgid "Contact details" msgstr "" @@ -1971,6 +2383,10 @@ msgstr "" msgid "Selecting :guilabel:`Contact details` adds to the :ref:`Form view ` a :ref:`Many2One field ` linked to the *Contact* model and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The :guilabel:`Contact` field is also added to the :ref:`List view `, and the :ref:`Map view ` is activated." msgstr "" +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + #: ../../content/applications/productivity/studio/models_modules_apps.rst:57 msgid "User assignment" msgstr "" @@ -1979,6 +2395,10 @@ msgstr "" msgid "Selecting :guilabel:`User assignment` adds to the :ref:`Form view ` a :ref:`Many2One field ` linked to the *Contact* model, with the following :guilabel:`Domain`: `Share User is not set` to only allow the selection of *Internal Users*. In addition, the :guilabel:`many2one_avatar_user` widget is used to display the user's avatar. The :guilabel:`Responsible` field is also added to the :ref:`List view `." msgstr "" +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + #: ../../content/applications/productivity/studio/models_modules_apps.rst:75 msgid "Date & Calendar" msgstr "" @@ -2075,6 +2495,10 @@ msgstr "" msgid "Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view ` a drag handle icon to manually reorder records." msgstr "" +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + #: ../../content/applications/productivity/studio/models_modules_apps.rst:186 msgid "Chatter" msgstr "" @@ -2087,6 +2511,10 @@ msgstr "" msgid "The :guilabel:`Chatter` feature can be added at a later stage." msgstr "" +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + #: ../../content/applications/productivity/studio/models_modules_apps.rst:203 msgid "Archiving" msgstr "" @@ -2115,6 +2543,432 @@ msgstr "" msgid "Before importing, make sure the destination database contains the same apps and modules as the source database. Studio does not add the underlying modules as dependencies of the exported module." msgstr "" +#: ../../content/applications/productivity/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:5 +msgid "With Studio, you can edit existing PDF reports (e.g., orders and quotations) or create new ones." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:10 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:12 +msgid "The default layout of reports is managed outside Studio. Go to :menuselection:`Settings --> Companies: Document Layout --> Configure Document Layout`. Layout settings apply to all reports but only to the current company." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:17 +msgid "Use :guilabel:`Download PDF Preview` to view how the different settings affect the layout of a sample invoice." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:23 +msgid "Layout" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:25 +msgid "Four layouts are available." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:29 +msgid "Light" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:35 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:41 +msgid "Bold" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:47 +msgid "Striped" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:56 +msgid "Font" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:58 +msgid "Seven fonts are available. Click on the links below to preview them on `Google Fonts `_." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:61 +msgid "`Lato `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:62 +msgid "`Roboto `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:63 +msgid "`Open Sans `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:64 +msgid "`Montserrat `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:65 +msgid "`Oswald `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:66 +msgid "`Raleway `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:67 +msgid "`Tajawal `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:70 +msgid ":guilabel:`Tajawal` supports both Arabic and Latin scripts." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:75 +msgid "Company logo" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:77 +msgid "Upload an image file to add a :guilabel:`Company Logo`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:80 +msgid "This adds the logo to the company’s record on the *Company* model, which you can access by going to :menuselection:`General Settings --> Companies --> Update Info`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:86 +msgid "Colors" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:88 +msgid "Change the primary and secondary colors used throughout reports to highlight important elements. The default colors are automatically generated based on the colors of the logo." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:94 +msgid "Layout background" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:96 +msgid "Change the :guilabel:`Layout Background` of the report:" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:98 +msgid ":guilabel:`Blank`: nothing is displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:99 +msgid ":guilabel:`Geometric`: an image featuring geometric shapes is displayed in the background." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:100 +msgid ":guilabel:`Custom`: use a custom background image by uploading one." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:105 +msgid "Company tagline" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:107 +msgid "The :guilabel:`Company Tagline` is displayed on the header of :ref:`External reports `. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:113 +msgid "Company details" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:115 +msgid "The :guilabel:`Company Details` are displayed on the header of :ref:`External reports `. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:121 +msgid "Footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:123 +msgid "Use the :guilabel:`Footer` field to put any text in the :ref:`External reports' ` footers. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:129 +msgid "Paper format" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:131 +msgid "Use the :guilabel:`Paper format` field to change the paper size of reports. You can either select :guilabel:`A4` (21 cm x 29.7 cm) or :guilabel:`US Letter` (21.59 cm x 27.54 cm)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:135 +msgid "You can change the :guilabel:`Paper format` on individual reports. Open the app containing the report, then :menuselection:`Toggle Studio --> Reports --> Select or Create a report --> Report --> Select a Paper format`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:None +msgid "Configuration pop-up window for the default layout of PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:146 +msgid "Header and footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:148 +msgid "When creating a new report in Studio, you must choose between one of three styles of reports first. This is solely used to determine what is displayed on the header and footer. To do so, go to the app on which you want to add a new report, then :menuselection:`Studio button --> Reports --> Create` and select :ref:`studio/pdf-reports/header-footer/external`, :ref:`studio/pdf-reports/header-footer/internal`, or :ref:`studio/pdf-reports/header-footer/blank`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:157 +msgid "External" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:159 +msgid "The header displays the company :ref:`studio/pdf-reports/default-layout/logo` and several values set on the *Company* model: the :guilabel:`Company Name`, :guilabel:`Phone`, :guilabel:`Email`, and :guilabel:`Website`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:164 +msgid "To change a company's information, go to :menuselection:`Settings --> Companies --> Update Info`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:None +msgid "Example of an External header" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:170 +msgid "The footer displays the values set on the :ref:`studio/pdf-reports/default-layout/footer`, :ref:`studio/pdf-reports/default-layout/details`, and :ref:`studio/pdf-reports/default-layout/tagline` fields, as well as the page number." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:None +msgid "Example of an External footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:181 +msgid "Internal" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:183 +msgid "The header displays the user's current date and time, :guilabel:`Company Name`, and page number." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:185 +msgid "There is no footer." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:190 +msgid "Blank" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:192 +msgid "There is neither a header nor a footer." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:197 +msgid "Add tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:199 +msgid "After opening an existing report or creating a new one, go to the :guilabel:`Add` tab to add or edit elements. The elements are organized into four categories: :ref:`studio/pdf-reports/elements/block`, :ref:`studio/pdf-reports/elements/inline`, :ref:`studio/pdf-reports/elements/table`, and :ref:`studio/pdf-reports/elements/column`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:207 +msgid "Block" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:209 +msgid "Block elements start on a new line and occupy the full width of the page." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:212 +msgid "You can set an element's width by selecting it and going to the :guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:214 +#: ../../content/applications/productivity/studio/pdf_reports.rst:244 +msgid ":guilabel:`Text`: add any text using small font size by default." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:216 +msgid ":guilabel:`Title Block`: add any text using larger font size by default." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:218 +msgid ":guilabel:`Image`: add an image. You can either upload one from your device, add one from an URL, or select one already existing on your database." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:221 +#: ../../content/applications/productivity/studio/pdf_reports.rst:246 +msgid ":guilabel:`Field`: dynamically add a field's value." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:223 +msgid ":guilabel:`Field & Label`: to dynamically add a field's value and label." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:225 +msgid ":guilabel:`Address Block`: to dynamically add the values, if any, of a contact's (`res.partner` model): *Name*, *Address*, *Phone*, *Mobile*, and *Email*." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Example of an Address Block" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:235 +msgid "Inline" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:237 +msgid "Inline elements are used around other elements. They do not start on a new line and the width adapts to length of the content." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:241 +msgid "You can set an element's width and margins by selecting it and going to the :guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:251 +msgid "Table" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:253 +msgid "Table elements are used together to create a data table." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:255 +msgid ":guilabel:`Data table`: create a table and dynamically add a first column displaying the *Name* values of a :ref:`Many2Many ` or :ref:`One2Many ` field on your model." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Example of a Data table" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:263 +msgid ":guilabel:`Field Column`: add a new column to the table displaying the values of a :ref:`Related Field ` to the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:267 +msgid ":guilabel:`Text in Cell`: add any text within an existing table cell." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:269 +msgid ":guilabel:`Field in Cell`: add, within an existing table cell, the values of a :ref:`Related Field ` to the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:273 +msgid ":guilabel:`Subtotal & Total`: add an existing :guilabel:`Total` field's value. If a :guilabel:`Taxes` field exists, the untaxed and taxes amounts are added before the total amount." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:279 +msgid "Column" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:281 +msgid "Columns are used to add multiple :ref:`blocks ` elements on the same line." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:284 +msgid ":guilabel:`Two Columns`: add any text in two different columns." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:286 +msgid ":guilabel:`Three Columns`: add any text in three different columns." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:289 +msgid "Report tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:291 +msgid "Several configuration options are available under the :guilabel:`Report` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:293 +msgid ":guilabel:`Name`: change the report name. The new name is applied everywhere (in Studio, under the :guilabel:`Print` button, and for the PDF file name)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:296 +msgid ":guilabel:`Paper format`: change the paper size of the report." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:298 +msgid ":guilabel:`Add in print`: add the report under the :guilabel:`🖶 Print` button available on the record." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:301 +msgid ":guilabel:`Limit visibility to groups`: limit the availability of the PDF report to specific :doc:`user groups <../../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:305 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:307 +msgid "Select an element on the report to access the element's options and edit it." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:None +msgid "The Options tab for a text element" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:314 +msgid "You can select and edit multiple elements at the same time by clicking on the different sections or divisions (e.g., `div`, `table`, etc.)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:317 +msgid "Below are presented some of the most common options:" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:319 +msgid ":guilabel:`Margins`: add spacing at the :guilabel:`top`, :guilabel:`right`, :guilabel:`bottom`, and :guilabel:`left` of the element." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:322 +msgid ":guilabel:`Width`: set the element's maximum width." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:324 +msgid ":guilabel:`Visible if`: set under which condition(s) the element should be displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:326 +msgid ":guilabel:`Visible for`: set for which :doc:`users groups <../../general/users/access_rights>` the element should be displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:329 +msgid ":guilabel:`Remove from View`: remove the element from the report's view." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:331 +msgid ":guilabel:`Text decoration`: bold, italicize, and underline the font." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:333 +msgid ":guilabel:`Alignment`: align the element to the left, center, or right of the report." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:335 +msgid ":guilabel:`Font style`: use one of the default font styles." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:337 +msgid ":guilabel:`Colors`: change the font's color and the background color." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:340 +msgid "You may need to select a section or division above the element you want to edit to see some of the options described above." +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:3 msgid "Views" msgstr "" @@ -2163,6 +3017,10 @@ msgstr "" msgid "To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:59 msgid "Activity" msgstr "" @@ -2175,6 +3033,10 @@ msgstr "" msgid "This view can only be modified within Studio by editing the XML code." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:76 msgid "Search" msgstr "" @@ -2191,6 +3053,10 @@ msgstr "" msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion Fields`." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:94 msgid "Multiple records views" msgstr "" @@ -2219,6 +3085,10 @@ msgstr "" msgid "To change the way records are grouped by default, select a new group under :guilabel:`Default Group by`." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:127 msgid "List" msgstr "" @@ -2247,6 +3117,14 @@ msgstr "" msgid "To add a drag handle icon to reorder records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:161 msgid "Map" msgstr "" @@ -2275,6 +3153,10 @@ msgstr "" msgid "To have a route suggested between the different records, tick :guilabel:`Enable Routing` and select which field should be used to sort records for the routing." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:187 msgid "Timeline views" msgstr "" @@ -2319,6 +3201,10 @@ msgstr "" msgid "You can also use :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:242 msgid "Cohort" msgstr "" @@ -2343,6 +3229,10 @@ msgstr "" msgid "To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is used." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:268 msgid "Gantt" msgstr "" @@ -2391,6 +3281,10 @@ msgstr "" msgid "To specify with which degree of precision each time scale should be divided by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month Precision`." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:308 msgid "Reporting views" msgstr "" @@ -2419,6 +3313,10 @@ msgstr "" msgid "To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display count`." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:341 msgid "Graph" msgstr "" @@ -2451,6 +3349,10 @@ msgstr "" msgid "*For Bar charts only*: When using two data dimensions (categories), display the two columns on top of each other by default by ticking :guilabel:`Stacked graph`." msgstr "" +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" + #: ../../content/applications/productivity/studio/views.rst:368 msgid "Dashboard" msgstr "" @@ -2458,3 +3360,7 @@ msgstr "" #: ../../content/applications/productivity/studio/views.rst:370 msgid "The :guilabel:`Dashboard` view is used to display multiple reporting views and key performance indicators. Which elements are displayed on the view depends on the configuration of the other reporting views." msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales Analysis Report model's Dashboard view" +msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index eeac65383..6887b1eb2 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -70,7 +70,8 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:8 #: ../../content/applications/sales/rental.rst:20 #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:13 -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:114 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:9 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:9 #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:16 #: ../../content/applications/sales/subscriptions/configuration.rst:5 @@ -141,6 +142,10 @@ 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 +msgid "Configuring Sales Teams" +msgstr "" + #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:23 msgid "Use Contact Forms on your website" msgstr "" @@ -149,18 +154,34 @@ 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 +msgid "Default Contact Us page" +msgstr "" + #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:32 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 +msgid "Contact Form toggle" +msgstr "" + #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:39 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 +msgid "Contact Us Page using email" +msgstr "" + #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:46 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 +msgid "Contact Form settings" +msgstr "" + #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:55 msgid "Customize Contact Forms" msgstr "" @@ -173,6 +194,10 @@ 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 +msgid "Form Builder building blocks" +msgstr "" + #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:68 msgid "Forms can be created from scratch to serve a wide variety of purposes. However, Odoo's default *Contact Us* page is designed to fit most users' needs. Start with the default form and modify from there." msgstr "" @@ -217,6 +242,10 @@ 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 +msgid "Editable field options" +msgstr "" + #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:97 msgid "By default, when a Form is submitted, it sends you an email with the customer's inputted information. To have it automatically generate a lead/opportunity instead, edit the Form and select :guilabel:`Create an Opportunity` as the Action." msgstr "" @@ -279,10 +308,10 @@ msgid "The blue box will automatically tell you how many credits are going to be msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:68 -msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." +msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:71 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:72 msgid ":doc:`In-App Purchases (IAP) `" msgstr "" @@ -334,6 +363,10 @@ 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 +msgid "View of the gamification module being installed in Odoo" +msgstr "" + #: ../../content/applications/sales/crm/optimize/gamification.rst:21 msgid "Create a challenge" msgstr "" @@ -346,6 +379,10 @@ 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 +msgid "View if the gamification tools menu in Odoo Settings" +msgstr "" + #: ../../content/applications/sales/crm/optimize/gamification.rst:35 msgid "A challenge is a mission that you send to your sales team. It can include one or several goals, set for a specific period of time. Configure your challenge as follows:" msgstr "" @@ -378,6 +415,10 @@ 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 +msgid "View of the challenge form and a challenge being created for Odoo Sales" +msgstr "" + #: ../../content/applications/sales/crm/optimize/gamification.rst:58 msgid "Set up goals" msgstr "" @@ -394,6 +435,10 @@ 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 +msgid "View of the goal definition form and a goal definition being created for Odoo Sales" +msgstr "" + #: ../../content/applications/sales/crm/optimize/gamification.rst:73 msgid "Goals may include your database setup as well (e.g. set your company data and a timezone, create new users, etc.)." msgstr "" @@ -406,6 +451,10 @@ 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 +msgid "View of the badges page in Odoo" +msgstr "" + #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:3 msgid "Enrich your contacts base with Partner Autocomplete" msgstr "" @@ -418,6 +467,10 @@ msgstr "" msgid "Go to :menuselection:`Settings --> Contacts` and activate the *Partner Autocomplete* feature." msgstr "" +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:None +msgid "View of settings page and the activations of the feature in Odoo" +msgstr "" + #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:18 msgid "Enrich your contacts with corporate data" msgstr "" @@ -430,6 +483,14 @@ msgstr "" msgid "For example, after typing *Odoo*, you will get the following information:" msgstr "" +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:None +msgid "Creating a new contact in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:None +msgid "View of the information being shown about odoo with the autocomplete option in Odoo" +msgstr "" + #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:33 msgid "Partner Autocomplete also works if you enter a VAT number instead of a company name." msgstr "" @@ -447,7 +508,7 @@ msgid "If you run out of credits, the only information that will be populated wh msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:46 -msgid "If you are on Odoo Online (SAAS) and you have the Enterprise version, you benefit from free trial credits to test the feature." +msgid "If you are on Odoo Online and you have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:48 @@ -467,82 +528,122 @@ msgid "Create custom dashboards in Google Spreadsheet that retrieves data direct msgstr "" #: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:12 -msgid "From the *General Settings*, active *Google Drive* and *Google Spreadsheet*. The options *Authorization Code* and *Get Authorization Code* are now available." +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 +msgid "Enable the Google Drive and Google Spreadsheet features in Odoo" msgstr "" #: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:19 -msgid "Now, link your Google account with Odoo going to :menuselection:`Get Authorization Code --> select your Google account --> enter your password --> copy the code --> paste it into the Authorization Code field`." +msgid "Now, link your Google account with Odoo by following these steps:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:21 +msgid "Get Authorization Code" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:22 +msgid "Select your Google account" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:23 +msgid "Enter your password" msgstr "" #: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:24 +msgid "Copy the code" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:25 +msgid "Paste it into the Authorization Code field" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:28 msgid "Create a new Spreadsheet" msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:26 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:30 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:32 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +msgid "From the CRM application, for example, click on add to Google Spreadsheet in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:36 msgid "A new spreadsheet will be automatically created in your Google Drive." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:35 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:39 msgid "When you opening this new file, a second sheet is created automatically by Odoo with a tutorial/documentation on *How to use Google Spreadsheet*." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:39 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:43 msgid "Link a Spreadsheet with Odoo" msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:41 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:45 msgid "From this new file, configure your database." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:42 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:46 msgid "Go to :menuselection:`Odoo --> Server Settings --> Database Name --> Username --> Password`." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:49 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +msgid "Menu called Odoo is shown on the settings bar in the Spreadsheet" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:53 msgid "Applications" msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:51 -msgid "You have 2 different formulas of using Google Spreadsheet in Odoo: retrieve data and retrieve grouped sums." +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:55 +msgid "You have two different formulas available when using Google Spreadsheet in Odoo: *retrieve data* and *retrieve grouped sums*." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:55 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:59 msgid "Google Drive limits the execution time of scripts; if the data you requested takes too long to be delivered, you might get an error. There is no specific size limit, since the time for Odoo to respond depends on several factors - although reading data regarding several thousand records is usually fine." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:62 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:66 msgid "Retrieve Data" msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:66 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:70 msgid "The theoretical formula is :command:`= oe_browse (table;columns;filters;orderby:limit)`. Used it if you want to display the information without grouping it (e.g.: each sales order in the database)." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:67 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:71 msgid "Find some the arguments in the table below." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:74 -msgid "Retrieve Grouped Sums" -msgstr "" - -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:77 -msgid "The theoretical formula is :command:`= oe_read_group (table;columns;group_by;filters;orderby:limit)`. Use it when you want to display a sum of data (e.g.: total invoiced)." +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +msgid "Table with examples of arguments to use in Odoo" msgstr "" #: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:78 +msgid "Retrieve Grouped Sums" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:81 +msgid "The theoretical formula is :command:`= oe_read_group (table;columns;group_by;filters;orderby:limit)`. Use it when you want to display a sum of data (e.g.: total invoiced)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:82 msgid "Find some arguments in the table below." msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:85 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:None +msgid "Table with examples of grouped sum arguments to use in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:89 msgid "Other uses" msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:87 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:91 msgid "Mix Odoo data with spreadsheet data, add traditional formulas, and create Dynamic Tabled and Graphs." msgstr "" @@ -663,47 +764,63 @@ msgid "Create a new Sales Team" msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:12 -msgid "To create a new Sales Team, go to :menuselection:`CRM --> Configuration --> Sales Teams` then click **Create**." +msgid "To create a new Sales Team, go to :menuselection:`CRM --> Sales --> Teams` then click :guilabel:`Create`." msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:15 -msgid "On the creation page, set an *Email Alias* to automatically generate a lead/opportunity for this Sales Team every time a message is sent to that unique email address. You can also choose whether to accept emails from *Everyone*, *Authenticated Partners*, or *Followers Only*." +msgid "On the creation page, set an :guilabel:`Email Alias` to automatically generate a lead/opportunity for this Sales Team every time a message is sent to that unique email address. You can also choose whether to accept emails from :guilabel:`Everyone`, :guilabel:`Authenticated Partners`, or :guilabel:`Followers Only`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:19 -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." +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:20 +msgid "Set a :guilabel:`Domain` to assign leads/opportunities to this Sales Team based on specific filters, such as country, language, or campaign. Set an :guilabel:`Invoicing Target` if this team has specific monthly revenue goals." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:28 +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:None +msgid "Create a Sales Team in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:29 msgid "Add members to a Sales Team" msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:30 -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." +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:31 +msgid "To add team members, click :guilabel:`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:39 +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:None +msgid "Add a Salesperson inside Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:40 msgid "One person can be added as a team member or Team Leader to multiple Sales Teams, allowing them to access all of the pipelines that they need to." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:42 +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:44 msgid "Sales Team dashboard" msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:44 -msgid "To view the Sales Team dashboard, go to :menuselection:`CRM --> Configuration --> Sales Teams`. Any teams you are a part of will appear as dashboard tiles." +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:46 +msgid "To view the Sales Team dashboard, go to :menuselection:`CRM --> Sales --> Teams`. Any teams you are a part of will appear as dashboard tiles." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:47 +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:49 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:55 +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:None +msgid "Sales Team Overview dashboard in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:57 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:63 -msgid "Click on the **Pipeline** button to go directly to that team's CRM pipeline." +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:None +msgid "Click the Three Dot Menu in Odoo CRM dashboard to view documents and create opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:65 +msgid "Click on the :guilabel:`Pipeline` button to go directly to that team's CRM pipeline." msgstr "" #: ../../content/applications/sales/crm/track_leads.rst:5 @@ -726,6 +843,10 @@ 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 +msgid "Lead Scoring module installation" +msgstr "" + #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:22 msgid "Create scoring rules" msgstr "" @@ -738,10 +859,18 @@ 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 +msgid "Score Rule example" +msgstr "" + #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:32 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 +msgid "Scoring section on a lead" +msgstr "" + #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:39 msgid "Assign leads" msgstr "" @@ -750,10 +879,18 @@ 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 +msgid "Team Assignments using domains" +msgstr "" + #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:50 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 +msgid "Lead Assignments" +msgstr "" + #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:57 msgid "Odoo automatically assigns new leads to teams/salespeople once per day." msgstr "" @@ -770,6 +907,10 @@ 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 +msgid "Filtering for unassigned leads" +msgstr "" + #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:72 msgid "You can also find unassigned leads and create re-engagement campaigns using the :guilabel:`Email Marketing` or :guilabel:`Marketing Automation` apps." msgstr "" @@ -918,6 +1059,10 @@ msgstr "" 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 "" @@ -934,14 +1079,26 @@ msgstr "" 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 "" @@ -954,6 +1111,10 @@ msgstr "" 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 "" @@ -970,6 +1131,10 @@ msgstr "" 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 "" @@ -978,6 +1143,10 @@ msgstr "" 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 "" @@ -1063,7 +1232,6 @@ msgid "Setting up the Fiscal Data Module with the Odoo POS" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:6 -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:170 msgid "Introduction" msgstr "" @@ -1117,7 +1285,7 @@ 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 SaaS 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." +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 @@ -1292,6 +1460,10 @@ msgstr "" 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 "" @@ -1336,6 +1508,10 @@ msgstr "" msgid "To make products available for sale, go to :menuselection:`Point of Sale --> Products --> Products` and open a product. In the *Point of Sale* tab, enable *Available in Point of Sale*." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Product form. Making the product available in PoS." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:28 msgid "You can also define if the product has to be weighted or not." msgstr "" @@ -1348,6 +1524,10 @@ msgstr "" msgid "To add a payment method, you first need to create it. Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods` and click on create. Then, you can name your payment method and set it up." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Creating a new payment method for a Point of Sale." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:43 msgid "Don’t forget your credentials for methods using a payment terminal." msgstr "" @@ -1356,6 +1536,10 @@ msgstr "" 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 open the PoS in which you want to include the payment method. Then, add the payment method." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Making the payment method available in a point of sale." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:55 msgid "*Configuration* is the menu where you can edit all your point of sale settings. Some more features are available for restaurants." msgstr "" @@ -1372,10 +1556,18 @@ msgstr "" msgid "Open a new session from the dashboard by clicking on *New Session*." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Launching a new session." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:70 msgid "After the loading screen, you arrive on the PoS interface." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Point of sale dashboard." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:76 msgid "Once an order is completed, you can register the payment. All the available payment methods appear on the left of the screen. Select the payment method and enter the received amount. Then, you can validate the payment." msgstr "" @@ -1396,10 +1588,18 @@ msgstr "" msgid "To do that, from the PoS interface, select the product and quantity (with the +/- button) that the customer wants to return. For multiple products, repeat the process individually." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Refunding a product with the point of sale app." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:97 msgid "When on the payment interface, the total is negative. To end the refund, process the payment and validate it." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Giving back money to customer in Odoo Point of Sale." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:105 msgid "Close the PoS session" msgstr "" @@ -1408,6 +1608,10 @@ msgstr "" msgid "To close your session at the end of the day, click on the close button on the upper right corner of your screen and confirm. Now, close the session on the dashboard view." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "How to close a point of sale session." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:115 msgid "It’s strongly advised to close your PoS session at the end of each day." msgstr "" @@ -1416,6 +1620,10 @@ msgstr "" msgid "Once a session is closed, you can see a summary of all transactions per payment method. Then, click on a line to see all orders that were paid during your PoS session. If everything is correct, validate the session and post the closing entries." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Point of sale sales report before closing the session." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:126 msgid "To connect the PoS hardware with an Odoo IoT Box, please refer to these docs: :doc:`Connect an IoT Box to your database ` and :doc:`Use the IoT Box for the PoS `." msgstr "" @@ -1432,10 +1640,18 @@ msgstr "" msgid "To access your statistics, go to :menuselection:`Point of Sales --> Reporting --> Orders`. There, you can see various statistics in graph or pivot form." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Orders analysis with pivot view of the point of sale reporting feature." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:145 msgid "You can also access them through the dashboard." msgstr "" +#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None +msgid "Accessing orders analysis via the point of sale dashboard. Reporting feature on the PoS form." +msgstr "" + #: ../../content/applications/sales/point_of_sale/overview/https.rst:3 msgid "Secure connection (HTTPS)" msgstr "" @@ -1683,10 +1899,18 @@ msgstr "" 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 +msgid "The POS Six module." +msgstr "" + #: ../../content/applications/sales/point_of_sale/payment/six.rst:28 msgid "Back in :menuselection:`Point of Sale --> Configuration --> Payment Methods`, click :guilabel:`Create` to 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 +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 msgid "Pay with a Payment Terminal" @@ -1696,10 +1920,18 @@ msgstr "" 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 +msgid "The PoS interface." +msgstr "" + #: ../../content/applications/sales/point_of_sale/payment/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 +msgid "The Reverse button on the PoS interface." +msgstr "" + #: ../../content/applications/sales/point_of_sale/payment/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 "" @@ -1984,10 +2216,18 @@ msgstr "" 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 "" @@ -1996,6 +2236,14 @@ msgstr "" 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 "" @@ -2008,10 +2256,18 @@ msgstr "" 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 "" @@ -2024,6 +2280,10 @@ msgstr "" 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 "" @@ -2036,10 +2296,19 @@ msgstr "" 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 "" @@ -2052,6 +2321,10 @@ msgstr "" 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 "" @@ -2372,6 +2645,10 @@ msgstr "" msgid "From the **Point of Sale** application, open a new session. Then, click on :guilabel:`Quotations/Orders` to get the complete list of quotations and sales orders created on the sales application." msgstr "" +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:None +msgid "Quotations and sales order button on the Point of Sale interface" +msgstr "" + #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:21 msgid "To ease finding the right sales order, you can filter that list on the **customer** or on the **order reference**. You can also set the customer before clicking on :guilabel:`Quotations/Orders` to reduce the list to one particular customer." msgstr "" @@ -2384,6 +2661,10 @@ msgstr "" msgid "From the list of sales order, select one to make a payment." msgstr "" +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:None +msgid "list view of sales orders and quotations" +msgstr "" + #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:34 msgid "You can either:" msgstr "" @@ -2416,6 +2697,10 @@ msgstr "" msgid "To enable traceability, go to :menuselection:`Point of Sale --> Products --> Products`. Then, select a product and check the :guilabel:`Tracking By Unique Serial Number` or the :guilabel:`Tracking By Lots` box in the :guilabel:`Inventory` tab." msgstr "" +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:None +msgid "Enable traceability settings" +msgstr "" + #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:17 msgid "Serial numbers and lots importation" msgstr "" @@ -2424,6 +2709,11 @@ msgstr "" msgid "You can import serial numbers in Point of Sale. To do so, select a **sales order** or a **quotation** containing tracked products. Then, agree to load the **Lots or Serial Numbers** linked to the :abbr:`SO (sales order)`." msgstr "" +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:None +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:None +msgid "Pop-up window for serial number import" +msgstr "" + #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:28 msgid "The imported tracking numbers appear below the tracked products. You can modify them by clicking on the list-view button next to the products." msgstr "" @@ -2440,6 +2730,10 @@ msgstr "" msgid "If a tracked product is available in your POS, adding the product to the cart opens a pop-up window where you can type or scan the product's serial or lot numbers. To add more than one of the same tracked products, click on **enter** to validate and start a new line." msgstr "" +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:None +msgid "adding new serial and lots numbers" +msgstr "" + #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:52 msgid "Changing a tracked product's quantity using the numpad turns the list-view button red. Click on it to add the missing lot and serial numbers." msgstr "" @@ -2484,6 +2778,10 @@ 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 +msgid "Example of rental pricing configuration in Odoo Rental" +msgstr "" + #: ../../content/applications/sales/rental.rst:32 msgid "Under *Reservations*, you can add fines for any *Extra Hour* or *Extra Day*. You can also set a *Security Time*, expressed in hours, to make the product temporarily unavailable between two rental orders." msgstr "" @@ -2540,6 +2838,10 @@ 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 +msgid "Digital Documents settings in Odoo Rental" +msgstr "" + #: ../../content/applications/sales/rental.rst:76 msgid "This feature requires the :doc:`Sign <../finance/sign>` app. If necessary, Odoo installs it after activating *Digital Documents*." msgstr "" @@ -2564,6 +2866,10 @@ 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 +msgid "Printing a Pickup and Return receipt in Odoo Rental" +msgstr "" + #: ../../content/applications/sales/sales.rst:10 msgid "**Odoo Sales** is the application to run your sales process (from quotation to sales order) and deliver and invoice what has been sold." msgstr "" @@ -3232,6 +3538,10 @@ 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 +msgid "Button to generate an eBay verification token in Odoo" +msgstr "" + #: ../../content/applications/sales/sales/ebay_connector/setup.rst:70 msgid "Subscribe to account deletion notifications" msgstr "" @@ -3240,6 +3550,10 @@ 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 +msgid "Overview of the Alerts & Notifications dashboard of eBay" +msgstr "" + #: ../../content/applications/sales/sales/ebay_connector/setup.rst:79 msgid "To subscribe to deletion/closure notifications, eBay needs a few details:" msgstr "" @@ -3260,6 +3574,10 @@ msgstr "" msgid "A verification token" msgstr "" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:None +msgid "Dedicated fields to enter the endpoint details" +msgstr "" + #: ../../content/applications/sales/sales/ebay_connector/setup.rst:92 msgid "You can edit the last two fields once the email address field is filled out." msgstr "" @@ -3276,6 +3594,10 @@ 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 +msgid "Button to send test notification" +msgstr "" + #: ../../content/applications/sales/sales/ebay_connector/setup.rst:107 msgid "Using the updated synchronisation method" msgstr "" @@ -3356,6 +3678,10 @@ msgstr "" 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." msgstr "" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None +msgid "How can you do a down payment on Odoo Sales?" +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**." msgstr "" @@ -3368,14 +3694,26 @@ msgstr "" 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)." msgstr "" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None +msgid "What is a basic sales flow using down payments on Odoo Sales (1)?" +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)." msgstr "" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None +msgid "What is a basic sales flow using down payments on Odoo Sales (2)?" +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." msgstr "" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None +msgid "What is a basic sales flow using down payments on Odoo Sales (3)?" +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." msgstr "" @@ -3392,10 +3730,18 @@ msgstr "" msgid "From the products list, search for the **Down Payment** product." msgstr "" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None +msgid "Creation of a down payment product on 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." msgstr "" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:None +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`" msgstr "" @@ -3494,6 +3840,10 @@ 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 +msgid "How to choose your invoicing policy on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:30 msgid "If you decide to choose the **Invoice what is delivered** rule, you will not be able to activate the feature called **Automatic invoice**, which automatically generates invoices when the online payment is confirmed." msgstr "" @@ -3506,6 +3856,10 @@ 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 +msgid "How to change your invoicing policy on a product form on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:46 msgid "Impact on sales flow" msgstr "" @@ -3522,10 +3876,18 @@ msgstr "" msgid "**Invoice what is delivered**: Small impact on sales flow because you will have to manually enter the delivered quantity on the sales order or to install the **Inventory App** to confirm the delivered quantity before creating an invoice, with the **Sales App**. Indeed, if you try to create an invoice without validating the delivered quantity, you will receive an error message as below." msgstr "" +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:0 +msgid "How the choice of your invoicing policy impacts your sales flow on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:65 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 +msgid "How to see your delivered and invoiced quantities on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:74 msgid "Odoo will automatically add the quantities to the invoice (even if it is a partial delivery)." msgstr "" @@ -4004,6 +4366,10 @@ msgstr "" msgid "In the credentials section, click on **Create Credentials** and select **API Keys**." msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "API & Services page on Google Cloud Platform" +msgstr "" + #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:37 msgid "Save your **API Key**. You'll need it for the next step in Odoo!" msgstr "" @@ -4012,10 +4378,18 @@ msgstr "" msgid "Use the search bar to look for **Google Custom Search API** and select it." msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform" +msgstr "" + #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:45 msgid "Enable the API." msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "\"Custom Search API\" tile with Enable button highlighted on Google Cloud Platform" +msgstr "" + #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:54 msgid "Google Programmable Search dashboard" msgstr "" @@ -4024,6 +4398,11 @@ msgstr "" msgid "Go to `Google Programmable Search Engine `_ and click on **Get Started**. Log in with your Google account." msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Google Programmable Search Engine page with the **Get Started** button on the up-right\n" +"of the page" +msgstr "" + #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:64 msgid "Fill the language and the name of the search engine. Give it an explicit name (e.g. Odoo Images)." msgstr "" @@ -4105,235 +4484,240 @@ msgid "`Create, modify, or close your Google Cloud Billing account Settings`, locate the **Products Variants** line, and tick the option **Products can have several attributes**, then click on **Apply**." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:129 -msgid "Creating products with variants" +msgid "Color: Blue, Red, White, Black" msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:14 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:131 -msgid "Once you have activated the variant option, you can add variants to your products. To do so, go to the Sales module, :menuselection:`Sales --> Products`. It is also accessible from the Purchase and inventory modules." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:135 -msgid "Now, click on the product you wish to add variants to." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137 -msgid "In the product page, a new tab called Variants has appeared. The number in purple written on top is the number of variants this product currently has. To add new variants, click on the tile. In the new window, click on **Create**." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:142 -msgid "In **Attributes**, click on the rolldown menu and select the type of variance you wish to add. If the variant does not yet exist, you can create it on the fly by clicking on Create and edit…" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:149 -msgid "In the Attributes window, the **Value** field is the description of the attribute such as Green, Plastic or 32GB. The **Attribute** field is the type of variant such as Color, Material or Memory." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:156 -msgid "You can add a cost for the variant on the fly by adding it in the **Attribute Price Extra** field, or choose to modify it later. Click on **Save**." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:160 -msgid "You can also add a different barcode and internal reference to the variant." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:163 -msgid "When you have entered all the specifications of the variant, click on **Save**." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:167 -msgid "Managing Product Variants" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:172 -msgid "The examples below are all based on this product template that has two variant attributes :" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:175 -msgid "T-Shirt B&C" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:177 -msgid "Color: Red, Blue, White" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:179 msgid "Size: S, M, L, XL, XXL" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:182 -msgid "Managing combination possibilities" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:16 +msgid "In this example, the **T-Shirt** is the product template, and **T-Shirt, S, Blue** is a product variant. **Color** and **size** are the attributes. **S** and **Blue** are values." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:184 -msgid "By default, with the above product template, you get 15 different products (3 colors, 5 sizes). If the XXL size only exists for red and blue t-shirts, you can deactivate the white product variant." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:19 +msgid "The above example has a total of 20 different product variants (5 sizes x 4 colors). Each one of these has its own inventory, sales, etc." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:188 -msgid "To do this, click on the **Variants** button, select the XXL, White T-shirt. From the product form, uncheck the **Active** box of the T-shirt White, XXL." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:26 +msgid "Activating product variants" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:197 -msgid "That deactivating a product is different than having an inventory of 0." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:28 +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:200 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:None +msgid "Activating product variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:37 +msgid "Creating attributes" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:39 +msgid "Attributes need to be created before product variants can be set up. Attributes can be accessed via :menuselection:`Sales --> Configuration --> Products --> Attributes`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:43 +msgid "The order of attributes on the :guilabel:`Attributes` page dictates how they appear on the :guilabel:`Product Configurator`, :guilabel:`Point of Sale` dashboard, and :guilabel:`eCommerce` pages." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:47 +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 +msgid "Attribute creation window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:54 +msgid "Then, select a :guilabel:`Display Type`, which determines how this product will be shown on the :guilabel:`eCommerce` page, :guilabel:`Point of Sale` dashboard, and :guilabel:`Product Configurator`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:58 +msgid ":guilabel:`Radio`: options appear in a bullet style list." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:59 +msgid ":guilabel:`Select`: options appear in a dropdown menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:60 +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 +msgid "Display Types on Product Configurator." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:67 +msgid "The :guilabel:`Variants Creation Mode` informs Odoo when to automatically create a new variant once an attribute is added to a product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:70 +msgid ":guilabel:`Instantly`: creates all possible variants as soon as attributes and values are added to a product template." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:72 +msgid ":guilabel:`Dynamically`: creates variants only when corresponding attributes and values are added to a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:74 +msgid ":guilabel:`Never`: never automatically creates variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:77 +msgid "Once added to a product, an attribute's :guilabel:`Variants Creation Mode` cannot be edited." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:79 +msgid "Values should be added to an attribute before saving, but more values can be added at any time, if needed. To add a value, click :guilabel:`Add a line`. From there, you can:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:82 +msgid "Type in the value's name." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:83 +msgid "Check a box to indicate whether or not the value is custom (i.e. the customer provides unique specifications)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:85 +msgid "Specifically for colors, add an HTML color code to make it even easier for salespeople and customers to know what they're selecting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:88 +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 +msgid "Selecting a color." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:95 +msgid "Finally, click :guilabel:`Save` to finish creating the attribute." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:98 +msgid "Attributes can also be created directly from the product template by adding a new line and typing the name into the :guilabel:`Variants` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:101 +msgid "After an attribute is added to a product, a new tab appears on the attribute's page called :guilabel:`Related Products`. This tab lists every product in the database that is currently using the attribute." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:106 +msgid "Creating product variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:108 +msgid "After creating an attribute, use the attribute to create a product variant by going to :menuselection:`Sales --> Products --> Products`. Then, select an existing product and click :guilabel:`Edit`, or create a new product by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:112 +msgid "The :guilabel:`Variants` smart button at the top of the product template indicates the number of currently configured variants on the product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:115 +msgid "To add a new variant, click on the :guilabel:`Variants` tab, then click on :guilabel:`Add a line` to add any attributes and values. When all the attributes and values have been added, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:120 +msgid "Similar product variant creation processes are accessible through the Purchase, Inventory, and eCommerce applications." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:124 +msgid "Managing product exclusions" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:126 +msgid "The following examples are all based on a product template that has two attributes:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:128 +msgid "T-Shirt" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:130 +msgid "Color: Blue, Red, White" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:133 +msgid "With the above product template, there are 15 different t-shirt variants in three different colors and five different sizes. If the white t-shirts are not available in the XXL size, then that variant can be deactivated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137 +msgid "To deactivate a particular product variant, go to :menuselection:`Sales --> Products --> Products` and select the relevant product. Next, click on the :guilabel:`Configure Variants` button, open the relevant product variant attribute value form (in this example, the :guilabel:`White Color` attribute), and then click on :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:142 +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 +msgid "Excluding attributes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:152 msgid "Setting a price per variant" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:202 -msgid "You can add a cost over the main price for some of the variants of a product." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:154 +msgid "Extra costs can be added to a product's standard price for specific product variants." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:205 -msgid "Once you have activated the variant option, you can add variants to your products. To do so, go to the Sales module, open :menuselection:`Sales --> Products` and click on the product you want to modify. Click on the **Variant Prices** button to access the list of variant values." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:156 +msgid "To do this, open :menuselection:`Sales --> Products --> Products`, and click on the relevant product. Next, click on :guilabel:`Configure Variants` to access the list of product variant values." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:213 -msgid "Click on the variant name you wish to add a value to, to make the 3 fields editable. In the **Attribute Price Extra** field, add the cost of the variant that will be added to the original price." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:160 +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:220 -msgid "When you have entered all the extra values, click on **Save**." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:None +msgid "Value Price Extra setting." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:223 -msgid "`Accounting Memento: Details of Journal Entries `_" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:169 +msgid "Impact of variants" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:225 -msgid ":doc:`/applications/finance/accounting/getting_started/process_overview/supplier_bill`" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:171 +msgid ":guilabel:`Barcode`: barcodes are associated with each variant instead of the product template. Each individual variant can have its own unique barcode/SKU." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 +msgid ":guilabel:`Price`: every product variant has its own public price, which is the sum of the product template price and any extra charges for particular attributes. For example, a red shirt's cost is $23 because the shirt's template price is $20, plus an additional $3 for the red color variant. Pricelist rules can be configured to apply to the product template or to the variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:180 +msgid ":guilabel:`Inventory`: inventory is counted for each individual product variant. On the product template form, the inventory reflects the sum of all variants, but the actual inventory is computed by individual variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:184 +msgid ":guilabel:`Picture`: each product variant can have its own specific picture." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:187 +msgid "Changes to the product template automatically apply to every variant of that product." msgstr "" #: ../../content/applications/sales/sales/products_prices/taxes.rst:5 @@ -4360,6 +4744,10 @@ 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 +msgid "How to configure deadlines on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/deadline.rst:22 msgid "Use deadline in your quotation templates" msgstr "" @@ -4368,10 +4756,18 @@ 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 +msgid "How to use deadline in a quotation template on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/deadline.rst:34 msgid "By clicking on the **Customer Preview** button, you will be able to see when the offer expires. For your information, the number of days will be the same as those mentioned in the quotation template." msgstr "" +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:0 +msgid "How customers will see deadlines on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/deadline.rst:44 #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:50 #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51 @@ -4392,6 +4788,10 @@ 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 +msgid "How to enable different customer addresses on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:21 msgid "Add addresses from a quotation" msgstr "" @@ -4400,6 +4800,10 @@ 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 +msgid "How to add addresses from a quotation on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:35 msgid "If you select a customer with defined invoice and delivery addresses, Odoo will automatically use them to fill in the fields. Now, if you want to change it instantly, it is possible to do so directly from the quotation or the sales order." msgstr "" @@ -4412,6 +4816,10 @@ 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 +msgid "How to add addresses from a contact form on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:54 msgid "Deal with different addresses" msgstr "" @@ -4420,10 +4828,18 @@ 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 +msgid "How to manage different customer addresses on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:65 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 +msgid "Automatic quotation fields filling on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:74 msgid "With Odoo Sales, it is now very convenient to play with various addresses in terms of invoice and delivery features." msgstr "" @@ -4444,6 +4860,10 @@ 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 +msgid "How to enable online payment on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:22 msgid "There, you will have direct access to the **Payment Acquirers** page. It will allow you to select and configure your acquirers of choice. Before creating or modifying a payment acquirer, be sure to check out our documentation about how to be paid with payment acquirers such as :doc:`/applications/finance/payment_acquirers/paypal`, :doc:`/applications/finance/payment_acquirers/authorize`, and others in the :doc:`/applications/finance/payment_acquirers` documentation." msgstr "" @@ -4460,6 +4880,10 @@ 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 +msgid "How to register a payment on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:46 msgid "By clicking on the **Customer Preview** button, you will be able to see what your customers will have to choose when it comes to payment." msgstr "" @@ -4492,6 +4916,11 @@ 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:0 +msgid "How to enable online signature on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:21 msgid "If you are familiar with this documentation: :doc:`quote_template`, you can activate or not the **Online Signature** feature for each quotation template you use, under their confirmation tab. Example:" msgstr "" @@ -4504,6 +4933,10 @@ 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 +msgid "How to confirm an order with a signature on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:43 msgid "Once signed, you will have the possibility to choose your payment methods. Then, when the quotation will be paid and confirmed, a delivery order will be created automatically by Odoo." msgstr "" @@ -4528,18 +4961,34 @@ 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 +msgid "How to add optional products to your quotations on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:22 msgid "By clicking on the **Customer Preview** button, you will be able to see what your customers will have as possibilities after opening a quotation from their received email." msgstr "" +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:0 +msgid "Preview your quotations on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:30 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 +msgid "How to select optional products on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:40 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 +msgid "How to follow each movement made by your customers on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:49 msgid "Add optional products to your quotation templates" msgstr "" @@ -4552,10 +5001,86 @@ 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 +msgid "How to add optional products to your quotation templates on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:62 msgid "With Odoo Sales, it is now very easy to understand your customer's needs." msgstr "" +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:3 +msgid "Use product variants on quotations and sales orders" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:5 +msgid "Product variants can be added to quotations and sales orders using the Product Configurator, Variant Grid Entry, or both." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:11 +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 +msgid "Activating entry type settings." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:20 +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 +msgid "Sales variant selection." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:32 +msgid "The product must have at least two variants (one attribute with two values) created in order for the :guilabel:`Sales Variant Selection` option to appear. Click :guilabel:`Add a line` under :guilabel:`Attribute` to add attributes and values to this product and create product variants." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37 +msgid "Use the Product Configurator" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:39 +msgid "The :guilabel:`Product Configurator` appears on a quotation or sales order when products are added that have both variants configured and the :guilabel:`Product Configurator` option selected." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:42 +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 +msgid "Product Configurator and Price Extras." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:52 +msgid "By default, the product variant attributes are displayed on the quotation or sales order in the :guilabel:`Description` column, but the :guilabel:`Product Variant` column can be added through the additional options menu (3 vertical dots icon)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:57 +msgid "Use Variant Grid Entries" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:59 +msgid ":guilabel:`Variant Grid Entries` appear on a quotation or sales order when products are added that have both variants configured and the :guilabel:`Order Grid Entry` option selected. Grid entry can streamline the process of creating large, varied quotations by letting salespeople enter exact quantities of each product variant all at once." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:64 +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 +msgid "Variant Grid Entry pop-up." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:74 +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 +msgid "Line items for grid variants." +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3 msgid "Use quotation templates" msgstr "" @@ -4568,10 +5093,18 @@ 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 +msgid "How to enable quotation templates on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19 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 +msgid "How to enable quotation builder on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:29 #: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:47 msgid "Create your first template" @@ -4585,6 +5118,10 @@ 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 +msgid "Create a new quotation template on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:42 msgid "Design your template" msgstr "" @@ -4593,10 +5130,18 @@ 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 +msgid "Design your quotation template on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54 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 +msgid "Drag & drop building blocks to create your quotation template on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:63 msgid "Use a quotation template" msgstr "" @@ -4605,6 +5150,10 @@ msgstr "" msgid "When creating a quotation, you can choose a specific template." msgstr "" +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:None +msgid "Select a specific template on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:73 msgid "You can select any template of your choice and suggest it as the default template in the **Sales** settings." msgstr "" @@ -4617,6 +5166,10 @@ 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 +msgid "Allow your customers to sign electronically or to pay online on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:88 msgid "Every quotation will now have this setting. Of course you can always change it and make it specific for each quotation." msgstr "" @@ -4647,6 +5200,10 @@ 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 +msgid "How to enable Default Terms & Conditions on Odoo Sales?" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:27 msgid "Please note that this feature is activated via the settings of the **Invoicing App** and **not** via the settings of the **Sales App**. Moreover, you don't need to install the invoicing application since it is done automatically with the installation of the sales application." msgstr "" @@ -4659,6 +5216,10 @@ 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 +msgid "Default Terms & Conditions on quotation on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:42 msgid "They appear subsequently on every quotation, sales order, and invoice." msgstr "" @@ -4671,6 +5232,10 @@ 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 +msgid "Add Default Terms & Conditions to your quotation templates on Odoo Sales" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:56 msgid "Be sure to check out our documentation about quotation templates: :doc:`quote_template`, to master each step of this amazing feature." msgstr "" @@ -4687,10 +5252,18 @@ 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 +msgid "General Terms & Conditions on your website" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:73 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 +msgid "General Terms & Conditions in your business documents" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:83 msgid "GT&C as attachment in your emails" msgstr "" @@ -4699,6 +5272,10 @@ 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 +msgid "General Terms & conditions as attachment in your email" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:94 msgid "GT&C as attachment in your quotation templates" msgstr "" @@ -4707,6 +5284,10 @@ 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 +msgid "General Terms & conditions as attachment in your quotation templates" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:109 msgid "To customize your email templates, activate the **developer mode** and go to :menuselection:`Settings --> Technical --> Email --> Templates`." msgstr "" @@ -4751,6 +5332,12 @@ 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:0 +msgid "View of a subscription product form in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:30 msgid "In the Sales tab, underneath the Subscriptions section, make sure the *Subscription products* option is activated. In fact, if you create a subscription product from the **Odoo Subscriptions** application, this option is selected by default. However, if you create a product from another application, it is not the case." msgstr "" @@ -4822,6 +5409,10 @@ 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 +msgid "Default subscription templates on Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:43 msgid "The **Odoo Subscriptions** application automatically installs **Odoo Sales** and **Odoo Invoicing** as they work integrated." msgstr "" @@ -4830,6 +5421,10 @@ 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 +msgid "Create your own subscription templates on Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:61 msgid "For each template, you can also choose if you want your customers to be able to close their subscriptions or not. If enabled, you can set an *Automatic closing* limit and specify the *Group of subscription* and *Journal* options." msgstr "" @@ -4838,10 +5433,18 @@ msgstr "" msgid "On each template, you can add your **Terms and Conditions**. Specifying terms and conditions is essential to set out important contractual points between the customers and the sellers (payment, refund policy, cancellation, complaints, etc.)." msgstr "" +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:0 +msgid "Terms & conditions on Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:74 msgid "Finally, if you want to know the basic running health status of your subscriptions, you also have access to a specific tab called **Health Check**. There, you can edit and create your own filters to define what is a subscription in good health *vs* bad health. The system automatically summarizes all the records corresponding to these filters and you are able to manage them in one click." msgstr "" +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:0 +msgid "Health check on Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:85 msgid "After creating your own subscription templates, be sure to check out our documentation on how to create, edit and manage your own :doc:`Subscription products <../../subscriptions/configuration/subscription_products>`, to complete the sales flow." msgstr "" @@ -4884,6 +5487,10 @@ 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 +msgid "New automatic alert in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:30 msgid "On the *Apply on* section, first give the alert a name. Then, you can choose to apply this alert on a subscription template, on a specific customer, or even on a specific product. If you want to add more specifications, you can also specify the value of your MRR, the change rate of your MRR over a certain period of time, the value of the satisfaction rate, and even the stage to which you want to apply this alert." msgstr "" @@ -4904,6 +5511,10 @@ 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 +msgid "Satisfaction survey in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:63 msgid "Modify an existing automatic alert" msgstr "" @@ -4912,6 +5523,10 @@ 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 +msgid "Modify an existing automatic alert in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:71 msgid "This alert is applied to the *Rating Satisfaction* of your customers, and the action is triggered on *Timed condition*. If their satisfaction rate is lower than 50%, a salesperson contacts the customer. This action is automatically assigned to the salesperson who manages the subscription, and the due date is 5 days after the triggering of this action. This alert ensures that your clients are happy and that you are taking actions if they are not. It helps to keep your customer retention rates very high." msgstr "" @@ -4948,6 +5563,10 @@ 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 +msgid "Difference between MRR and ARR in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:23 msgid "**Non-Recurring Revenue (NRR)**: NRR shows the revenue earned for everything else than subscription-based products or services. This includes gains of a rare or unique nature that are unlikely to occur in the ordinary course of businesses." msgstr "" @@ -4984,6 +5603,10 @@ msgstr "" msgid "of 9,33%." msgstr "" +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:0 +msgid "Difference between logo churn and revenue churn in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:50 msgid "Reminder: even though they seem to evolve in the same direction most of the time, it might not be the case all the time." msgstr "" @@ -5004,6 +5627,10 @@ 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 +msgid "Subscriptions analysis report in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:74 msgid "Retention analysis report" msgstr "" @@ -5012,6 +5639,10 @@ 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 +msgid "Retention analysis report in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:86 msgid "Revenue KPIs report" msgstr "" @@ -5020,10 +5651,18 @@ 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 +msgid "Revenue KPIs report in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:98 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 +msgid "Detailed MRR report in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:108 msgid "Salesperson dashboard report" msgstr "" @@ -5032,6 +5671,10 @@ 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 +msgid "Salesperson dashboard report in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow.rst:5 msgid "Sales flow" msgstr "" @@ -5060,6 +5703,10 @@ 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 +msgid "Configuration to close your subscription with Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:43 msgid "Be sure to check out our documentation on how to :doc:`Use subscription templates <../../subscriptions/configuration/subscription_templates>` to fully understand the importance of this feature in a basic flow using the **Odoo Subscriptions** application." msgstr "" @@ -5076,10 +5723,18 @@ 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 +msgid "Close your subscription from an administration point of view with Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:62 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 +msgid "What happens when you close your subscription with Odoo Subscriptions?" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:72 msgid "Customer view" msgstr "" @@ -5088,14 +5743,26 @@ 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 +msgid "Close your subscription from a customer point of view with Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:83 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 +msgid "What happens when customers close their subscription with Odoo Subscriptions?" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:90 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 +msgid "What happens when customers close their subscription in Odoo Subscriptions?" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:100 msgid "Before closing a subscription, check out our documentation on how to :doc:`Create a quotation using subscription products <../../subscriptions/sales_flow/create_a_quotation>` to understand how subscriptions are managed in the **Odoo Subscriptions** application." msgstr "" @@ -5128,10 +5795,18 @@ 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 +msgid "View of a quotation form in Odoo Sales" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:39 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 +msgid "Customer preview of a quotation form in Odoo Sales" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:48 msgid "From there, your customers have three choices: *Sign & Pay* the quotation, give you a *Feedback* or *Reject* the quotation. It appears that they are very happy and accept the option *Sign & Pay*. Then, they have to validate the order with a signature and by choosing a payment method. When it is done, you can check out the quotation in **Odoo Sales** and *Confirm* it." msgstr "" @@ -5144,10 +5819,18 @@ 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 +msgid "Quotation form in Odoo Sales with a button \"Subscriptions\"" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:63 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 +msgid "Use of the intelligent button \"Subscriptions\" in Odoo Sales" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:73 msgid "In the top-right corner, you can see the status of the subscription. When a subscription is new and created from **Odoo Subscriptions**, the status is *Draft*. When a sales order has been validated, the status is *In progress*. Finally, when a customer decides to close his subscription, the status becomes *Closed*." msgstr "" @@ -5188,10 +5871,18 @@ 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 +msgid "Renew your subscription with Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:38 msgid "The *To renew* tag is automatically ticked when a payment fails. This indicator also appears on the customer portal. To visualize that, you just have to click on the *Customer preview* button. The tag *To renew* appears on the top right corner." msgstr "" +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0 +msgid "Customer preview of a renewal with Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:46 msgid "When a subscription needs to be renewed, you have the possibility to use a new button called *Renewal quotation*. By clicking on it, a new quotation is created. From there, start a basic sales flow allowing you to send the quotation by email to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers in order to have their confirmation and, then, *Confirm* it in **Odoo Sales**." msgstr "" @@ -5200,10 +5891,18 @@ msgstr "" msgid "In the Chatter of this new quotation, it is mentioned that \"This renewal order has been created from the previous subscription\". Once confirmed by your customers, this quotation becomes a sales order and a new sale is mentioned in the upper right corner of the subscription." msgstr "" +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0 +msgid "Renew a quotation with Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:61 msgid "By clicking on the *Sales* button, you have a summary of your sales orders in a list view. The only difference between your two quotations is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your renewal." msgstr "" +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0 +msgid "Renewal as Subscription Management form in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:70 msgid "Visualize your subscriptions to renew" msgstr "" @@ -5212,6 +5911,10 @@ 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 +msgid "List view of all subscriptions and use of the filter to renew in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:3 msgid "Upsell a subscription" msgstr "" @@ -5232,6 +5935,10 @@ 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 +msgid "Activation of the discount option in Odoo Sales" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:36 msgid "Upsell your first subscription" msgstr "" @@ -5240,10 +5947,18 @@ 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 +msgid "Upsell your subscription with Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:48 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 +msgid "Add products to your subscription via the upsell option in Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:56 msgid "When the quotation is confirmed by your customers, the products are added to the initial subscription. Quotation prices are, then, prorated to the remaining time of the current invoicing period." msgstr "" @@ -5252,10 +5967,18 @@ 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 +msgid "Visualize all your subscriptions updates with Odoo Subscriptions" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:72 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 +msgid "List view of all sales orders created for a subscription" +msgstr "" + #: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:79 msgid "The only difference between your two sales orders is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your upselling." msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index 8fbca02c0..b42c96c2a 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-09-01 15:11+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,10 +49,18 @@ msgstr "" 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:16 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 "" @@ -93,10 +101,18 @@ msgstr "" msgid "If you use them, select your *Worksheet Template* and then click on *Save*." msgstr "" +#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:None +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:25 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." msgstr "" +#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:None +msgid "Field Service task on a sales order in Odoo Sales" +msgstr "" + #: ../../content/applications/services/helpdesk.rst:11 msgid "`Odoo Tutorials: Helpdesk `_" msgstr "" @@ -181,6 +197,13 @@ msgstr "" msgid "To configure the feature go to :menuselection:`Helpdesk --> Settings --> Helpdesk Teams --> Edit` and enable *Ticket closing*." msgstr "" +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:None +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:None +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:None +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:None +msgid "Ticket closing in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:18 msgid "In order to designate to which stage the ticket migrates to once it is closed, go to :menuselection:`Helpdesk --> Overview --> Tickets`." msgstr "" @@ -209,6 +232,10 @@ msgstr "" msgid "To do an analysis of the tickets that have been closed by costumers go to :menuselection:`Helpdesk --> Reporting --> Tickets --> Filters --> Add Custom filter --> Closed by partner --> Applied`." msgstr "" +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:None +msgid "Reports on Ticket closing in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview.rst:5 #: ../../content/applications/services/timesheets/overview.rst:5 msgid "Overview" @@ -237,14 +264,28 @@ msgstr "" msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and enable *Help Center*." msgstr "" +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None +msgid "Overview of the settings page of a helpdesk team emphasizing the help center feature in\n" +"Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:23 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 +msgid "Overview of a forum’s settings page in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:31 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 +msgid "Overview of the Forums page of a website to show the available ones in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:38 msgid "Turn tickets into forum posts by simply clicking on *Share on the Forum* on the ticket's page." msgstr "" @@ -261,14 +302,27 @@ msgstr "" msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *eLearning*." msgstr "" +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:None +msgid "Overview of the settings page of a customer care team emphasizing the feature elearning in\n" +"Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:61 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 +msgid "View of a course being published for Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:67 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 +msgid "View of the elearning applications dashboard for Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73 msgid "Todo" msgstr "" @@ -297,6 +351,10 @@ 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 +msgid "View of the helpdesk teams page in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/getting_started.rst:21 msgid "Team’s productivity and visibility" msgstr "" @@ -317,6 +375,11 @@ 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 +msgid "View of a helpdesk team settings page emphasizing the productivity and visibility features\n" +"in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/getting_started.rst:40 msgid "For the *Random* and *Balanced* assignment methods, you can set the *Team Members* among whom tickets are assigned. Leave the field empty to include all employees (with the proper access rights)." msgstr "" @@ -333,10 +396,18 @@ 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 +msgid "View of a stage’s setting page emphasizing the option to add teams in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/getting_started.rst:55 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 +msgid "View of a team’s kanban view in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/getting_started.rst:64 msgid ":doc:`/applications/general/users`" msgstr "" @@ -353,14 +424,27 @@ 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 +msgid "Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature\n" +"in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/ratings.rst:21 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 +msgid "Overview of a helpdesk team kanban view emphasizing the menu edit stage in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/ratings.rst:28 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 +msgid "View of a standard helpdesk customer review email template for Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/ratings.rst:35 msgid "Ratings can be seen on the chatter of each ticket, under the *See Customer Satisfaction* link on the main dashboard, and through *Reporting*." msgstr "" @@ -373,6 +457,11 @@ 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 +msgid "View of the helpdesk ticket from a user’s portal emphasizing the link to the helpdesk team\n" +"in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/ratings.rst:51 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88 #: ../../content/applications/services/helpdesk/overview/sla.rst:47 @@ -395,6 +484,10 @@ 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 +msgid "View of a helpdesk teams setting page emphasizing the channels options in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21 msgid "Email Alias" msgstr "" @@ -407,6 +500,11 @@ 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 +msgid "View of the settings page of a helpdesk team emphasizing the email alias feature\n" +"in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:35 msgid "Using your own email server is required to send and receive emails in Odoo Community and Enterprise. Online users benefit from a ready-to-use email server." msgstr "" @@ -423,10 +521,19 @@ 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 +msgid "View of the settings page of a helpdesk team emphasizing the Go to Website button in\n" +"Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:49 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 +msgid "View of the website form to submit a ticket for Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:56 msgid "Live Chat" msgstr "" @@ -439,6 +546,11 @@ msgstr "" 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 +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)*." msgstr "" @@ -463,6 +575,10 @@ msgstr "" msgid "3 stars = *Urgent*" msgstr "" +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:None +msgid "View of a team’s kanban view and the prioritized tasks in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:87 #: ../../content/applications/services/helpdesk/overview/reports.rst:60 msgid ":doc:`sla`" @@ -500,6 +616,10 @@ 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 +msgid "View of a helpdesk ticket analysis by team and ticket type in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/reports.rst:25 msgid "The number of tickets closed per day, per team." msgstr "" @@ -508,6 +628,10 @@ 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 +msgid "View of a helpdesk ticket analysis by team and close date in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/reports.rst:35 msgid "Filter it by *Assignee* to see Key Performance Indicators (KPI) per agent." msgstr "" @@ -520,6 +644,11 @@ 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 +msgid "View of helpdesk ticket analysis of the hours to close by ticket type and team in\n" +"Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/reports.rst:48 msgid "Save filters" msgstr "" @@ -528,6 +657,11 @@ 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 +msgid "View of helpdesk ticket analysis emphasizing the option to add a filter as a favorite one\n" +"in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/reports.rst:59 msgid ":doc:`receiving_tickets`" msgstr "" @@ -552,6 +686,10 @@ 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 +msgid "View of an SLA form in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/sla.rst:23 msgid "Choose to which **Team** the policy is relevant and the **Minimum Priority** a ticket needs to have for the policy to be applied." msgstr "" @@ -564,6 +702,10 @@ 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 +msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/sla.rst:37 msgid "SLA Analysis" msgstr "" @@ -572,6 +714,10 @@ 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 +msgid "View of the SLA status analysis page emphasizing the group by option in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5 msgid "Timesheet and Invoice" msgstr "" @@ -596,6 +742,11 @@ 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 +msgid "View of a helpdesk team settings page emphasizing the timesheet on ticket and time\n" +"reinvoicing features in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:28 msgid "Step 2: Set up a service" msgstr "" @@ -608,10 +759,19 @@ 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 +msgid "View of a product's form emphasizing the product type and unit of measure fields in Odoo\n" +"Sales" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:40 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 +msgid "View of a product form and the invoicing options under the tab sales in Odoo Sales" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:47 msgid "This configuration ensures that the customer is invoiced by the number of hours predicted in the sales order, meaning that less or extra hours recorded are not taken into account. It also ensures that every time a sales order is confirmed, a new task is created under the right project, automating the process." msgstr "" @@ -632,6 +792,10 @@ 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 +msgid "View of a sales order emphasizing the order lines in Odoo Sales" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:72 msgid "Step 2: Invoice the customer" msgstr "" @@ -640,6 +804,10 @@ msgstr "" msgid "In *Sales*, select the respective sales order to *Create Invoice*." msgstr "" +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:None +msgid "View of a sales order emphasizing the create invoice button in Odoo Sales" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:82 msgid "Step 3: Link the task to the ticket" msgstr "" @@ -648,6 +816,10 @@ 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 +msgid "View of a helpdesk ticket emphasizing the field task in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:92 msgid "Step 4: Record the time spent" msgstr "" @@ -656,10 +828,18 @@ 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 +msgid "View of a helpdesk ticket emphasizing the timesheets tab in Odoo Helpdesk" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:100 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 +msgid "View of a sales order emphasizing the delivered column in Odoo Sales" +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:108 msgid "Hours recorded on the ticket are automatically shown in *Timesheets* and on the dedicated task." msgstr "" @@ -717,6 +897,10 @@ 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 +msgid "Create a sales order and add a product." +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:48 msgid "Record a timesheet" msgstr "" @@ -725,6 +909,10 @@ msgstr "" msgid "To record a timesheet, jump back to the Helpdesk ticket by going to the :guilabel:`Helpdesk` dashboard, clicking :guilabel:`Tickets` on the team's card, and locating the correct ticket. 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 +msgid "Record time spent on a ticket." +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:60 msgid "The ticket's timesheets can be recorded before or after the sales order is made, the order doesn't matter." msgstr "" @@ -737,6 +925,10 @@ msgstr "" msgid "To link the :guilabel:`Sales Order` to the ticket, start on the ticket form and click :guilabel:`Edit`. Next, select the :guilabel:`Sales Order` that was created earlier from the :guilabel:`Sales Order Item` drop-down menu. Odoo will automatically filter the options to only show sales orders that are connected to the ticket's customer. Lastly, click :guilabel:`Save` to connect the ticket and the :guilabel:`Sales Order Item`." msgstr "" +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:None +msgid "Link the SO item to the ticket." +msgstr "" + #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:77 msgid "The :guilabel:`Sales Order Item` can be connected to the ticket before or after any timesheets are recorded, the order doesn't matter." msgstr "" @@ -810,6 +1002,10 @@ 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 +msgid "In the settings of your project, define the emails alias under the tab email in Odoo Project" +msgstr "" + #: ../../content/applications/services/project/tasks/email_alias.rst:30 msgid "All the recipients of the email (To/Cc/Bcc) are automatically added as followers of the task." msgstr "" @@ -818,6 +1014,10 @@ 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 +msgid "View of the email alias chosen on the dashboard view in Odoo Project" +msgstr "" + #: ../../content/applications/services/timesheets.rst:8 msgid "Timesheets" msgstr "" @@ -834,10 +1034,19 @@ 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 +msgid "View of Timesheets setting enabling the feature record time off in Odoo Timesheets" +msgstr "" + #: ../../content/applications/services/timesheets/overview/time_off.rst:16 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 +msgid "View of a time off types form emphasizing the time off requests and timesheets section in\n" +"Odoo Time Off" +msgstr "" + #: ../../content/applications/services/timesheets/overview/time_off.rst:26 msgid "Now, once the employee has requested his time off and the request has been validated (or not, depending on the setting chosen), the time is automatically allocated on *Timesheets*, under the respective project and task." msgstr "" @@ -846,14 +1055,26 @@ 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 +msgid "View of the time off request form in Odoo Time Off" +msgstr "" + #: ../../content/applications/services/timesheets/overview/time_off.rst:33 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 +msgid "Video of timesheets emphasizing the requested time off from the employee in Odoo Timesheets" +msgstr "" + #: ../../content/applications/services/timesheets/overview/time_off.rst:41 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 +msgid "View of the details of a project/task in Odoo Timeheets" +msgstr "" + #: ../../content/services/support/what_can_i_expect.rst:7 msgid "What can I expect from the support service?" msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index 25acc55d7..36fca6682 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-11-17 09:05+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -215,6 +215,10 @@ msgstr "" msgid "Don't forget to hit *Save* once all variants have been entered." msgstr "" +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +msgid "ecommerce product variants values" +msgstr "" + #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:39 msgid "Edit variants" msgstr "" @@ -223,6 +227,10 @@ 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 +msgid "ecommerce product variants smart button" +msgstr "" + #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:48 msgid "Clicking the *Variants* smart button takes you to the Product Variants page, where you can edit the following data for each specific variant:" msgstr "" @@ -263,6 +271,10 @@ 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 +msgid "ecommerce product variants configure variants" +msgstr "" + #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:72 msgid "To set a specific public price for a particular variant, simply click on the variant you want to modify, then click on *Edit*." msgstr "" @@ -271,10 +283,18 @@ 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 +msgid "ecommerce value price extra" +msgstr "" + #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:82 msgid "This is how the *Value Price Extra* looks on your website:" msgstr "" +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:None +msgid "ecommerce value price extra on the frontend" +msgstr "" + #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:89 msgid "Pricelist formulas let you set advanced price computation methods for product variants. See :doc:`../maximizing_revenue/pricing`." msgstr "" @@ -287,10 +307,18 @@ 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 +msgid "ecommerce product variants archive" +msgstr "" + #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:103 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 +msgid "ecommerce product variants archive search" +msgstr "" + #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:110 msgid ":doc:`../../../sales/sales/products_prices/products/variants`" msgstr "" @@ -335,10 +363,18 @@ msgstr "" msgid "To add *Accessory Products*, go to :menuselection:`Website --> Products --> Products` and, under the :guilabel:`Sales Tab`, add your products to the :guilabel:`Accessory Products` field." msgstr "" +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:None +msgid "Add an accessory product to product form." +msgstr "" + #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:32 msgid "Now, go to your website and add the product to your cart. On the payment step, you can see your accessory products suggested to the customer." msgstr "" +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:None +msgid "See of payment view and accessory product suggestion." +msgstr "" + #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:40 msgid "`Odoo Tutorials: Alternative, Accessory, and Optional Products `_." msgstr "" @@ -355,10 +391,18 @@ msgstr "" msgid "To enable optional products, go to :menuselection:`Website --> Configuration --> Settings` and tick :guilabel:`Optional Products`. Then, go to :menuselection:`Website --> Products --> Products` and open the item you want to add an optional product to. In the :guilabel:`Sales tab` of that product, add as many optional products as you want." msgstr "" +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:None +msgid "Add an optional product to product form." +msgstr "" + #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:60 msgid "From now, when a customer adds this product to their cart, a pop-up appears and suggests also adding the optional product(s)." msgstr "" +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:None +msgid "Pop-up with optional products appears." +msgstr "" + #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:68 msgid ":doc:`upselling`" msgstr "" @@ -557,10 +601,18 @@ 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 +msgid "payment is confirmed in the chatter of sales order" +msgstr "" + #: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:24 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 +msgid "page with details surrounding the specific transaction" +msgstr "" + #: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:32 msgid "Specific messages are provided to your customers for every payment status whenever they are redirected to Odoo after the transaction. To edit these messages, go to the *Messages* tab of the payment method." msgstr "" @@ -589,6 +641,10 @@ msgstr "" msgid "Then activate *Automatic Invoices* and *Save*." msgstr "" +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:None +msgid "example of automatic invoice" +msgstr "" + #: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:54 msgid "Capture payment after the delivery" msgstr "" @@ -670,10 +726,18 @@ msgstr "" 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 +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 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 +msgid "View of a live chat channel form for Odoo Live Chat" +msgstr "" + #: ../../content/applications/websites/livechat/overview/get_started.rst:27 msgid "For both scenarios, under:" msgstr "" @@ -690,6 +754,10 @@ msgstr "" 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 +msgid "View of a channel’s rules form for Odoo Live Chat" +msgstr "" + #: ../../content/applications/websites/livechat/overview/get_started.rst:43 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 "" @@ -706,6 +774,10 @@ msgstr "" 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 +msgid "View of the widget tab for Odoo Live Chat" +msgstr "" + #: ../../content/applications/websites/livechat/overview/get_started.rst:59 msgid "Managing chat requests" msgstr "" @@ -714,6 +786,10 @@ msgstr "" 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 +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 msgid "Conversations are dispatched based on the current workload of the online operators." msgstr "" @@ -726,6 +802,10 @@ msgstr "" 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 +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`" @@ -760,14 +840,26 @@ msgstr "" msgid "A copy of the conversation can also be sent by email." msgstr "" +#: ../../content/applications/websites/livechat/overview/ratings.rst:None +msgid "View of the chat window from a user’s side for Odoo Live Chat" +msgstr "" + #: ../../content/applications/websites/livechat/overview/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 +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 msgid "And under :menuselection:`Report --> Customer Ratings`." msgstr "" +#: ../../content/applications/websites/livechat/overview/ratings.rst:None +msgid "View of the customer ratings page in Odoo Live Chat" +msgstr "" + #: ../../content/applications/websites/livechat/overview/ratings.rst:35 msgid "Make the rating public" msgstr "" @@ -776,6 +868,10 @@ msgstr "" 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 +msgid "View of the public ratings in the website for Odoo Live Chat" +msgstr "" + #: ../../content/applications/websites/livechat/overview/responses.rst:3 msgid "Commands and Canned Responses" msgstr "" @@ -828,6 +924,10 @@ msgstr "" 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 +msgid "View of the chat window with a helpdesk ticket created in Odoo Live Chat" +msgstr "" + #: ../../content/applications/websites/livechat/overview/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 "" @@ -844,6 +944,10 @@ msgstr "" 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 +msgid "View of a chat window and the use of a canned response in Odoo Live Chat" +msgstr "" + #: ../../content/applications/websites/website.rst:8 msgid "Website" msgstr "" @@ -976,6 +1080,10 @@ msgstr "" msgid "Go to :menuselection:`Website --> Configuration --> Settings` and activate *Link Trackers*." 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 "" @@ -984,6 +1092,10 @@ msgstr "" 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 "" @@ -1012,6 +1124,10 @@ msgstr "" 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 "" @@ -1749,11 +1865,11 @@ msgid "Generate an Unsplash access key" msgstr "" #: ../../content/applications/websites/website/optimize/unsplash.rst:9 -msgid "**As a SaaS 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." +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-Saas users" +msgid "Generate an Unsplash access key for non-Odoo Online users" msgstr "" #: ../../content/applications/websites/website/optimize/unsplash.rst:15 @@ -1777,7 +1893,7 @@ msgid "You should be redirected to your application details page. Scroll down a msgstr "" #: ../../content/applications/websites/website/optimize/unsplash.rst:42 -msgid "**As a non-SaaS user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour." +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 @@ -1797,7 +1913,7 @@ msgid "You will be redirected to your application details page. The **applicatio msgstr "" #: ../../content/applications/websites/website/optimize/unsplash.rst:65 -msgid "**As a non-SaaS user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction." +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